Agile Testing - LAST Conference 2015
•Descargar como PPTX, PDF•
1 recomendación•1,358 vistas
Stop trying to test in quality, shift quality to the left & start building it in.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Destacado
Destacado (8)
Similar a Agile Testing - LAST Conference 2015
Similar a Agile Testing - LAST Conference 2015 (20)
Más de Theresa Neate
Más de Theresa Neate (8)
Último
Último (20)
Agile Testing - LAST Conference 2015
- 1. Theresa Neate & Bharat Sangekar - LAST Conference 2015 Agile Testing - Shifting quality to the left
- 2. Theresa Neate & Bharat Sangekar - LAST Conference 2015 What you will get out of this talk 1. Theresa will a. provide some context about the mindset of agile testing b. give an overview of the rituals of agile testing c. workshop some pragmatic approaches to agile testing 2. Bharat will a. give an overview of the adaptive role of an agile tester b. discuss depth of testing in shifting quality left c. provide an example of a shift left scenario d. discuss ways quality can shift left 3. Summary and questions 2
- 3. Theresa Neate & Bharat Sangekar - LAST Conference 2015 Introducing Bharat https://au.linkedin.com/in/bsangekar Barrat, maybe Brett = Not bad Brad = Cool Just not, BORAT 3
- 4. Theresa Neate & Bharat Sangekar - LAST Conference 2015 Introducing Theresa 4 @teresitatheresa https://au.linkedin.com/in/tessn
- 5. Theresa Neate & Bharat Sangekar - LAST Conference 2015 “Agile” vs agile 5 More reading @ James Shore’s blog: http://bit.ly/1UIIJ7Y
- 6. Theresa Neate & Bharat Sangekar - LAST Conference 2015 Some differences between agile and traditional testing http://pixshark.com 6
- 7. Theresa Neate & Bharat Sangekar - LAST Conference 2015 Shifting quality to the left - the mindset credit: http://www.growingagile.co.za/ 7
- 8. Theresa Neate & Bharat Sangekar - LAST Conference 2015 Workshop - tester touch points 8 image credit: Anand Bagmar, ThoughtWorks
- 9. Theresa Neate & Bharat Sangekar - LAST Conference 2015 Famous 5 words... 9 ● Five words every tester is afraid to face after a release? ○ How did this slip testing? (https://www.youtube.com/watch?v=j-zczJXSxnw) ● Now imagine a developer’s response to this, famous 5 words: ○ It works on my machine. ● The question is not: ○ How did this slip testing? ● The question is: ○ How did the team not address the technical debt?
- 10. Theresa Neate & Bharat Sangekar - LAST Conference 2015 Shifting Quality Left 10 ● Testing that enables Agility. ○ Building quality in code. ○ Tester to be an integrated part of a self organised team. ○ Tests to uncover ambiguous requirements. ○ Tests to uncover technical debt. ● What stays? ○ Context driven concepts and heuristics-based techniques. ● What changes? ○ Focus on the learning & the doing, not the planning of the doing. ● Who tests? ○ You Do. ● But WHY, you ask? ○ I am glad you asked.
- 11. Theresa Neate & Bharat Sangekar - LAST Conference 2015 Different Roles, Different Strokes 11
- 12. Theresa Neate & Bharat Sangekar - LAST Conference 2015 Depth of Field ~Fabio Pereira 12 http://tinyurl.com/c6yk4bg Depth of field (DoF) - is the distance between the nearest and the farthest objects in a scene that appear acceptably sharp in an image.
- 13. Theresa Neate & Bharat Sangekar - LAST Conference 2015 Shallow Depth of Testing ~Fabio Pereira 13 Depth of Testing (DoT) - is the distance between the nearest and farthest components that get visited during the execution of a test. Shallow Automated tests = Cheaper + Faster. http://fabiopereira.me/blog/2012/03/18/introducing-depth-of-test-dot/
- 14. Theresa Neate & Bharat Sangekar - LAST Conference 2015 Case study - Deep Impact Typical Data - driven application. Legacy product. Linq2SQL framework. Rich Windows UI. Manual testing, Auto tests at UI layer to check against the database. Auto tests took 2 days to run. Reset the database before test. 14 UI ● No auto tests at UI. ● Build service layer to describe events. ● Tests not to run against database. ● Auto tests at business layer by abstracting everything north of Linq. ● Test against hibernate. ● Build optimizing compiler for Linq. ● Focus was on testing business operations at the service/business layer. ● Can we do Business Driven Development (BDD) at the service layer? ● Subject Matter Expert (BA) and Technical Tester define and write tests at service layer to drive the development aimed at defect prevented. ● Waste? What Waste. No tech debt. ● Tests took minutes to run not hours or days. ● Very heavy collaboration. ● No ambiguity.
- 15. Theresa Neate & Bharat Sangekar - LAST Conference 2015 What’s the best automation tool to shift quality left? Cucumber, Specflow, Selenium, Sahi, Watir, Fitnesse, JBehave, Concordion, Geb, Groovy, Spock, Fit, FitNesse, Spock, ScalaTest, Spec 2, RSpec, Protractor… ...and then some. 15 The right tool is one that gets the best support from your team.
- 16. Theresa Neate & Bharat Sangekar - LAST Conference 2015 Type of Shift Left testing The past Traditional = Unit + Integration Also, the past Incremental = Development Testing + Operational Testing Where we are: Agile/DevOps = Test Driven Dev, Behaviour Driven Dev The future: Model Based = Testing Executable requirements, Architecture & Design models. 16
- 17. Theresa Neate & Bharat Sangekar - LAST Conference 2015 To Summarise Testing that enables Agility. Move away from: It works on my machine. How did this slip testing? Embrace: How did the team not address the technical debt? Tests to uncover ambiguous requirements. Tests to uncover Technical Debt. What else: QA’s do Quality analysis, not assurance. Who tests? You do. Empower the tester to help Shift Quality Left. 17
- 18. Theresa Neate & Bharat Sangekar - LAST Conference 2015 Recommended reading/study: Use your rediscovered curiosity, and learn! “ThoughtWorks Anthology” v1 (2008) “Agile Testing” (Janet Gregory & Lisa Crispin) “Evil Tester” blog and courses (Alan Richardson) “Explore it!” (Elizabeth Hendrickson) Online technical courses on Udemy, Code School, CodeAcademy, etc. All the above authors’ blogs, Twitter accounts, webinars, etc. Keep attending conferences and meetups to LEARN, not just network, and ask questions 18
- 19. Theresa Neate & Bharat Sangekar - LAST Conference 2015 In closing 19
- 20. Theresa Neate & Bharat Sangekar - LAST Conference 2015 20 Questions?
Notas del editor
- 30 sec
- 1 min
- 30 sec Start the conversation with my name, turns out my name has been a good conversation starter. I don’t own a mankini. Worked across the spectrum of product development and consulting roles in medium size to large organizations in 3 countries.
- 30 sec 20 years in QA, 10+ years in software testing, of which 7 of which in agile Experienced test lead / manager but as agilist focus on hands-on and influencing, not “managing”
- 3 min This is a fairly well-know story in agile circles Back in the 40's, the story goes, American troops landed on a remote island. The natives of the island had never seen modern civilization before, and were amazed by the men and materials Allied forces brought by the island. They watched the troops set up an airstrip and a tower, don headphones, and call great metal birds filled with valuable Cargo down from the heavens. When the bird landed, shares of the Cargo were distributed to all of the islanders, bringing prosperity and comfort. One day, the troops left, and the great metal birds stopped arriving. Missing their Cargo, the islanders made their own airstrip out of woven bamboo. They constructed a tall platform, placed their chief on the platform, and had him don coconuts carved to look like headphones. But no matter how hard they tried, the great metal birds never returned. “The tragedy of the cargo cult is its adherence to the superficial, outward signs of some idea combined with ignorance of how that idea actually works. In the story, the islanders replicated all the elements of cargo drops--the airstrip, the controller, the headphones--but didn't understand where the airplanes actually came from.” We are going to talk about the rituals of agile testing but we ask that these not be done without their understanding.
- 3 min LAST - as seasoned agilists you will know this already, but to recap: The tester is involved from the very beginning, right from analysis, through dev and to testing and done No testing PHASES, but we still have testing TYPES Due to no phases, no strict entry criteria, testing should occur ASAP But we do have exit criteria, or quality standards for our testing TYPES No separate testing team, but a co-located tester on each delivery team Therefore reduces the need for a hierarchy, test lead, test manager - you will always be hands-on We are all peers Less documentation because everything should be “signed off” as you go This applies to defects too LOTS of automated testing - automated repetitive tasks and reserve manual testing for exploratory or cognitive testing In Agile testing, you are shifting quality to the left because you are involved and provide feedback early
- 2 min As one starts moving away from mimicry only, and one begins to understand more about the tester’s role, these are salient points that form part of the team’s mindset.
- 7 min Now let’s talk about a few of the rituals Groups of 4: BA, Dev, Tester & Product Owner Story AS a bank customer I want to change my PIN So that I can protect my privacy Conclusion: 1) an example of adding value in story definition 2) an example of adding value in development 3) an example of adding value during handover/shoulder check 4) an example of adding value during story testing
- 2 min
- 2 min .So what changes and what stays in the process of shifting quality tests?
- 3 min You think they have figured out yet the boundaries of what a Agile Tester does? Metservice & MYOB examples, tester playing BA and tester playing Iteration Test Manager Test Automation. Aus Post DDC example Different automation tools for different projects accessibility environment setups Microservices, different layers of automation testing. You are the glue that holds the development pieces together.
- 1 min You think they have figured out yet the boundaries of what a Agile Tester does? Metservice & MYOB examples, tester playing BA and tester playing Iteration Test Manager Test Automation. Aus Post DDC example Different automation tools for different projects accessibility environment setups Microservices, different layers of automation testing. You are the glue that holds the development pieces together. Community of Practice. Testing has become sexier, you would need to too. No more death by boredom, this is fun. Relate this back to Theresa’s culture points and hand it back to her.
- 3 min You think they have figured out yet the boundaries of what a Agile Tester does? Metservice & MYOB examples, tester playing BA and tester playing Iteration Test Manager Test Automation. Aus Post DDC example Different automation tools for different projects accessibility environment setups Microservices, different layers of automation testing. You are the glue that holds the development pieces together. Community of Practice. Testing has become sexier, you would need to too. No more death by boredom, this is fun. Relate this back to Theresa’s culture points and hand it back to her.
- 3 min Client Layer - Browser Presentation Layer - MVC, Web Forms, Win Forms, WPF Data Access Layer - ADO.NET, Linq2Sql, Entity Farmework. Deep Impact - Typical data driven application writing tests against database. Look at the database. Bad thing, whole bunch of UI tests to check against the database. Reset the database before each test,. Build an optimizing compiler for Linq - declare the intent of the business operations that you are trying to do - Payroll. - Removed the database from the equation entirely, testing business layer by abstracting everything north of Linq. Linq2SQL is a data access layer - hibernate. Describe all the database operations at a level that abstracts the way - testing against the hibernate. SQL Server CE WinForms and WPF, C#. Greenfield project - build the service layer to describe events. Don't run against database. Payroll - 500 people had to check if the payroll account was available, each service, don't rewrite the code. Replace the 500 nodes by 1 node. - Performance gains. Using Database vs using domain. Push testing to the domain level, completely remove the database.
- 1 min So now I know what’s expected of me to have agile mindset, but what’s my technical toolkit Explain the open source tools and their implementations. Elaborate on why is it important to choose tools that are open source have developer support.
- 2 min
- 1 min
- 30 sec Only if newbies in the room: You never know enough or know it all Be willing to learn
- 1 min In the last 30 minutes we hope to have demonstrated the difference between cargo cult “agile” testing and meaningful, understanding agile testing & shifting quality left
- 5 min