SA1 Release Testing
Procedures and tests used to validate a new release on the test infrastructure.
- Install the Testbench (take the DB backups and restore them in the DBs).
- Build gLite
- Locally with the python client
- Remotely with the Webapp
- Build Etics
- Locally with the python client
- Remotely with the Webapp
- Build locked
- Build unlocked
- Verify the produced reports
- possibility of downloading produced packages
- Review all bugs
- Reproduce the bugs and check they are fixed
- Report non fixed bugs
- Run consistency tests on the DBs
- Repeat the builds above if necessary
Open Questions
- Do we need some tests to check:
- NMI?
- Several platforms?
- Test the deployment of all components?
- Run all tests (unit, etc) on the installation?