Current behavior:

We use --env variable to pass some environment variables to cypress, when it's running both in headless and headed mode.

One of the parameters is a hash (mix of numbers and characters). Surprisingly some specific hash values make cypress to fail reading this value from the command line (e.g. 769e98018). The corresponding environment variable is not set and the `Cyp

I'm getting bit with failing documentation builds because I'm writing docstrings that JSDoc doesn't like (specifically, TS-style). But there's no linting happening before getting to Netlify.

We may be able to make JSDoc just check the syntax and exit (and make it part of the lint scripts).

This is moot if we want to move forward with maintaining our own TS types (for which there is an op

The go build command in the Compilation Wiki will throw complaints.

#Compile from source
cd $HOME/gocode/src/github.com/buger/gor
go build LDFLAGS = -ldflags "-extldflags "-static""

$ go build LDFLAGS = -ldflags "-extldflags \"-static\""
can't load package: package LDFLAGS: malformed module path "LDFLAGS": missing dot 

As a new end user, I cannot find a single user guide or decent documentation. The javadoc reads like it's written as a quick review for someone who already knows the ins/outs of Mockito and just need some sample code. I don't even know what or how Mockito works and the first couple of lines are talking about "mockito inline".

Most open source projects have really great user guides and document

We need to write an article similar to https://github.com/hdorgeval/testcafe-snippets/blob/master/say-goodbye-to-flakyness.md. There should be a list of best practices that help writing stable and reusable tests.

The title says it all. I couldn't find any documentation on the theming, but the home page says you can use custom and third-party themes.

I've setup EG2 using CocoaPods, and ensured the base functionality works. I then followed the instructions for the whitebox setup.

When attempting to interact with the target app, I get the following error: caught "NSInvalidArgumentException", "*** -[NSProxy doesNotRecognizeSelector:<method_name>] called!"

Wi

This is meant as a discussion to follow up on #411. For those interested in getting more involved with goss, I am interested in the following:

1. Now that there is a CONTRIBUTING.md, issue/pr templates,

背景是乐视大数据部接收机tcp协议接收机压力测试，服务端口为9999。采用falcon监控相关性能信息。
解决方式是tcpcopy服务器开启4倍流量时出现大量rst包现象，后来改为两个tcpcopy进程启动1倍流量后,恢复正常。看cpu参数我理解是单tcpcopy进程占用一个cpu核心100%，24核cpu没有完全使用。采用开启两个进程曲线救国。
10.116.95.87 target server

10.116.95.81 intercept
/usr/local/intercept/sbin/intercept -i eth1 -F 'tcp and

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

Hi there,

I think this can be a good issue for a first-time contributor. It would be great if we can increase documentation for the DatabaseCleaner::Configuration API: https://github.com/DatabaseCleaner/database_cleaner/blob/master/lib/database_cleaner/configuration.rb#L56-L72

Even though methods are pretty self-explanatory, I think it is a good idea to maintain a complete documentation for

Hi,

first of all, I really like Kotest's matchers and consider to move from AssertJ to them.

But I noticed that AssertJ adds useful line breaks after each element in the failure message of the collection matches. Here is an example:

AssertJ:

assertThat(actualDesigns).containsExactly(
    Design(id = 1, userId = 9, name = "Cat", dateCreated = Instant.ofEpochSecond(151827819

Actual

Test environments don't set up certificates. Using Taiko against these environments produces certificate errors. For example

goto("https://172.0.1.111:1234") 
[FAIL] Error: Navigation to url https://172.0.1.111:1234 
failed.
REASON: net::ERR_CERT_AUTHORITY_INVALID, run .trace for more info.

Change

Ignore certificates by default. The tester can choose to not ig

Prepare similar Controls Overview like we have for "win32" backend: https://pywinauto.readthedocs.io/en/latest/controls_overview.html

Actual behavior

When there is no internet connection or the machine is behind a proxy

$ gauge install js
Failed to install plugin 'js'.
Reason: Invalid plugin. Could not download js-install.json file.

This error very cryptic and does not point out to the right cause which confuses the user for example.

Steps to reproduce

1. Go off the internet or configure a proxy

1. Is your feature request related to a problem? Please describe. (这个功能是为解决什么问题)
A clear and concise description of what the problem is. Explain your use case, context, and rationale behind this feature request (请尽可能详尽地说明这个需求的用例和场景)

2. Describe the solution you'd like(请描述你期望的结果)
A clear and concise description of what you want to happen (简单清楚的描述你期望的结果)

**3. Additional context `

How can I mock a url that is used to download a file?
Is it possible to set a file into the body of register_uri?

Hello!,

Just started working with this package and have to say is great!.

Was playing with the Supervisor class and would love to have an option specify the path where supervisorctl resides as well to be able to define where the configuration may reside.

There are some scenarios where the

If you comment out test cases with a here-doc like

: <<EOC
@test 'to be ignored for now' {
}
EOC

this greatly confuses bats-core.
As far as I have seen from a very quick look, you pre-process the test file line-wise.
So every line that looks like a test, even if just part of a multi-line string or here-doc will be considered a test case and confuse bats-core later on.

The hard 100 request (POST/PUT/GET/etc) limit should be more prominently called out in docs.

Line 172 from https://github.com/Mashape/mockbin/blob/master/docs/api/bins.md reads:

All requests to Bin will be logged for later inspection (max of 100 requests)

On a personal project I must have missed that line and burned myself because I thought there was an internal application/ne

When there is no match, the response body will contain useful debugging information such as what matcher came the closest and which specific criteria it did not match on.

The problem is that we can also get the false positive scenario, where we are expecting a particular match to take place but a different one does instead.

We propose an explain functionality along the lines of `hoverctl

When running our jasmine integration tests we see this deprecation warning:

Setting throwOnExpectationFailure directly on Env is deprecated, please use the oneFailurePerSpec option in configure

We should address this.