Ad
More Related Content
What's hot (20)
Viewers also liked (20)
Ad
Similar to Why Automated Testing Matters To DevOps (20)
Ad
Recently uploaded (20)
Why Automated Testing Matters To DevOps
- 1. Automated Testing is a Pain in My ____ Paul Merrill @dpaulmerrill [email protected] beaufortfairmont.com
- 2. What is your worst experience with automated testing?
- 3. What is automated testing?
- 4. Automated Testing: A process that stimulates a system & reports whether expectations are met
- 5. Types of Automated Testing
- 6. Unit Tests • Written by developers • Intimate with code under test • ONLY interact with unit under test • Mock everything else • May influence design • May expose design concerns • Run FAST (hundreds in secs on dev machine)
- 8. Integration Tests • Intimate with code under test • May or may not interact with other systems • May use mocks, simulators, scaffolding • May influence design • May expose separation of concerns • May or may not run on Dev machines • May be fast or slow • May or may not encapsulate a user function
- 9. Integration Tests System Under Test (SUT) Component A Component C Component D Component B
- 10. Integration Tests - Example 1 System Under Test (SUT) Reporting Service Authentication Broker Parsing Service
- 11. Integration Tests - Example 2 System Under Test (SUT) Restful Server User Interface Database Request
- 12. End to End (E2E) Tests • Interacts with System as an “Actor” would • Assumes similar environment to production • May or may not run on Dev machines • Hopefully fast, usually slow (minutes & hours)
- 13. End to End (E2E) Tests
- 14. What does bad automated testing look like?
- 15. Bad Automated Testing Causes unexpected work, like… – “You filled up the disk” – “The network was flooded” – Data leaks – Tests fail because of poor design – Cascading failures – Numerous false positives – Inconsistent results
- 16. What does good automated testing accomplish, how is it different?
- 17. Good Automated Tests… Expedite work, like… • “The tests showed me where to look” • Expose error states – java.lang.StackOverflowError (bad recursion) • High signal-to-noise ratio – No cascading, except in serious cases – Few false positives • Act as or establish a “Source of Truth” – Tests fail here, but not there – Tests fail with this data, but not that data • Isolate problem scope
- 18. Good Automated Tests… Smooth edges via friction Friction: • Failing tests • Failing systems • Identifying system limits • Forcing consideration of constraints, scenarios, cases Smoothed: • Pronounce or expose implied contracts
- 19. How does this affect you?
- 20. Follow the Value • Your role is, was, or is projected to be valuable to someone somewhere • Someone has decided: – Consumers won’t buy without your role OR – To speculate that value is increased by your role
- 21. Passing the Value The person who understands your value may not be the person who makes decisions Or The person who understands your value may not communicate it in a way that benefits you
- 22. If your value is obscured… You go home!
- 23. …So Increase & Promote Value • By using what you have: – Tests – Code – Systems – Communication • By digging deeper: – Peers – Customer – Investor – Manager
- 24. Checks and Balances • The code serves as a test case for the test • The code serves as a test case for the deployment • The tests serve as tests for the code • The tests serve as tests for the deployment • The deployment serves as a test for the code • The deployment serves as a test for the tests
- 25. Checks and Balances • Each touch-point presents opportunity for greater value through: – Efficiencies – Effectiveness – Goodwill – Making life easier for someone • Customer? • Investor? • User? • Peer?
- 26. Creating Value via DevOps Role • Use friction to create value • What is a failing (or passing) test telling you? • How can you create a better system based on feedback (like that from automated tests)?
- 27. “Release” The act of coding, testing & deploying
- 28. A Release Serves as… • A test of the market • A test of the customer • A test of the business (or business line) • A test of the investment • A collector of revenue (fuels the business) • A test of your role’s value
- 29. • Automated Tests • Deployments as Tests • Code as Tests • Releases as Tests Each giving feedback you are uniquely positioned to leverage to create value for the business. Tests…
- 30. Any test could be a pain in your ____ OR It could be an opportunity to create value in your systems and lines of business!