Autoamted Exploratory Tests - evolution from functional to exploratory tests

1. AutomatedExploratoryTests Zbyszek Moćkun

2. Automatedtestsevolution for webapplication Aim

3. Fewwordsaboutprocess and environment Introduction

5. Content Management Systems (CMS)

6. Small and medium projects

7. No time and budget for automation

8. Agile methodologies: Scrum, Kanban

9. Release management

10. No time for regressiontests

11. Last sprint cumulation

13. Automation TestsLifecycle

15. Costs

16. Needinvestmentsatthebegining

17. Dependenciesbetweentests

18. Onlydefinedfunctionalityistested

19. Coverage

20. Lack of duplicationduringmanual test execution

22. Whatshould we tests? Twoperspective User Client

23. Aspects

24. Looking for a symptom „Symptom is a departure from normal function or feeling which is noticed by a patient, indicating the presence of disease or abnormality.” http://wikipedia.org

25. Symptoms

27. Savedreference data

28. Otherversion of the same application (differentserver)

30. Ten sam skrypt dla różnych projektów

32. Combinemanuall and automatedfunctionaltests

33. Chosensteps automation

34. ApplicationTestingwith data generator

36. AutomatedExploratoryTests- adventages One tool Containsallsymptoms For allprojects Quick to introduceintoproject Easy for change management Don’trequiregoodknowledgeabouttestedapplication, speedup learning process ContinuousIntegration Strongsolutionif we combinewith standard functionalautomatedtests Migrationtests

37. AutomatedExploratoryTests- example

39. Comparators (ImageMagick)

40. Validators (W3C)

41. Performance (JMeter, Proxy)

42. ProxyServers(BrowserMob)

43. Firefox/Firebug (NetExport, ConsoleExport, JS Console output redirector)