add first version (empty, minimal and data-tables are enabled) of the compatibility kit

Author: daantimmer

compatibility/CMakeLists.txt

@@ -0,0 +1,40 @@
+function(add_compatibility_kit name)
+    set(libname compatibility.${name}.test)
+    add_executable(${libname})
+
+    if(CCR_BUILD_TESTS)
+        add_test(NAME ${libname} COMMAND ${libname})
+    endif()
+
+    target_link_libraries(${libname} PRIVATE
+        cucumber_cpp
+        gtest_main
+    )
+
+    target_include_directories(${libname} PUBLIC
+        $<BUILD_INTERFACE:${CMAKE_CURRENT_SOURCE_DIR}/../..>
+    )
+
+    target_sources(${libname} PRIVATE
+        compatibility.cpp
+        ${name}/${name}.cpp
+    )
+
+    string(REPLACE "-" "_" KITNAME ${name})
+
+    target_compile_definitions(${libname} PRIVATE
+        KIT_NAME=${KITNAME}
+        KIT_FOLDER="${CMAKE_CURRENT_SOURCE_DIR}/${name}"
+        KIT_NDJSON_FILE="${CMAKE_CURRENT_SOURCE_DIR}/${name}/${name}.ndjson"
+    )
+endfunction()
+
+file(GLOB kits RELATIVE ${CMAKE_CURRENT_LIST_DIR} ${CMAKE_CURRENT_LIST_DIR}/*)
+foreach(kit ${kits})
+    if (IS_DIRECTORY ${CMAKE_CURRENT_LIST_DIR}/${kit})
+        if (EXISTS ${CMAKE_CURRENT_LIST_DIR}/${kit}/${kit}.cpp)
+            message(STATUS "Adding compatibility kit: ${kit}")
+            add_compatibility_kit(${kit})
+        endif()
+    endif()
+endforeach()

compatibility/ambiguous/ambiguous.feature

@@ -0,0 +1,6 @@
+Feature: Ambiguous steps
+  Multiple step definitions that match a pickle step result in an AMBIGUOUS status, since Cucumnber cannot determine
+  which one to execute.
+
+  Scenario: Multiple step definitions for a step
+    Given a step with multiple definitions

compatibility/ambiguous/ambiguous.ndjson

@@ -0,0 +1,13 @@
+{"meta":{"protocolVersion":"31.0.0","implementation":{"name":"fake-cucumber","version":"123.45.6"},"cpu":{"name":"arm64"},"os":{"name":"darwin","version":"24.5.0"},"runtime":{"name":"Node.js","version":"24.4.1"},"ci":{"name":"GitHub Actions","url":"https://github.com/cucumber-ltd/shouty.rb/actions/runs/154666429","buildNumber":"154666429","git":{"revision":"99684bcacf01d95875834d87903dcb072306c9ad","remote":"https://github.com/cucumber-ltd/shouty.rb.git","branch":"main"}}}}
+{"source":{"data":"Feature: Ambiguous steps\n  Multiple step definitions that match a pickle step result in an AMBIGUOUS status, since Cucumnber cannot determine\n  which one to execute.\n\n  Scenario: Multiple step definitions for a step\n    Given a step with multiple definitions\n","uri":"samples/ambiguous/ambiguous.feature","mediaType":"text/x.cucumber.gherkin+plain"}}
+{"gherkinDocument":{"feature":{"tags":[],"location":{"line":1,"column":1},"language":"en","keyword":"Feature","name":"Ambiguous steps","description":"  Multiple step definitions that match a pickle step result in an AMBIGUOUS status, since Cucumnber cannot determine\n  which one to execute.","children":[{"scenario":{"id":"1","tags":[],"location":{"line":5,"column":3},"keyword":"Scenario","name":"Multiple step definitions for a step","description":"","steps":[{"id":"0","location":{"line":6,"column":5},"keyword":"Given ","keywordType":"Context","text":"a step with multiple definitions"}],"examples":[]}}]},"comments":[],"uri":"samples/ambiguous/ambiguous.feature"}}
+{"pickle":{"id":"3","uri":"samples/ambiguous/ambiguous.feature","location":{"line":5,"column":3},"astNodeIds":["1"],"tags":[],"name":"Multiple step definitions for a step","language":"en","steps":[{"id":"2","text":"a step with multiple definitions","type":"Context","astNodeIds":["0"]}]}}
+{"stepDefinition":{"id":"4","pattern":{"type":"REGULAR_EXPRESSION","source":"^a (.*?) with (.*?)$"},"sourceReference":{"uri":"samples/ambiguous/ambiguous.ts","location":{"line":3}}}}
+{"stepDefinition":{"id":"5","pattern":{"type":"REGULAR_EXPRESSION","source":"^a step with (.*)$"},"sourceReference":{"uri":"samples/ambiguous/ambiguous.ts","location":{"line":7}}}}
+{"testRunStarted":{"id":"6","timestamp":{"seconds":0,"nanos":0}}}
+{"testCase":{"id":"7","pickleId":"3","testSteps":[{"id":"8","pickleStepId":"2","stepDefinitionIds":["4","5"],"stepMatchArgumentsLists":[{"stepMatchArguments":[{"group":{"start":2,"value":"step","children":[]}},{"group":{"start":12,"value":"multiple definitions","children":[]}}]},{"stepMatchArguments":[{"group":{"start":12,"value":"multiple definitions","children":[]},"parameterTypeName":""}]}]}],"testRunStartedId":"6"}}
+{"testCaseStarted":{"id":"9","testCaseId":"7","timestamp":{"seconds":0,"nanos":1000000},"attempt":0}}
+{"testStepStarted":{"testCaseStartedId":"9","testStepId":"8","timestamp":{"seconds":0,"nanos":2000000}}}
+{"testStepFinished":{"testCaseStartedId":"9","testStepId":"8","testStepResult":{"status":"AMBIGUOUS","duration":{"seconds":0,"nanos":0}},"timestamp":{"seconds":0,"nanos":3000000}}}
+{"testCaseFinished":{"testCaseStartedId":"9","timestamp":{"seconds":0,"nanos":4000000},"willBeRetried":false}}
+{"testRunFinished":{"testRunStartedId":"6","timestamp":{"seconds":0,"nanos":5000000},"success":false}}

compatibility/ambiguous/ambiguous.ts

@@ -0,0 +1,9 @@
+import { Given } from '@cucumber/fake-cucumber'
+
+Given(/^a (.*?) with (.*?)$/, function () {
+  // first one
+})
+
+Given(/^a step with (.*)$/, function () {
+  // second one
+})

compatibility/attachments/attachments.feature

@@ -0,0 +1,36 @@
+Feature: Attachments
+  It is sometimes useful to take a screenshot while a scenario runs or capture some logs.
+
+  Cucumber lets you `attach` arbitrary files during execution, and you can
+  specify a content type for the contents.
+
+  Formatters can then render these attachments in reports.
+
+  Attachments must have a body and a content type.
+
+  Scenario: Strings can be attached with a media type
+    Beware that some formatters such as @cucumber/react use the media type
+    to determine how to display an attachment.
+
+    When the string "hello" is attached as "application/octet-stream"
+
+  Scenario: Log text
+    When the string "hello" is logged
+
+  Scenario: Log ANSI coloured text
+    When text with ANSI escapes is logged
+
+  Scenario: Log JSON
+     When the following string is attached as "application/json":
+       ```
+       {"message": "The <b>big</b> question", "foo": "bar"}
+       ```
+
+  Scenario: Byte arrays are base64-encoded regardless of media type
+    When an array with 10 bytes is attached as "text/plain"
+
+  Scenario: Attaching PDFs with a different filename
+    When a PDF document is attached and renamed
+
+  Scenario: Attaching URIs
+    When a link to "https://cucumber.io" is attached