Test Management System
Work package deliverables
| No | Deliverable | Proof | 
|---|---|---|
| 1 | Set up system for full visibility of sources (tests cases and scenarios) and results (artifacts) of automatic (CI/CD pipeline) and manual tests | |
| 2 | CI/CD and security pipelines fully integrated into test management system | |
| 3 | Tests running in defined environments (feature, development, staging, production) | |
| 4 | Testing schedule / matrix defined for the milestone | |
| 4.1. | Test stages that will be required to run for this milestone are defined, fully scoped and properly established | |
| 4.1.1 | Static analysis integrated into the pipeline | |
| 4.1.2 | Unit tests written in go (in device-management-service repo) and included into the pipeline (with ~90% coverage rate) | |
| 4.1.3 | Functional tests are written in Gherkin and included into the pipeline (in appropriate stage) | |
| 4.1.4 | Security tests defined, implemented and included into the pipeline / schedule | |
| 4.1.5 | End to end tests defined in Gherkin and included into the pipeline (in appropriate stages) | |
| 4.1.6 | Other tests that need to be implemented are identified, and additional stages are identified as needed | |
| 5 | All testing artifacts for each run / build are accessible via integrated test management system (Testmo) and available for QA team to make a decision for release | |
| 6 | Test schedule / matrix include all the tests independently of how they are implemented and provides full visibility; Some test may be needed but not automated due to lack of time or automating them is problematic; These tests should be marked as 'manual' and executed via manual schedule monitored by QA team via test management system / testmo | |
| 7 | Process / procedure of how bug reports that are approved for solving are described by the test cases scenarios and included into the test stages | 
Edited  by kabir