@@ -33,10 +33,13 @@ Cognizant of costs and maintenance overhead, we categorize the environments to a
### Transient Environments
***QA Development Secondary Environment**
This a recommended environment to provide a stable environment for the QA team to build functional tests for new capabilities in the platform. This will start initially manual during test development before they can automate this to create postman/newman scripts. The goal is to explore, document and automate the test cases and append the suite to be ready for push into durable QA automation environment. At the moment the QA engineers will need to compete with automation tests and milestone updates in QA automation environment for their own development. Because this requires test data and the assurance before pre-ship it should also be fed with build artifacts from the CSP/provider's CICD rather than just the community Gitlab - so tests run in simulated prod environment.
***Preship Secondary Environment for Operational Procedure Testing**
Because Production environment is mainly for operator and representative users to exercise the system before shipping out, the tests should assure the environment will not be impacted negatively. This means any tests around load/performance tests or operational tests such as disaster recovery, backup/restore, service rollback/roll-forward strategies need to be done in an isolated space. This environment is a transient setup that can allow for such potentially destructive tests - as a mock production environment, this should be populated from the CSP/provider's CICD rather than just the community Gitlab and the test data sets (Volve, TNO) should be pre-populated here.
***Preship Secondary Environment**
***Preship Secondary Environment for Security Testing**
This is similar to the previous transient preship secondary environment - any tests around security such as pen tests, port-scans, DOS attacks etc. will be done in this temporary but isolated space. As a mock production environment, this should be populated from the CSP/provider's CICD rather than just the community Gitlab and the test data sets (Volve, TNO) should be pre-populated here.
