Automation is Easy! (python version)
Download as PPTX, PDF1 like1,493 views
The document discusses the importance and strategies of implementing automation for testing web pages using Python. It emphasizes starting with end-to-end tests, reviewing test plans, and utilizing independent unit tests while suggesting tools for various programming languages. Ultimately, it presents automation as a useful tool for test engineers, highlighting the necessity of having proper guidance and resources to ease the learning process.
More Related Content
![Selenide alternative in Python - Introducing Selene [SeleniumCamp 2016]](https://cdn.slidesharecdn.com/ss_thumbnails/seleniumcamp2016-selenidealternativeinpython-introducingselene-160226140611-thumbnail.jpg?width=560&fit=bounds)
![Kiss PageObjects [01-2017]](https://cdn.slidesharecdn.com/ss_thumbnails/kisspageobjects-01-2017-170113192904-thumbnail.jpg?width=560&fit=bounds)
Similar to Automation is Easy! (python version) (20)
Automation is Easy! (python version)
- 1. Automation is Easy or easy automation coverage of your web pages in Python 1
- 6. Effective Testing *= Testing with automated routine work
- 7. QA = Assistance in assuring Quality
- 8. QA applied to Testing = Making Testing Effective => using Automation :) where appropriate
- 9. But it’s hard, no?
- 11. Summary
- 12. Coverage Styles End to End style + more coverage in less time with less efforts during implementation + integration coverage Unit/One-feature-per-test style + in case of bugs, gives more complete report + easier to identify reason from the report => + less time and efforts in support
- 13. How many => => Only: + functional high priority use cases
- 14. Avoid => => No - style checks - low priority test cases (that user will not do on regular basis) - additional requirements, like “different kind of names for entities” <=
- 15. Implementing Automation • Project in progress, no Automation? 1. start with End To End style smoke integration tests 2. review and test plan 3. cover with “One feature”/“Unit” style independent tests
- 16. Implementing Automation • Project just started OR ready features are automated? 1. Test plan new features 2. Cover with “One feature”/“Unit” style independent tests 3. Add End to End integration smoke tests
- 17. Wasn’t it Easy? :)
- 18. How to start? • Choose language • Learn language (books, interactive tutorials, koans, etc.) • Choose Easy Tools • Find a mentor (friend, dev on your project, etc…) • Go :)
- 19. Choose language? • Have project? • choose language of project’s developers • Have no project but want to find work fast? • choose one of the most popular language • Have no project but want to code in your style, and it does not matter how long will you seek for the job? • choose language that fits you
- 21. koans + docs.seleniumhq.org + google.com = “You can do this in any language.”
- 22. Easy Tools? • Just a few examples… • Java: Selenide • Ruby: Capybara + SitePrism • Python: … (write you own or wait for stable version of Selene;)
- 23. No Tool for your language? • Have project? • ask project’s developers to write it for you • Have no project and lack of knowledge? • switch to language that has easy tools :) • Brave? • implement it by your own (see next lesson ;)
- 24. Can I start with no manual experience? Automation is just a tool, which can be pretty easy, as you saw:), so: • IF • you are smart and brave • have guys who will help you • know where to find “easy automation tricks&tools” • THEN • why not? :)
- 25. Just Remember… • Automation is NOT a separate Role • Automation IS A TOOL for Test Engineer to do his work effectively
- 26. Q&A ask more in this russian chat