test

Current behavior

When using Cypress as a library, there is one file called node_modules/cypress/types/net-stubbing.ts which only contains type definitions.
Together with latest version of API extractor, this creates the error:

Error: <project>/node_modules/cypress/types/net-stubbing.ts:1:1 - (ae-wrong-input-file-type) Incorrect file type; API Extractor expects to analyze compiler out

Description of the feature request:

BlzMod will soon allow native.local_repository() and native.new_local_repository() to be called from module extension implementation functions (see issue 15412).

This feature request is to add new optional arguments to new_local_repository() to generate MODULE.bazel files, in addition to BUILD.bazel and WORKSPACE.bazel ones.

e.g. module_file and `m

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

Describe the bug

I'm having some trouble and need some advice on creating a TS class with private/protected readonly members and have it pass my vitest tests.

asset.ts

export enum AssetType {
  STOCK,
  CRYPTO,
}

export abstract class Asset {
  protected readonly _type: AssetType;
  protected readonly _symbol: string;
  protected readonly _name: string;
  protec

uiautomator2的版本号：2.11.1

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

模版图像是：

截图：

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

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

https://github.com/kotest/kotest/blob/b47f92247e12bdb43617c762950ed1f392e0afe1/kotest-assertions/kotest-assertions-core/src/commonMain/kotlin/io/kotest/matchers/result/matchers.kt#L62

Currently, a test that tests for

a shouldBeSuccess b

will fail if a is Failure (as expected).

What it won't do is print what was the failure, so there's no way to debug other than, well, debug

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,

Describe the solution you'd like
An example to use jest-preview to test app with jquery

Describe how should jest-preview implements this feature

• Use @testing-library/dom to test
• Use jest-preview to debug/ write new tests faster

Additional context

• @testing-library/dom can test any JS framework
• jquery update the JSDOM manually in the test environment. Anyth