Hello.
I've included the header file "catch.hpp" in my iOS application where I have a C++ part and defined #define CATCH_CONFIG_MAIN in a cpp file that I want to be tested.

I've also written a simple test:

int return_int(int arg){
return 1;
}

TEST_CASE( "Test", "[int]" ) {
REQUIRE(return_int(1) == 1);
REQUIRE(return_int(2) == 1);
}

But all I have are these two errors

If I create a test using a testcase source with a name "{m} (unique attribute)" and pass that test in through -testlist argument the test will not be discovered. If there is no space "{m}(unique attribute)" this works fine. The problem is in the TextRunner.MakeRunSetting when its building the prefilter list from the test list it is not trimming the sub string so the parent of the tests are not bei

Issue Classification

• Feature request

Feature Request

From yarn build. 3 github paths fail in docosaurus, slack url needs to be absolute.

• Page path = /implementation_guides/javascript/readme:
  -> link to examples/v3/e2e (resolved as: /implementation_guides/javascript/examples/v3/e2e)
  -> link to examples/v3/todo-consumer (resolved as: /implementation_guides/javascript/

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.

As part of the process of making the Pact docs more user friendly, we'd like to start writing feature documentation once, and providing code examples for each of the languages, rather than everyone having to write the same docs over and over again in each language.

The documentation for the consumer version selectors can be our first opportunity to give this approach a try. I have written the beh

Bug Report

After updating to the latest test-tls13-obsolete-curves.py there were ~100 failures due to a new check that extensions are rejected due to a mismatch of the curve with the key share. While that's a good test, it is unrelated to the purpose of this test file. As such one updating to the new version that does not want to comply with the newly introduced requirement, would have to dis