Trends in Agile Testing by Lisa Crispin
•Transferir como PPT, PDF•
11 gostaram•5,686 visualizações
![Introduction ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (9)
Semelhante a Trends in Agile Testing by Lisa Crispin
Semelhante a Trends in Agile Testing by Lisa Crispin (20)
Mais de Directi Group
Mais de Directi Group (20)
Último
Último (20)
Trends in Agile Testing by Lisa Crispin
- 1. Trends in Agile Testing Code Chef Talks 2009 Lisa Crispin With Material from Janet Gregory
- 5. Traditional vs. Agile SDLC Phased or gated – ex. Waterfall It 1 It 2 It 3 A B A B A B C C D Time Agile : iterative and incremental - Each story is expanded, coded and tested - Possible release after each iteration Requirements Specifications Code Testing Release Copyright 2009 Lisa Crispin and Janet Gregory
- 10. Test Approach - The Agile Way Copyright 2007: Lisa Crispin and Janet Gregory Project Initiation Get an understanding of the project Participate in estimating stories Create Test Plan Release Planning Each Iteration 1 … . X Write and execute story tests Write and execute new functional test cases Pair test with other testers, developers Automate new functional test cases Run automated regression test cases Perform Load Test Complete Regression Test Perform UAT Perform Mock Deploy Participate in Release Readiness System Test / End Game Participate in Release to Prod Participate in Retrospectives Release to Prod/ Support
- 22. BDD/Narrative/Scenario Example Given that the FitNesse wiki is a Wiki Given that the FitNesse User is a Web User Given that the FitNesse wiki was able to start for the first time When the FitNesse User attempts to go to the Home Page Then the content of the Home Page for the FitNesse User should be Welcome to the Wonderful World of FitNesse! From: Antony Marcano, Andy Palmer, testingreflections.com, pairwith.us
- 24. Testing Tool Spectrum Agile2009 - © ASERT 2006-2009 Database Drivers DbUnit DataSets SqlUnit groovy.sql JPA JDO BigTable JDBC SOAP / REST Drivers GroovyWS XML-RPC CXF Axis2 JAX-WS JAX-RS Utilities All Pairs Combinations Polyglot languages Logic programming Threads, Parallel concurrency libraries Data-driven libraries Networking libraries XML Processing Read/write files, Excel / Word / CSV, Reporting, Logging Other Drivers FEST Email FTP AntUnit Telnet SSH Exec Tools iTest2, SoapUI, Twist, IDEs, JMeter, Text editors, Recorders, Build Tools, CI Web Drivers WebTest WebDriver JWebUnit Tellurium Selenium HtmlUnit Watij HttpBuilder Cyberneko Runners Native Groovy, JUnit, TestNG, Spock, EasyB, JBehave, Cucumber, Robot Framework, Slim
- 30. Questions?
- 32. Copyright 2008 Janet Gregory, DragonFire Bridging the Communication Gap Specification By Example and Acceptance Testing Gojko Adzic
- 33. Now Available Agile Testing: A Practical Guide for Testers and Agile Teams By Lisa Crispin and Janet Gregory www.agiletester.ca
Notas do Editor
- When I talk about Agile, I will usually refer to XP or SCRUM because those are the 2 methodologies I am the most familiar with. When I talk about traditional methods, I mean phased or gated methodologies such as waterfall. Phased Approach - waterfall Coding occurs after requirements and specifications are complete Testing occurs after coding is complete Application not delivered until all phases are complete Some problems with waterfall: missing and out of date requirements gaps between what the customer is expecting and what is delivered Agile = Testing occurs on a feature by feature basis Each feature (or story) is delivered incrementally Business value is delivered on a regular basis