Seven Fundamentals of a Successful Testing Team
- 1. W9 Test Automation 5/10/17 13:45 Seven Fundamentals of a Successful Testing Team Presented by: Greg Paskal Ramsey Solutions Brought to you by: 350 Corporate Way, Suite 400, Orange Park, FL 32073 888-‐-‐-‐268-‐-‐-‐8770 ·∙·∙ 904-‐-‐-‐278-‐-‐-‐0524 -‐ info@techwell.com -‐ http://www.starwest.techwell.com/
- 2. Greg Paskal Greg Paskal is a natural innovator, pioneering new approaches across the technology landscape. Greg enjoys mentoring others in highly sustainable, maintainable approaches to manual and automated testing. The author of Test Automation in the Real World and a variety of StickyMinds.com publications, Greg can be heard on the TestTalks podcast with Joe Colantonio. Greg is a frequent speaker at conferences, including STAREAST, STARWEST, QA Trailblazers, and the Automation Guild. Greg founded the Open Test Technology Forum to encourage collaboration and to focus on greater quality across the SDLC. Learn more about Greg at GregPaskal.com, METSTesting.com, RealWorldTestAutomation.com, and MissionWares.com.
- 3. T E C H N O L O G Y T E A M Seven Fundamentals of a Successful Testing Team Presented By: Greg Paskal
- 4. T E C H N O L O G Y T E A M
- 5. T E C H N O L O G Y T E A M
- 6. T E C H N O L O G Y T E A M https://www.ted.com/talks/simon_sinek_how_great_leaders_inspire_action
- 7. T E C H N O L O G Y T E A M 5 Fundamental #1 – Foundations of Testing Why Software Testing Ø Reduce Risk Ø Protect Brand Ø Ensure Expectations
- 8. T E C H N O L O G Y T E A M 6 Fundamental #1 – Foundations of Testing Build on sound testing practices
- 9. T E C H N O L O G Y T E A M 7 Fundamental #1 – Foundations of Testing Positive Negative Boundary Build a common vocabulary
- 10. T E C H N O L O G Y T E A M 8 Fundamental #1 – Foundations of Testing Wrong focus Making it up as you go Reinventing Test Engineering Common Foundation Traps
- 11. T E C H N O L O G Y T E A M
- 12. T E C H N O L O G Y T E A M 10 Fundamental #2 – Manual Test Strategy http://www.METSTesting.com
- 13. T E C H N O L O G Y T E A M 11 Fundamental #2 – Manual Test Strategy • Critical • High • Medium • Low Tires Four Condition Pressure Balanced Critical High Medium Low Actions can be prioritized by importance such as…
- 14. T E C H N O L O G Y T E A M
- 15. T E C H N O L O G Y T E A M 13 Fundamental #3 – Execute the Strategy Day in the life of our typical manual tester - Check for new release - Standups - Check for re-test of fixed defects - Run METS Critical Test - Exploratory Testing - Documents they should create
- 16. T E C H N O L O G Y T E A M 14 Fundamental #3 – Execute the Strategy Encouraging Ownership - Build champions within your team. - Talk about how they are using their tools. - METS - Exploratory - Defects found using Positive, Negative and Boundary tests.
- 17. T E C H N O L O G Y T E A M 15 Fundamental #3 – Execute the Strategy http://www.METSTesting.com - Test most critical to least critical - Test as much as time allows - METS is awesome for exploratory testing.
- 18. T E C H N O L O G Y T E A M 16 Fundamental #3 – Execute the Strategy - Re-writing test cases for every release Common QA Traps - “I just” & “I don’t care about” mindset - A love affair with tools
- 19. T E C H N O L O G Y T E A M
- 20. T E C H N O L O G Y T E A M 18 Fundamental #4 – Automation Methodology Why Test Automation
- 21. T E C H N O L O G Y T E A M 19 Fundamental #4 – Automation Methodology Consistent Execution Reveals Inconsistency A manual tester confidence tool.
- 22. T E C H N O L O G Y T E A M 20 Fundamental #4 – Automation Methodology Build on a sound Manual Testing Strategy Make sure you’re actually testing something
- 23. T E C H N O L O G Y T E A M 21 Fundamental #4 – Automation Methodology What OS and Language to develop in? What Browsers and Devices?
- 24. T E C H N O L O G Y T E A M 22 Fundamental #4 – Automation Methodology Automation Reality Check - Find it in one, find it in all environments - Not a replacement for Manual Testers - Automation demos sell software but rarely represent reality
- 25. T E C H N O L O G Y T E A M 23 Fundamental #4 – Automation Methodology Common Test Automation Traps - Nothings free in Test Automation - Be ready for the expense - Consultant built with no handoff plans
- 26. T E C H N O L O G Y T E A M
- 27. T E C H N O L O G Y T E A M 25 Fundamental #5 – Building Automation Automate the Critical Tests
- 28. T E C H N O L O G Y T E A M 26 Fundamental #5 – Building Automation
- 29. T E C H N O L O G Y T E A M 27 Fundamental #5 – Building Automation Build your automation to be maintainable - Test assets managed and stored consistently (Scripts, Libraries, Drivers) - Consistent naming convention (Tests, Objects, Etc.) - Mirror the physical application when organizing - Avoid abbreviations - Logical groupings - Consistent across projects
- 30. T E C H N O L O G Y T E A M 28 Fundamental #5 – Building Automation - Automated tests should be traceable to manual tests Common Traps when Building Automation - More complex than the thing being tested - Tied to a specific User, Computer, Credentials - Overly complicated to use - No historical reporting capabilities
- 31. T E C H N O L O G Y T E A M 29 Fundamental #5 – Building Automation Common Traps when Building Automation (Continued) - ROI Roller Coaster
- 32. T E C H N O L O G Y T E A M
- 33. T E C H N O L O G Y T E A M 31 Fundamental #6 – Manual Tester and Automation Manual Tester Activities - Run test automation daily - Same time - Same environment(s) - Same order - Regardless of new code or build
- 34. T E C H N O L O G Y T E A M 32 Fundamental #6 – Manual Tester and Automation Learning the Application “Personality” Cooperative Always Runs Perfect Consistent Predictable Stubborn Temperamental to Run Inconsistent Unpredictable Tired Slow to Run Latent Unpredictable Strict Specific Run Conditions Unforgiving Predictable
- 35. T E C H N O L O G Y T E A M 33 Fundamental #6 – Manual Tester and Automation - Run Again - Analyze for identical results When Test Automation Fails - Identify flaky automated tests flaky test: a test, manual or automated, producing different results when executed upon the identical codebase
- 36. T E C H N O L O G Y T E A M 34 Fundamental #6 – Manual Tester and Automation Common Traps When Manual Testers Use Automation - Required to become command line experts - Executing on their local machine - Disable browser auto updates
- 37. T E C H N O L O G Y T E A M
- 38. T E C H N O L O G Y T E A M 36 Fundamental #7 – Important Partnerships Working Together - QA & Automation Engineer - QA, Automation & Dev Engineer - QA, Automation, Dev & Ops Engineer
- 39. T E C H N O L O G Y T E A M 37 Fundamental #7 – Important Partnerships New Testing Opportunities New Automation Opportunities Keeping These Partnerships Healthy
- 40. T E C H N O L O G Y T E A M 38 Fundamental #7 – Important Partnerships Common Traps when building Partnerships - QA becoming the “Software Police” - Living up to the “Technologist Stereotype” - Squash Imposter Syndrome
- 41. T E C H N O L O G Y T E A M Final Thoughts
- 42. T E C H N O L O G Y T E A M Interested in Test Automation? Greg shares from 30 years of experience in “Test Automation in the Real World”. RealWorldTestAutomation.com Contact Information Need a better Manual and Automated Test Strategy? Learn more about Greg’s Minimal Essential Testing Strategy. METSTesting.com I would enjoy hearing how you’re using the teachings from this presentation. Greg Paskal