Agile Test Automation: Truth, Oxymoron or Lie?
•
1 recomendación•964 vistas
This document discusses agile test automation and addresses whether it is an essential truth, oxymoron, or lie. It notes that agile emphasizes parallel teamwork between development, testing, and business. While test automation may initially require extensive ramp-up time and skills acquisition, building a library of automated scripts and using programmatic test tools can help achieve faster feedback, consistency, and avoid technical debt. The document advocates automating tests in parallel with development in each sprint to allow for easy, flexible regression testing. It argues that with an evolving approach to automation and a focus on reusing test data, process knowledge, and results, agile test automation can be an essential part of the agile process.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Destacado
Destacado (15)
Similar a Agile Test Automation: Truth, Oxymoron or Lie?
Similar a Agile Test Automation: Truth, Oxymoron or Lie? (20)
Último
Último (20)
Agile Test Automation: Truth, Oxymoron or Lie?
- 1. Agile Test Automation: Truth, Oxymoron or Lie? George Wilson Original Software
- 3. Quick Poll Are you currently using Agile methodologies? Yes – for all projects Yes – for some projects Thinking about it Not at all
- 6. Parallel Teamwork Dev Test Business
- 7. Why Test Automation May Fail Extensive ramp-up time Lower on-going value Skills Acquisition Build Script Library Automation partially available Script Maintenance Cycles Benefit ‘Black-outs’ Shelf-ware Warning Benefit Effort Time Effort 4-8+ months Programmatic Test Tools
- 8. Falling Back to Manual Testing Less challenging More effort Skills Acquisition Build Script Library Automation partially available Script Maintenance Cycles Benefit ‘Black-outs’ Shelf-ware Warning Benefit Effort Time Effort 4-8+ months Programmatic Test Tools Fall Back to Manual Testing
- 11. Agile Testing Success Build tests in parallel First time manual Issues Automation Data
- 12. Automation is Essential Manual is slow Faster feedback Consistency Empower testers Confidence Avoid toxic debt Documentation
- 13. Inhibitors Rapid change Attitude Initial investment Sweat and pain Fear
- 14. Traditional Automation Pyramid Application Automation High Risk Manual
- 16. Too Late, too slow Sp 1 Sp 2 Sp 3 Sp 4 Build regression Not a separate sprint. Sp 1 Sp 2 Sp 3 Sp 4 Regn Regn Regn Not overflowing the sprint.
- 17. Regression Deliverable Des Code FT RT Sprint 1 Sprint 2 Sprint 3 ReF Des Code FT RT ReF Des Code FT RT ReF Design Code, TDD Refactor Functional Test Regression Test Regression in each sprint Easy, Flexible Avoid toxic debt – bugs and scripts
- 18. Manual Auto Table effects UI – Db validation Data Rules Start: Manual Testing Progress: Automated Testing Test Cycles Evolutionary Testing Unit Testing Integration Simulation Tibco, Software AG, Web Methods, Websphere… Oracle SQLServer DB2
- 21. Daily Regression Cross platform Multi action Branching Error recovery
- 22. Agile AQM model
- 23. Control – Electronic Whiteboard
- 24. Testing is all about data Input Process Output Data Process Result Data Process ResultData Data
- 25. Setup & Tear-Down Raise order Despatch Invoicing GL processing Incremental Roll-back Automated Test Processes
- 26. Testing the Database Pol Last Claim Claim Curr Tot Claim Name 1203301 00.11.2006 Y GBP 1266.61 Jackson 1203302 10.11.2006 C EUR 505.20 Henderson Wilks1203303 01.01.2006 N GPB 1203301 12.01.2006 420.00 1203301 08.11.2006 761.42 1203302 10.11.2006 505.20 GBP Pounds Sterling EUR Euro USD US Dollars Rules based validation
- 27. Re-use is key Process Knowledge Results Data Automation meaningless without re-use
- 30. Essential User Interface Fast build for UI Code free Middleware & Services Stub and simulate Test component interaction Database Plan data Manage data
- 31. Dilbert says...