Mastering Software Testing: The good, The bad and The ugly
📩 Got questions? Want to connect?
📧 Email: [email protected]
🔗 LinkedIn: [Luis Daniel Mesa Velásquez]( / luis-daniel-mesa-velasquez )
☕ Love my content? Support my work!
💖 Patreon: [JumperCode]( / jumpercode )
💙 Ko-fi: [Buy me a coffee](https://ko-fi.com/luismesa)
Mastering Software Testing: The good, The bad and The ugly
Some characteristics of good tests:
1. Good tests verify the correctness of the code
2. Good tests help prevent regression
3. Good tests allow the software to evolve at a steady pace
4. Good tests define the boundaries of your system
5. Good tests act as executable pieces of documentation that are always current, unlike a wiki or sharepoint
6. Good tests guide design choices towards simplicity
7. Good tests allow continuous releases with confidence
8. Good tests allow you to cope with change
9. Good tests should stabilize your codebase, if you change something in a method without changing the test, then one or more of your tests should alert you by failing
10. Good tests deal with the past, the present and the future
Some characteristics of poor tests:
1. Poor test are brittle
2. Poor tests are complex
3. Poor tests are hard to maintain
4. Poor tests are cryptic
5. Poor tests are slow
6. Poor tests do not guide or document anything
7. Poor tests deal with the past and the present only