Testing Testing everywhere
Download as PPTX, PDF0 likes980 views
Testing tools and strategies for various types of tests were discussed, including: 1. Unit testing with libraries like Nose, API testing with Request, and web testing with Selenium. 2. Performance testing using MultiMechanize to run load tests and generate reporting. 3. Behavior-driven development (BDD) using Lettuce to write tests with a given-when-then structure and integrate with Request and Selenium tests. 4. The document recommended a Python-based testing strategy for components, integration, end-to-end, and performance tests.
Testing Testing everywhere
- 1. Testing, testing everywhere! Toni Robres Turón @twiindan
- 2. {name: Toni Robres} {role: QA}
- 4. Sometimes diversity is not good
- 5. Sometimes diversity is not good
- 7. Which characteristics should have the perfect testing tool?
- 13. Testing Activities Unit Testing Acceptance Testing Web Testing Performance Testing Test Definition
- 14. Unit Testing • Nose – Extended framework for python unit testing – Easy to write and run tests – Provides coverage – Provides profiler – Test can be organized – Include tools for testing
- 17. Coverage
- 18. API REST Testing • Request: HTTP For humans – Library to perform API REST requests – Easy to use – Basic and Oauth Authentication – Cookies support – Multipart Files Upload – Session objects – Verify SSL Certificates – Proxies – Can be integrated with nose and lettuce
- 19. Basic usage
- 20. Usage • Query Parameters defined as Python Dict: • Custom headers defined as Python Dict
- 21. Usage Basic authentication Content body defined as Python Dict
- 22. Usage • Upload a file: • Cookies • Cookies
- 23. Web Testing • Selenium – Most extended library to test Web GUI – Suport Firefox, Chrome and Internet Explorer – Can be integrated with nose and lettuce – Integrated with CI – Grid support – Cookies support
- 24. Selenium • How it works? – Locate the Elements • By id, CSS, XPATH, name, Class... – Select Elements • Assert properties – Interact • Send keys • Click
- 25. Basic Example
- 26. Page Object Pattern • Language Neutral Pattern for representing a web page in an Object Oriented manner • Necessary for survive in Selenium – Increase maintanability – Increase readability – Abstract web page logical from tests
- 29. Web Testing • What happen with selenium IDE?
- 30. Perfomance Testing • MultiMechanize – Runs concurrent Python scripts to generate load against service – Reporting as Jmeter compatible – Easy configuration – Can reuse Custom Request library – Multithreading and multiprocessing – Distributed
- 31. Config File
- 32. Script File
- 34. Multi Mechanize Stats • test summary • transaction timers • custom timers (from instrumented client code) • time-series/interval data • counts • rate/throughput • response times • average, min, max, stdev • percentiles (80th, 90th, 95th)
- 35. Graphs
- 36. Graphs
- 37. Graphs
- 38. Summarizing • I can do tests in all Levels: – Web – API – Performance • What happen with test Definition and test Execution stats?
- 39. Jira / TestLink / IBM
- 40. BDD • Using examples to create a shared understanding and surface uncertainly to deliver software that matters. • Define the software behaviour: – Given (Preconditions) – When (actions) – Then (Post conditions)
- 41. Lettuce • BDD Tool for Python • Easy to integrate with tests developed with Request and Webdriver • Data driven • Using decorators to execute functions that describes the software behaviour
- 42. Feature Example Scenario Outline: Retrieve the geolocation with city name given Given a <city> name When I request the geoencoding of the city Then I obtain the <city> name with the <country_code> Examples: | city | country_code | | Barcelona | ES | | Paris | FR | | San+Francisco | US |
- 43. Coding example
- 44. Test Runner and report
- 45. Web Usuarios SMS Web Soporte Backend BBDD
- 46. Que probar y con que?
- 47. Que probar y con que? • Unit testing all components • Component test: – Backend Requests – Webs Webdriver mocking the backend – Mobile Appium mocking the backend • Integration: – Webs and backend – Mobile and backend – Backend with SMS plattform • E2E
- 48. Bonus Track • What happen if my component has different interface than API REST? – All the components always have an input – For example • Rabbit Pika, Kombu • MongoDB Pymongo • Redis Python Redis client • MySQL sqlite, sqlalchemy
- 49. Overview • Using Python for all testing activities – Easy to integrate – Can reuse common libraries – Only needs learn one tool – Collaboration between development and testing – Community
- 50. Result
- 51. Questions?
Editor's Notes
- #4: Three tools for the frontend testers under UI Seven for the backend testers in their APIs Nine for the Performance testers doomed to kill systems One for the dark load of software enginering One tool to rule them all, One tool never found by testers
- #5: You can choose an incorrect tool to testing Sometimes choose an ineficient tool
- #8: Fleixibility
- #15: Organized (fixtures, suites, packages...) Tools (asserts, raises, timers...) Tags DOCTEST for documentation Hooks (before, after) Parallel testing Results in Xunit format XML
- #24: Remote WebDriver
- #27: Language Neutral Pattern for representing a web page in an Object Oriented manner
- #35: vtest summary transaction timers custom timers (from instrumented client code) time-series/interval data counts rate/throughput response times average, min, max, stdev percentiles (80th, 90th, 95th)