First of all – Why we need testing! We need development “That Pays”
- Satisfy the customer through early and continuous delivery of valuable software.
- Testing is the only way to “approve” that something is really done from an end customer’s perspective.
In addition, automated testing is a core activity of any agile development methodology. As we move towards continuous deployment, test automation becomes ever more important due to the quick feedback response that is provides to the development team about the health of the application.
We automate the tests for a different reason
- Defect Prevention rather than defect detection.
- Communicate requirements.
- “Pin” the functionality once it’s built
We automate the tests in a different way
- Using tools that support collaboration & communication and not just confirmation.
We automate tests to
- Prevent anticipatable defects from happening.
- Find non anticipatable defects ASAP
However, the real issue that
- Automation testing requires development
- Development requires developers
- Developers (i.e. “automation experts”) = big $$$
- Development requires decent development tools
It would be nice if…
- Testers could write tests
- Developers could write the automation code
- Combine the two with little effort.
Majid Bhatti is a Program Director & Agile Coach and he has extensive experience of Information Technology and Enterprise Business Integration Management including Project / Program Management of Infrastructure & Business Intelligence Applications deployment, Agile Implementation, Large-scale outsourcing deals pursuit, Transition & Transformation of IT services with track record of successful launching, directing and managing of large scale complex programs.
468total visits,3visits today