Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Building The Blocks of Trust in Automation by Sneha Viswalingam

139 views

Published on

Having followed best practices from previous Selenium Conference talks, the Zoll Lifevest team was able to shift from flaky tests to stable and reliable automated tests. During that time, Sneha Viswalingam learned the importance of building trust in the test suite to unite the team as a whole. Once trust is established in the automated tests, it became crucial to the overall software development lifecycle.

In this talk, Sneha covers the following topics:

- Strategies that she used to make the tests reliable
- Trainings for the manual testers to contribute to the automation efforts
- Importance of having an Automation Test Reporting Dashboard
- Presenting the project status and test reports on a wallboard to reinforce trust

By implementing these steps in her organization, Sneha has built trust not only within the test suite but into the team as a whole.

Published in: Software
  • Be the first to comment

  • Be the first to like this

Building The Blocks of Trust in Automation by Sneha Viswalingam

  1. 1. @sviswalingam
  2. 2. @sviswalingam
  3. 3. @sviswalingam
  4. 4. @sviswalingam
  5. 5. @sviswalingam
  6. 6. @sviswalingam
  7. 7. @sviswalingam
  8. 8. @sviswalingam
  9. 9. @sviswalingam
  10. 10. @sviswalingam
  11. 11. @sviswalingam Sneha Viswalingam Test Automation Engineer Zoll Lifevest
  12. 12. @sviswalingam
  13. 13. @sviswalingam
  14. 14. @sviswalingam Anatomy of a Test Credits to @rantene
  15. 15. @sviswalingam
  16. 16. @sviswalingam
  17. 17. @sviswalingam Identify ● Look for a pattern ● Spot the flaky test ● Note them down
  18. 18. @sviswalingam Isolate ● Tag the flaky tests ● Run main test suite and flaky test suite separately
  19. 19. @sviswalingam
  20. 20. @sviswalingam Investigate ● Post mortem analysis ● Look for the root cause
  21. 21. @sviswalingam
  22. 22. ● Observe the tests for many runs ● If they pass continuously,then add them back to the main suite @sviswalingam
  23. 23. @sviswalingam
  24. 24. @sviswalingam Code committed to Repository Pull request created for commit Pull Request URL documented in JIRA ticket Push changes to master branch Automation Engineer makes required changes All Automation Team members review One Automation team member reviews Approved Framework Updates? NO YES NO YES Code Review Process
  25. 25. @sviswalingam
  26. 26. @sviswalingam
  27. 27. @sviswalingam
  28. 28. @sviswalingam
  29. 29. @sviswalingam Quality Assurance Leaders - Advocates for Success
  30. 30. @sviswalingam Software Developers - Design for Testability - Knowledge Sharing
  31. 31. @sviswalingam Test Engineers - Subject Matter Experts
  32. 32. @sviswalingam High Level Architecture Feature File Page Objects File Step definition File Test Scripts Automation Core Specflow Selenium C#
  33. 33. @sviswalingam Writing Feature Files ● Behavior Driven ● Phrasing Steps ● Title ● Style
  34. 34. @sviswalingam Tidy Gherkin ● Chrome App, easy to install ● No need to install an IDE ● Ease of use ● Free and Lightweight
  35. 35. @sviswalingam
  36. 36. @sviswalingam Knowledge Sharing ● Workflow of Automation CI ● Hands-on Test Execution ● Introduction to BDD ● Troubleshooting and Evaluating Automation Bugs
  37. 37. @sviswalingam
  38. 38. @sviswalingam
  39. 39. @sviswalingam
  40. 40. @sviswalingam
  41. 41. @sviswalingam Build your own Dashboard
  42. 42. @sviswalingam
  43. 43. @sviswalingam
  44. 44. @sviswalingam
  45. 45. @sviswalingam
  46. 46. Thank You!

×