MDPS Prototype Validation Plan

[mike-gangl]

MDPS Validation Plan

Validation from the perspective of the MMO: MDPS Operators/MDPS Developers, non-functional requirements, based on L3 Requirements. These should be heavily influenced by:

• existing test (SPS, CS) nightlies
• Incoprorate unity-py in nightly testing so procedures can be shared with users
• test plan (gherkin), test proc (code)
• Reporting?

Documents

• L1-3 Requirements (complete)
• Prototype Requirements

Acceptance Criteria

• Automated Testing to test various functionalities (CS, SPS)
• Test Reporting is generated and made available (slack, testrails?)
• Test plan and test procedure are integrated together in gherkin
• Test plan should include deployment, testing and tear down
• Upgrades, rollbacks can be manual tested
• Includes monitoring of services

Work Tickets

Link to work tickets required to implement the epic

• [x] https://github.com/unity-sds/unity-system-test/issues/12
• [x] https://github.com/unity-sds/unity-system-test/issues/11
• [x] https://github.com/unity-sds/unity-system-test/issues/16

Dependencies

Other epics or outside tickets required for this to work

• [ ] TBC

Associated Risks

links to risk issues associated with this epic

• [ ] TBC