This document discusses various types of software testing and their purposes. It covers unit testing, snapshot testing, property-based testing, contract testing, mutation testing, stress/load testing, chaos testing, and testing for different environments including backend, frontend, and cloud-native applications. The key points made are that different types of testing are needed to have confidence a solution works, catch regressions, avoid breaking consumers, ensure survivability of failures, and build the right product. Testing approaches must evolve with architectural changes like moving to the cloud. Isolation is important for hardening production systems.

1. Hardening
Diego Pacheco

3. Why Test matters?
o How do we Know the solution works?
o How do we know still working ?
o How do we know if we are breaking consumers ?
o How do we know we can survive failures in prod ?
o How we do know we are building the right product?

4. Why Test matters?
o How do we Know the solution works (Confidence)?
o How do we know still working (Automation + Regression)?
o How do we know if we are breaking consumers (Contract Testing)?
o How do we know we can survive failures in prod (Chaos Testing) ?
o How we do know we are building the right product (A/B/n Testing)?

5. Test & Design Relationship

6. Design is strategic

7. Why it matters?

8. Tooling & Test Diversity

9. Snapshot Testing
o Enhance Unit Testing for some
scenarios.
o Reduce typing
o Increase coverage
o Perfect for Design systems /
Components.
o Requires good tooling
o Could be great or useless.
o For Frontend: Jest(React) is super
awesome.

10. Snapshot Testing
https://jestjs.io/

11. Property-Based Testing
o Enhance Unit Testing for some
scenarios.
o Reduce typing
o Increase coverage
o Focus on Properties.
o Inputs got Generated.
o From Functional Programing
o Quick Check Haskell
https://jqwik.net/

12. Property-Based Testing
https://jqwik.net/

13. Contract Testing
o Perfect for SOA / Microservices
o Consumer Driven Tests
o Provider
o Consumer
o Re-use
o Does not depend on specific tool
o Junit + mocks (provider)

14. Contract Testing
o Service Provider should know
they consumers
o How do you the right
design?
o How we do proper gov?
o Other options: Swagger /
OpenAPI

15. Mutation Testing
https://pitest.org/
o Line coverage has limitations
o Uncover bugs | improve the tests.

16. Mutation Testing
https://pitest.org/

17. Stress/Load Testing
o Cost Effective
o Uncover Leaks | Inefficiencies
o More with Less
o Improve User Experience
o Important for CI/CD
o Can also help you with chaos
testing (Assertions).
https://gatling.io/docs/current/

18. Stress/Load Testing
https://gatling.io/docs/current/

19. Chaos Testing
o Everything fails all the time.
o Make sure things keep
working in production (cloud).
o Simian Army | Gremlin
o Simple Linux Tools
o Theories and Assertions (ST)
https://github.com/Netflix/SimianArmy

20. Chaos Testing
https://principlesofchaos.org/?lang=ENcontent

21. Chaos Testing
https://principlesofchaos.org/?lang=ENcontent

22. Testing Pyramid: Backend (Before Cloud)

23. Testing Pyramid

24. Trophy is all about Frontend!

25. Enter the Cloud: Changes everything!

26. Enter the Cloud: Changes everything!

27. How is that different from testing?

28. Spectrum: Hardening production.

29. Isolation is key!
https://aws.amazon.com/builders-library/automating-safe-hands-off-deployments/

30. Hardening Production!

31. Production: Is for Everybody or...

32. Thank you
Diego Pacheco