Use Gherkin to define TCK for UUID and UUri serialization

The up-tck component had been using Gherkin for defining the TCK's
test scenarios. The idea was that these could be used for verifying a
language library's compliance with the specification.

This is a first step in the direction described in
eclipse-uprotocol/up-tck#116.

The TCK's test scenarios have been adapted to cover more cases and, in
particular, also cover failure cases. The corresponding unit tests have
been replaced by Cucumber based tests and the Gherkin files have been
amended with OpenFastTrace specification identifiers and are now also
included when doing the requirements tracing run.

Author: sophokles73

.env.oft-current

@@ -17,7 +17,7 @@ UP_SPEC_FILE_PATTERNS="up-spec/*.adoc up-spec/*.md up-spec/basics up-spec/up-l1/
 
 # The file patterns that specify this component's resources which contain specification items
 # that cover the requirements
-COMPONENT_FILE_PATTERNS="*.adoc *.md *.rs .github examples src tests tools"
+COMPONENT_FILE_PATTERNS="*.adoc *.md *.rs .github examples features src tests tools"
 
 OFT_FILE_PATTERNS="$UP_SPEC_FILE_PATTERNS $COMPONENT_FILE_PATTERNS"
 OFT_TAGS=""

.env.oft-latest

@@ -17,7 +17,7 @@ UP_SPEC_FILE_PATTERNS="up-spec/*.adoc up-spec/*.md up-spec/basics up-spec/up-l1/
 
 # The file patterns that specify this component's resources which contain specification items
 # that cover the requirements
-COMPONENT_FILE_PATTERNS="*.adoc *.md *.rs .github examples src tests tools"
+COMPONENT_FILE_PATTERNS="*.adoc *.md *.rs .github examples features src tests tools"
 
 OFT_FILE_PATTERNS="$UP_SPEC_FILE_PATTERNS $COMPONENT_FILE_PATTERNS"
 OFT_TAGS="_,LanguageLibrary"

.github/workflows/check.yaml

@@ -23,6 +23,7 @@ on:
   pull_request:
     paths:
       - "src/**"
+      - "tests/**"
       - "Cargo.*"
       - "build.rs"
       - "deny.toml"
@@ -134,13 +135,11 @@ jobs:
           cargo hack check --feature-powerset --no-dev-deps
 
   # [impl->req~up-language-ci-test~1]
-  nextest:
+  test:
     # Subset of feature-combos, on only one OS - more complete testing in test-featurematrix.yaml
     outputs:
       test_results_url: ${{ steps.test_results.outputs.artifact-url }}
     runs-on: ubuntu-latest
-    env: 
-      NEXTEST_EXPERIMENTAL_LIBTEST_JSON: 1
     strategy:
       matrix:
         feature-flags: ["", "--no-default-features", "--all-features"]
@@ -151,28 +150,23 @@ jobs:
       - uses: dtolnay/rust-toolchain@master
         with: 
           toolchain: ${{ env.RUST_TOOLCHAIN }}
-      - uses: Swatinem/rust-cache@v2
-      # install tool to convert cargo's JSON test output to JUNIT format
-      - run: |
-          cargo install cargo2junit
-      # Using nextest because it's faster than built-in test
-      - uses: taiki-e/install-action@nextest
-      - name: Run cargo nextest
+
+      - name: Run lib tests
+        run: |
+          RUSTC_BOOTSTRAP=1 cargo test --no-fail-fast --lib ${{ matrix.feature-flags }} -- -Z unstable-options --format junit --report-time > ${GITHUB_WORKSPACE}/target/lib-test-results.xml
+      - name: Run doc tests
         run: |
-          cargo nextest run ${{ matrix.feature-flags }} --profile ci
-      - name: Run doctests
+          RUSTC_BOOTSTRAP=1 cargo test --no-fail-fast --doc ${{ matrix.feature-flags }} -- -Z unstable-options --format junit --report-time > ${GITHUB_WORKSPACE}/target/doc-test-results.xml
+      - name: Run TCK tests
         run: |
-          # we use tee to let cargo test print to the console
-          RUSTC_BOOTSTRAP=1 cargo test --doc ${{ matrix.feature-flags }} -- -Z unstable-options --format json --report-time | tee target/doctest-results.json
-          # write output to same directory as the one used by cargo nextest in order
-          # to flatten the directory hierarchy when uploading the test results
-          cat target/doctest-results.json | cargo2junit > target/nextest/ci/doctest-results.xml
+          # the Cucumber based tests write a junit format results file to "target/tck-[test]-results.xml"
+          cargo test --no-fail-fast --test 'tck_*' ${{ matrix.feature-flags }}
 
       - name: Upload all-features test results artifact
         id: test_results
         if: matrix.feature-flags == '--all-features'
         uses: actions/upload-artifact@v4
         with:
           name: test-results
-          # this will include the nextest and doctest result files in the archive's root folder
-          path: target/nextest/ci/*-results.xml
+          # include all test result files
+          path: target/*-results.xml

.github/workflows/nightly.yaml

@@ -49,6 +49,8 @@ jobs:
     uses: eclipse-uprotocol/ci-cd/.github/workflows/rust-x-build.yaml@main
 
   coverage:
+    # TODO: in order to allow tarpaulin to also gather coverage from the cucumber-rs based tests,
+    # the 'cargo tarpaulin' command needs to contain option '--implicit-test-threads'
     uses: eclipse-uprotocol/ci-cd/.github/workflows/rust-coverage.yaml@main
 
   current-spec-compliance:

.github/workflows/release.yaml

@@ -32,6 +32,8 @@ jobs:
     uses: eclipse-uprotocol/ci-cd/.github/workflows/rust-verify-msrv.yaml@main
 
   coverage:
+    # TODO: in order to allow tarpaulin to also gather coverage from the cucumber-rs based tests,
+    # the 'cargo tarpaulin' command needs to contain option '--implicit-test-threads'
     uses: eclipse-uprotocol/ci-cd/.github/workflows/rust-coverage.yaml@main 
 
   current-spec-compliance: