Use Gherkin to define TCK for UUID and UUri serialization #252
Conversation
|
|
||
| Scenario Outline: | ||
| Developers using a uProtocol language library should be able to verify that a specific | ||
| endpoint identifier matches a given pattern as specified by the UUri specification. |
There was a problem hiding this comment.
Is it possible to add links (to the spec) here? Probably something to do once we move this over to up-spec...
There was a problem hiding this comment.
Instead of linking directly to the corresponding sections in the spec documents, I would rather rely on the OFT specification items which are used to link to the corresponding requirements defined in the specification documents. Links tend to become invalid over time without anybody noticing. However, if the OFT spec items are changed, we will immediately know when doing the trace run ...
sophokles73
force-pushed
the
use_gherkin_to_define_tck
branch
5 times, most recently
from
bc58db0 to
8c8ddb8
Compare
|
I also had to adapt the check.yaml GitHub workflow to correctly run all tests (unit/doc/integration) and create junit reports for them. I have also figured out how to include the integration (TCK) tests in the tarpaulin (test coverage) run. That will require a (small) change to the shared workflow definition in the uprotocol/ci-cd repo. We can then replace the checks that we had originally implemented in unit tests with the corresponding TCK tests ... |
|
@PLeVasseur @stevenhartley WDYT? |
sophokles73
force-pushed
the
use_gherkin_to_define_tck
branch
5 times, most recently
from
823b09b to
7cdcfe7
Compare
sophokles73
force-pushed
the
use_gherkin_to_define_tck
branch
from
7cdcfe7 to
66cf285
Compare
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.
sophokles73
force-pushed
the
use_gherkin_to_define_tck
branch
from
66cf285 to
9b22c66
Compare
indeed |
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.
This is mainly a demonstration of how this could work. If we decide to go in this direction, we would first need to move the Gherkin files to up-spec, of course.