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

Spurred by conversation in avajs/ava#2449 and avajs/ava#1485 we'd like for our assertions to return booleans. true when they pass, false when they fail. This does not apply to the throws() and throwsAsync() assertions.

Failing assertions will fail the test, but do not throw exceptions. This means your test does not stop executing. Usua

Describe the bug
When TEMPLATE_LIST_TEST_CASE and TEMPLATE_LIST_TEST_CASE_METHOD were added, the corresponding versions with the CATCH_ prefix were missed.

Expected behavior
CATCH_TEMPLATE_LIST_TEST_CASE and CATCH_TEMPLATE_LIST_TEST_CASE_METHOD should be available.

Additional context

The commit that added TEMPLATE_LIST_TEST_CASE and `TEMPLATE_LIST_TEST_CASE_MET

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.

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

While working on an issue about parallel execution and for this I checked synchronization docs and was still unsure about where it is possible / needed / suggested to place the @ResourceLock and @Execution(SAME_THREAD) annotations. (_The current example only shows the test case, but it's a

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

(重要！问题分类)

• 测试开发环境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

This is more of a development problem and does not affect users as it is with dev dependencies. When cloning the repository and running yarn, yarn warns about incorrect peer dependencies:

$ git clone https://github.com/apiaryio/dredd.git dredd-clean
Cloning into 'dredd-clean'...
remote: Enumerating objects: 54, done.
remote: Counting objects: 100% (54/54), done.
remote: Compressin

AssertJ's AbstractIterableAssert is large. We don't have an equivalent to every last assertion (and this is sometimes intentional), but for cases in which we do have an equivalent, we could help prospective users / migrating users / users with

When running build.ps1 -t Test, the following output describes the failing tests:

1. Failed : NUnit.Framework.Api.FrameworkControllerTests.ExploreTestsAction_FileNotFound_ReturnsNonRunnableSuite
   Expected: String containing "The system cannot find the file specified."
   But was: "Le fichier sp├®cifi├® est introuvable. (Exception from HRESULT: 0x80070002)"
   at NUnit.Framework.Api.Framew

• pulsar version: N/A
• python version: N/A
• platform: N/A

Description

It seems that your documentation hosted at https://docs.pulsarweb.org/ is unavailable.

When I try to access it I get the following message:

Error 1014 Ray ID: 4598be0f691559cc • 2018-09-13 07:01:25 UTC
CNAME Cross-User Banned
What happened?

You've requested a page on a website that is par

Several pages of the docs are in need of an update. Includes the following:

• Adding the system daemon docs from the README to the site
• Updating or removing the examples page
• Updating the client libraries, including potentially adding a github organization
• Updating the support iframe
• Updating the glossary to the mental model map from manning
• Validating the contracts page is up to

The default Success message has poor contrast (gray over green).

The tutorial should reflect the routing and the pipeline testing change - the difference between the execution of the filters.

Basically we need to choose between:

class X {

  private $foo;

  public function __construct(string $foo) {
    $this->foo = $foo;
  }

  public function getFoo(): string {
    return $this->foo;
  }
}

or:

class X {

  /**
   * @var string
   */
  private $foo;

  public function __construct(string $foo) {
    $this->foo = $foo;
  }

  public f

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

Builds that change an interface or have backwards-incompatible changes in them will fail an Appveyor build because they pull in pact from NPM rather than the in-build changes.

See https://ci.appveyor.com/project/pact-foundation/pact-js/builds/32277939 for an example.

We should npm link @pact-foundation/pact as we do in build.sh on Linux, so that the examples are always tested against the

I would like to drop Spring Boot support for 1.5.x. It is EOL https://spring.io/blog/2018/07/30/spring-boot-1-x-eol-aug-1st-2019
I would also add some notes in the docs, that we adhere to the spring boot lifecycle in order to be transparent about dropping support for versions.

In some cases the RoundTrip call returns an error (e.g. EOF) and res is therefore nil:

https://github.com/pact-foundation/pact-go/blob/9fa77068bd49724a0fe38004586892206fb48e7e/proxy/http.go#L140

We are trying to migrate from MSTestV1 to MSTestV2. While doing so we noticed the behavior change documented in DeltaWithMSTestV1 - Behavior change 12 which leads to some trouble.

Unfortunately, we did not find any way to limit the execution time of the ClassInitialize and AssemblyInitialize methods.

In a

Hey,

Im going through examples in readme and in https://volument.com/baretest but as far as i can tell, just copy pasting them throws errors.

It would be nice to have a repo to clone to:

1. see how to set it up. currently i dont understand what this supposed to be const test = require('.')('sum'), in docs. And its not lack of my js knowledge that bothers me.
2. verify the performance cl

New test script idea

What TLS message this idea relates to?

ClientHello

What TLS extension this idea relates to?

signature_algorithms

What is the behaviour the test script should test?

RFC 8446, section B.3.1.3 and B.3.1.4 describe values, marked as obsolete_RESERVED that MUST NOT be offered or negotiated by TLS 1.3 implementations.

Check that presence of those

Bandit needs a logo. The automatically generated avatar on GitHub always reminds me of that.

My initial idea was to combine the hexagon of the C++ logo, a bandit mask and a BDD cycle in one logo. The [result of my first attemp