Use testing to Develop Better Software Faster
summary
Argues that testing must run throughout the DevOps cycle and gives concrete practices: use JUnit 5 and the right tool for the job (Mockito/WireMock, RestAssured/Postman, Cucumber/Serenity, JMeter/Gatling/Locust), write failing tests first (TDD) and prefer fast unit tests guided by the test pyramid. Cites painful real cases: repositories with zero tests, a flaky 700-test suite that nobody dared delete, ignored tests left for years, and recommends fixing or deleting flaky tests and keeping tests fast and descriptive.
AI-written summary · about
chapters (19)
- 0:00Start
- 4:06Holistic Testing
- 5:18Testing Activities
- 5:40Decision Diagram
- 6:16Tdd
- 6:44Tdd for Bug Fixing
- 7:18What Could Possibly Go Wrong
- 10:31Inputs Are Fun
- 12:40The Test Pyramid
- 17:16Unit Testing
- 17:56Can I Use Selenium To Test Endpoints
- 18:23Can I Use Cucumber To Do Performance Tests
- 22:21What Not To Do
- 26:35Achievement Unlocked
- 27:32Meaningful Names
- 28:10Readability
- 33:04Tests without any Assertions
- 33:16Tests That Will Never Fail
- 35:04Testing Multiple Things in a Row
related talks
57mAdvanced Testing Techniques: Tips from the trenches
48mA Reflection on Software Testing
01h 05mMicrotesting
48mTesting is Confidence - A Developer's Perspective
58mTesting Strategy - New Model, Better Outcomes
41mTesting done right: From bugs to brilliance
02h 46mThe Joy of Testing
29mTesting Applications - How to Do It Better?