Test automation expert days
Download as PPTX, PDF2 likes890 views
This document discusses different types of software testing including unit tests, integration tests, and end-to-end tests. It emphasizes that code should be designed with loosely coupled and independently testable units, and each unit should be tested separately before testing how units interact. It also provides information on testing tools and frameworks like Jasmine and strategies like test-driven development.
Test automation expert days
- 1. Test Automation Oren Rubin - Testim.io
- 2. Who am I?
- 3. Who are you? ● Company specialty? o Backend? Frontend? Mobile? ● Current development? o how frequent are the releases? ● QA or dev team? o Write code or manage?
- 4. Software Architecture Class Q: How to write large scale applications? A: You don't, you aim for small reusable components
- 5. Systems are composed of Units Unit A Unit B Unit C
- 6. Units have interfaces Click HTTP Browser Web Server DB
- 7. Units are composed of smaller units Web Server DB Click Browser HTML JS CSS a.js b.js
- 8. Test each unit separately? Browser Web Server DB Test A Test B Test C
- 9. Test how the units interact? Browser Web Server Test A DB
- 10. Test how the units interact? Web Server DB Test C Browser
- 11. Test the entire flow? Click HTTP Browser Web Server DB
- 12. Testing Theory - La järɡən ● Unit Tests ● Integration Tests ● End to End Tests ● Functional Tests ● Smoke Tests ● Load Tests ● Acceptance Test
- 13. Testing Theory - La järɡən
- 14. Unit vs. Integration vs. E2E
- 15. Testing Theory Setup Stimuli Assertions Tear down Test starts Initial State Some State The Assertions can differ: Functional, UI, Timing, Memory consumption
- 16. Testing Theory Black Box ● Check against the API ● Can be done by others White Box ● Look inside (gory details) ● Usually same person
- 17. Testing Metrics Black Box ● Users stories ● Response time ● Memory consumption (memory leaks) White Box ● Code coverage ● Loop edge cases: o Never go in o Go in once o More than once
- 18. Test automation Unit Tests
- 19. Unit Tests.. find the diffs Bad Code ● Long methods ● Tightly Coupled ● Unreadable ● Hard root cause ● Use Global Good Code ● Short methods ● Loose Coupling ● Readable ● Easy bug detection ● Separation of Concerns Unit Tested Code ● Short methods ● Loose Coupling ● Readable ● Easy bug detection ● Separation of Concerns
- 20. Unit Tests Remember: Units tests helps you write better code Regression tests are a bonus!
- 21. Testing Theory - Unit Tests Setup Stimuli Assertions Tear down Test starts Initial State Some State Assertions ● State changed ● callbacks (methods) were called
- 22. Testing Theory - Unit Tests a =new A() a.f() assert(a.x = 5) Test starts Initial State Some State Assertions ● State changed ● callbacks (methods) were called
- 23. Test each unit separately? mock http Browser Web Server DB mock timers Test A Test B Test C
- 24. Unit Isolation Spies Stubs Mocks
- 25. Unit Isolation - if needed Fake ajax Fake timers Work asynchronously
- 27. Spies
- 28. Spy on functions
- 29. Spy on functions
- 30. Spy on functions
- 31. Spy filters
- 32. Spy Assertions
- 33. Spy Assertions
- 34. Stubs
- 35. Stubs
- 36. Stubs
- 37. Mocks
- 38. Jasmine ● Very simple ● Great docs: http://pivotal.github.com/jasmine/ ● Load is by an HTML scaffold ● Completely standalone ● Custom Matchers: expect('moshe').toBeMoshe(); ● Easy to filter tests ● Nested describe blocks (each has beforeEach)
- 39. Jasmine
- 40. Jasmine
- 41. Jasmine
- 42. Sinon
- 45. TDD 1. Write test 2. Test fails 3. Write code 4. Test passes 5. Refactor 6. Go to 2
- 46. Keyword driven tests e.g. cucumber
- 47. TDD can apply to Integration and E2E
Editor's Notes
- #4: One important goal is to get to know fellow friends in the industry.. and share knowledge