Automated Exploratory Tests

619 views

Published on

Autoamted Exploratory Tests - evolution from functional to exploratory tests

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
619
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
11
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Automated Exploratory Tests

  1. 1. AutomatedExploratoryTests<br />Zbyszek Moćkun<br />
  2. 2. Automatedtestsevolution for webapplication<br />Aim<br />
  3. 3. Fewwordsaboutprocess and environment<br />Introduction<br />
  4. 4. Methodologies, projects, …<br />Methodologies<br />Projects<br /><ul><li> Web Application
  5. 5. Content Management Systems (CMS)
  6. 6. Small and medium projects
  7. 7. No time and budget for automation
  8. 8. Agile methodologies: Scrum, Kanban
  9. 9. Release management
  10. 10. No time for regressiontests
  11. 11. Last sprint cumulation
  12. 12. ContinuousIntegration Environment</li></li></ul><li>Standard approach to automation<br />AutomatedExploratoryTests<br />
  13. 13. Automation TestsLifecycle<br />
  14. 14. Adventages and Disadventages<br /><ul><li>Writingautomated scripts require
  15. 15. Costs
  16. 16. Needinvestmentsatthebegining
  17. 17. Dependenciesbetweentests
  18. 18. Onlydefinedfunctionalityistested
  19. 19. Coverage
  20. 20. Lack of duplicationduringmanual test execution
  21. 21. Functionality</li></li></ul><li>Automatedtestsevolutionprocess<br />AutomatesExploratoryTests<br />
  22. 22. Whatshould we tests?<br />Twoperspective<br />User<br />Client<br />
  23. 23. Aspects<br />
  24. 24. Looking for a symptom<br />„Symptom is a departure from normal function or feeling which is noticed by a patient, indicating the presence of disease or abnormality.”<br />http://wikipedia.org<br />
  25. 25. Symptoms<br />
  26. 26. ReferenceSymptoms<br /><ul><li>Previousapplication data
  27. 27. Savedreference data
  28. 28. Otherversion of the same application (differentserver)
  29. 29. Compare data as parameter</li></li></ul><li>Roboty<br /><ul><li>Skrypty, które poszukują symptomów
  30. 30. Ten sam skrypt dla różnych projektów
  31. 31. Narzędzia/skrypty</li></li></ul><li>AutomatedExploratoryTests – new idea<br />Severaldifferentdefinitions:<br /><ul><li>Replay exploratorytestsexecutedmanually
  32. 32. Combinemanuall and automatedfunctionaltests
  33. 33. Chosensteps automation
  34. 34. ApplicationTestingwith data generator
  35. 35. Thereis no ATE, becauseexploratorytestsrequirehumanfactor</li></li></ul><li>AutomatedExploratory Test – definition<br />AutomatedExploratoryTestssupportsmanualexploratorytesting, don’tbased on specific test scenario, looking for high riskareas, exploreapplicationquicker and deeper, additionallytests areano accessible for testers<br />„Automated Tests do not provide complete information. They provide partial information that might be useful”<br />Cem Kaner<br />
  36. 36. AutomatedExploratoryTests- adventages<br />One tool<br />Containsallsymptoms<br />For allprojects<br />Quick to introduceintoproject<br />Easy for change management<br />Don’trequiregoodknowledgeabouttestedapplication, speedup learning process<br />ContinuousIntegration<br />Strongsolutionif we combinewith standard functionalautomatedtests<br />Migrationtests<br />
  37. 37. AutomatedExploratoryTests- example<br />
  38. 38. OpenSourceTools<br /><ul><li>Selenium II/WebDriver
  39. 39. Comparators (ImageMagick)
  40. 40. Validators (W3C)
  41. 41. Performance (JMeter, Proxy)
  42. 42. ProxyServers(BrowserMob)
  43. 43. Firefox/Firebug (NetExport, ConsoleExport, JS Console output redirector)
  44. 44. HAR Viewer (http://www.softwareishard.com/har/viewer/)</li></li></ul><li>Q&A<br />

×