Once deployed to production, the AQS 2.0 services need a way to run the tests continuously to ensure stability and quality. When discussed running the Python-based test suite in CI previously (citation needed), there were a lot of challenges.
Open Questions
- could automated tests run in a cron-based fashion on Toolforge/Cloud VPS?
- Is there an automated report system that AQS team members are prompted to check regularly
- is there a way to implement an automated alert system?
- how will we check for regressions?
- can we use gitlab?
- how does RESTbase do it?
- Does serviceops have insights?
- Are AQS test environments (cassandra/druid) ready to run into a CICD pipeline?
References
- Doing Unique CI Things: DUCT
- AQS 2.0: Revisit in-service testing approach: https://phabricator.wikimedia.org/T328969#8623061