test

To reproduce:

1. Open Cypress.
2. Click “View App Data” via the context menu.
3. App crashes.

Desired behavior: View App Data works, and errors with View App Data are gracefully handled.

Description of the problem / feature request:

If I use

--execution_log_json_file

or

--

Currently, when entering epic mode the README is frozen in the last level of the tower. When you're trying to fine-tune the score for a level other than the last one, it would be helpful if we had the README for that level available. The proposal is that when entering epic mode, the README is updated with all levels, one following the other.

Example:

# Starbolt - beginner

uiautomator2的版本号：2.11.1

使用device.image.match时匹配错误

模版图像是：

截图：

匹配结果：{'similarity': 0.9961444735527039, 'point': [319, 673]}

直接使用findit模块测试也是这么高匹配度，估计是findit模块不给力，是

Clear and concise description of the problem

Error enumerable properties are not shown for test case:

import { test } from 'vitest';

test('throw error with context', () => {
  const err = new Error('This is an error with context');
  err.userId = 32;
  err.companyId = 64;
  throw err;
})

![image](https://user-images.githubusercontent.com/600821/156337522-c37b328b-6b28-

https://github.com/kotest/kotest/blob/f1c729d7de1150d30ee1806fe354887ce80777cd/kotest-framework/kotest-framework-api/src/commonMain/kotlin/io/kotest/core/config/AbstractProjectConfig.kt#L29

Small bugfix in KDocs

First, AbstractProjectConfig must be instantiated, therefore this must be changed to

: AbstractProjectConfig()

Change in KDocs

For the line
https://github.com/kotes

The issue is based on the discussion in #559.

@zvirja

should we probably modify CI so that doc is published automatically on push to master? This way if we don't want doc to be released right now - just keep it in a branch. Otherwise, we have this non-synchronized docs and manual work.. 😟

@dtchepak

I'm not sure what to do about publishing docs. It would be nice to auto-publish,