We’re continuing our work to create a curriculum focused on automation that is created with feedback from the testing community. We’ve already run a series of activities that have helped us identify a list of key tasks that helped us create this Job Profile .
We’re now in the process of going through each task and analysing them to identify the core steps we take to achieve them. For this post we’re considering the task:
Maintaining Test Environments
We’ve run a series of community activities including social questions and our curriculum review sessions to identify the steps we need to take to successfully achieve this task and have listed them below.
Identify what requires maintenance:
- Product version
- Product configuration
- Environment configuration
- Data management
- Rebuilding/resetting a broken environment
- Access management to product and infrastructure
- Integration with the pipeline
React to smoke tests / monitoring output / live issues
Making sure environment syncs with live
Making sure that environment data are sanitized and cleaned to not contain production data
Check if the environment is working properly (no memory leak or any other problem)
Connect to the environment and:
- Use CLI tools to debug issues and manage infrastructure
- Run scripts to install / update environment
- Connect to DBs to manage data
Test the environment and make sure it works
Establish a pipeline with test environment configuration
Test if the environment is connected to the right environment (db, application and so on)
What we would like to know is what do you think of these steps?
Have we missed anything?
Is there anything in this list that doesn’t make sense?
What do you do when an automated test fails?