test

Summary

Really small test difference with 9.x, for the settings page we confirm that the panels are collapsed by default in 9.x.

The panels are closed by default in the implementation, but there is no test confirming this behavior.

Acceptance Criteria

• Write a test to ensure the panels are closed by default.

Resources

9.x Settings page

<img width="912" alt="Sc

Description of the feature request:

For better bash-less Windows support,ctx.actions.run_shell could add command_bat (with the same behavior as genrule's cmd_bat) and command_ps (with the same behavior as genrule's cmd_ps).

This would, in particular, considerably simplify skylib's Windows support, where currently we are forced to write and execute temporary .bat files on Wind

Describe the bug

The printf formatting isn't working as expected from the example in the documentation.

describe.each([
  { a: 1, b: 1, expected: 2 },
  { a: 1, b: 2, expected: 3 },
  { a: 2, b: 1, expected: 3 },
])('describe object add(%i, %i)', ({ a, b, expected }) => {
  test(`returns ${expected}`, () => {
    expect(a + b).toBe(ex

uiautomator2的版本号：2.11.1

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

模版图像是：

截图：

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

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

On top of being able to specify item type, which must hold for every item, it should be possible to specify the contains schema, which must hold true for at least 1 item by default. It should be possible to specify min/max times the schema may occur using minContains, maxContains.

See https://json-schema.org/understanding-json-schema/reference/array.html#contains

As part of this,

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,

Which feature you want to improve?
GitHub Actions CI

What and why you want to improve that feature
GitHub Actions CI should run linting. So contributors know they need to enforce the pretiier

Potential bugs/ unexpected behaviors
None for now

How to implement the changes

• Update code inside .github/workflows.
• If we can update in an existing .yml file, we do not