This is a dup of #1620. However #1620 was closed by the stale bot and I can't reopen it. The issue still has merit so I (re-)submit the issue.

For our purposes, we'd just like the file names easily parsable and since the terminal's ls -l sorts by filename by default, make sure the filenames start with the year, month, day, hour etc.

Currently, lib/testsuite/screenshots.js:18 has:

st

(请尽量按照下面提示内容填写，有助于我们快速定位和解决问题，感谢配合。否则直接关闭。)

(重要！问题分类)

• 测试开发环境AirtestIDE使用问题 -> https://github.com/AirtestProject/AirtestIDE/issues
• 控件识别、树状结构、poco库报错 -> https://github.com/AirtestProject/Poco/issues
• 图像识别、设备控制相关问题 -> 按下面的步骤

描述问题bug
(简洁清晰得概括一下遇到的问题是什么。或者是报错的traceback信息。)

Linux执行airtest脚本报"There is no SIFT module in your OpenCV environment！"

根据https://github.com/AirtestPr

refer: microsoft/vscode#27950 (comment)

cc @kirksl

note that today you can do things like print foo in the debug terminal input / REPL as a workaround

When using pa11y programatically (I needed to hook into some webpack-dev-server lifecycle hooks) it wasn't clear from the README how to add the CLI reporter.

Thankfully it was consistent with the HTML reporter, which was documented, however it'd have been easier if there was a comment under the reporters section linking to other reporters.

Hi,

Here I outline various use cases I have seen during my past years on different projects, doing all kinds of automation of quality, for possible applications of RP. Outcomes could be improved documentation, tutorials or separate issues created.

As my home work I did quick look and searches of issues and codes on github and documentation on reportportal.io. Also @DzmitryHumianiuk have ans

Remove any following parts if does not have details about

Describe the bug
在测试poco官方提供的tutorial的时候，总是出现错误，按照这个代码运行的时候，拖动星星的顺序是从左到右第一个，第三个，第五个，然后就运行不下去了，甚至在拖动第三个的时候也停止了，

![qq 20190306170237](https://user-images.githubusercontent.com/18191658/53869373-0e5d0e00-4033-11e

Some patterns should be avoided when writing programs with P# (especially as some of them can break our controlled testing infrastructure). We should make sure to document these.

I followed the documentation for setting a viewport in the config file, but when I do so I get the following error when pa11y tries to run:

Error: page.setRequestInterception is not a function

Expectation
When setting a viewport in the pa11y config file, the test execution runs as expected against the given viewport.

Actual
I get the following error when setting a viewport in

I see things like Condition.get(String uri) which say that they accept a URI. But the examples show things like get("/demo"), which is not a URI at all --- it's a path. And there's no documentation about encoding at all.

Yes I know that Request.getRequestURI() really returns a path, but that's an old API and it was named badly to begin with. There are so many variations of things that are

Can the bars in features, tags, steps summary pages be made clickable so the link opens to the details page directly.
So it goes from pages/tag-summary.html to pages/tag-scenarios/tag_TagOver.html when the TagOver bar is clicked.
Saves the time for scrolling and searching for the desired tag, feature or step in the section below.

Create descriptions for JDI Asserts.
JDI Asserts classes are located in the following packages:

1. com.epam.jdi.light.asserts.generic
2. com.epam.jdi.light.ui.html.asserts

Before adding a new testing tool, please follow the contributing guide:

Search previous suggestions before making a new one, as yours may be a duplicate.
Make an individual pull request for each suggestion.
Chose the corresponding section.
New categories or improvements to the existing categorization are welcome.
Research if the tool you're including is actually awesome and useful. THanks