Description
As a MARGO User, I would like to run a set of automated Conformance Tests, for my specific commercial component mapping to a MARGO persona, at the end of which a test report is generated and automatically signed.
- The Conformance Tests must be built as Persona Specific Suites
- The Conformance Test must be easy to develop using a well-known / easy to use tool or representation
- It should be possible to select a pre-defined grouping or collection of tests
- The Conformance Framework must be capable of running the tests in an 'on-prem' Linux host
- The Conformance Framework must record the date/time, version of MARGO specification and the version of the tested component in the test report and sign it with a Digital Signature
- The Conformance Framework must provide the pass / fail status for each test in the test report
- The conformance framework may collect the OTEL traces and telemetry as evidence of the test
Raised by (email-id)
nilanjan.samajdar@capgemini.com
Type of Story
Implementation
Related product requirements
Specification
Definition of Done
The required technical documentation should be updated
In case of any prototyping activity, the evaluation, design and outcomes need to be documented
API updates need to be updated in swagger (or other) files
Test automation should be done to demonstrate the use-case
Code and documentation should be pulled into the release branch and the pull-request approved by the TWG
Estimated Story-points
200
Impacted artifacts
Description
As a MARGO User, I would like to run a set of automated Conformance Tests, for my specific commercial component mapping to a MARGO persona, at the end of which a test report is generated and automatically signed.
Raised by (email-id)
nilanjan.samajdar@capgemini.com
Type of Story
Implementation
Related product requirements
Specification
Definition of Done
The required technical documentation should be updated
In case of any prototyping activity, the evaluation, design and outcomes need to be documented
API updates need to be updated in swagger (or other) files
Test automation should be done to demonstrate the use-case
Code and documentation should be pulled into the release branch and the pull-request approved by the TWG
Estimated Story-points
200
Impacted artifacts