Skip to Content

Changes for page Testing Principles

Last modified by chrisby on 2024/04/01 12:52
From version 1.8
edited by chrisby
on 2023/05/29 11:58
Change comment: There is no comment for this version
To version 1.9
edited by chrisby
on 2023/05/29 12:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -17,3 +17,4 @@
17 17  * **'Program testing can be used to show the presence of bugs, but never show their absence!' **(Edsger W. Dijkstra).
18 18  ** Follow good testing practices to avoid a large number of bugs, but be aware that bugs may still occur and be prepared for them.
19 19  * **Requirement fulfillment over specific solutions:** Don't limit tests to a specific solution when multiple valid solutions exist. Test for compliance with solution requirements, not the specific output. This provides flexibility by accepting any valid solution. For example, in pathfinding problems, minimum travel costs validate a solution, not the particular path chosen.
20 +* **Conciseness**: Tests should be small, fast, and specific, which means, for example, that we don't need a million test data points, but maybe 5, each covering just one specific use case or border case. The exceptions are load/stress tests, which are specifically designed to send huge amounts of data to an application.