Agile Automated Testing quadrants
Q1- Automated- unit
Q2 -Requirements- business focus
Q3- Manual – feedback of Q1 and Q2 and starting for automated testing
Q4- Tools - Non functional requirments
Agile Automated Testing plan
- For each release of application
- Testing scope
- Feature complexity tst coverage
- Test new functionality
- Performance and load testing
- Infrastructure review
- Available resources
- Mititgation or risk plan
- Deliverables and milestone of testing
Agile Automated testing life cycle
- Iteration 0- initial setup identify resource,install tools, scheduling etc- ,
- construction iterations
- Release end game- system and acceptance testing
- Production
Agile automated testing risks
- Cost to build and maintain
- Does not replace exploratory manual testing
- Unreliable tests or unclear user stories
- Relying on macro-recording test
- Part of continuous integration process
- Inadequate test plan
- Missing setup/tear down scripts
- High level of maintenance
- Metrics may be misleading
- Lack of automated testing expertise
- Team collaboration is crucial
- Focusing on the valuable features
Agile and Devops Test automation
Agile vs. Devops principles
- Agile- speed of deployment, while in devops-team specialization
- Agile focus on creating vs deploying software while devops focus on communication vs documentation
- Devops relies on documentation, while agile will be scheduling timeframe or meetings
- Agile teams are small, devops many teams collaborate to large team
- Agile focus not on automation, devops focus on automation
Devops test automation factors
- Management of test data
- Steering parameters
- Test servers and virtualization
- Dedicated test user accounts
- Continuous testing and integration
- High degree of communication required among teams
Test automation and Dev-Ops
- Supports continuous development
- Coordination required amongst stakeholders
- All processes must be automated
Dev-Ops test automation best practices
- Set achievable expectations
- Ensure test automaton is adopted
- Assign dedicated resources
- Decide on a starting point
- Include automation testing in definition of done
- Review and adapt
No comments:
Post a Comment