Relate a subset of Verification Requirements defined in AIV MID Continuous Integration Roadmap to Software Tests and resultant reports

The verification of requirements defined in the AIV MID Continuous Integration Plan is currently an unknown / undefined process. If one such set of requirements that relate to preferably an integration point early in the plan can be identified, defined in Gherkin (BDD), and related Python tests can be produced, the process will be better understood from the viewpoints of both the AIV and the (T/P)DTs, and the software teams (SAFe).

A proper definition of such a process can assist with building a bridge between the AIV planning documentation and the agile software work streams.

• A SUT is identified for early testing in a PSI (or ITF?)
• One test (or tests) is (are) identified from the AIV MID Continuous Integration (CI) Roadmap and added to Jira (XTP)
  • ICD/L1 requirements are used to generate a test scenario/requirement
  • The test set is translated in Gherkin language and incorporated in the SKAMPI repository
  • Gitlab CI Pipeline is not blocked by failing tests
• The process of test creation related to the AIV MID CI Roadmap can be demonstrated or is documented