We never have enough of them. They never mirror production. They never work.
My opinions at my current company:
- Who should own test environments? Testers.
- Who should build test environments? NOT testers. DevOps.
- Who should request test environments? Testers.
- Who should populate, backup, or restore the test data in test environments? Testers.
- Who should configure test environments to integrate with other applications in the system? NOT testers. DevOps.
- Who should deploy code to test environments? NOT testers. Whoever (or whatever) deploys code to production.
- Who should control (e.g., request) code changes to test environments? Testers.
- Who should create and maintain build/deploy automation? NOT testers. DevOps.
- Who should push the “Go” button to programmatically spin up temporary test environments? Testers or test automation.
Fiddling with test environments is not testing work, IMO. It only subtracts from test coverage.
1 comments:
Subscribe to:
Post Comments (Atom)
RSS
Indeed. And perhaps the biggest reason for testers not deploying the builds is that if the first time DevOps (or whoever is doing it in prod) touches the process is on production night, we're all gonna be up till 5 AM, just hoping it actually works and all the database changes got pushed as well, and then spend the next day pretending that's actually an acceptable process.