Changes for page Testing Principles

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -17,5 +17,5 @@
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		-* **Speed**: Tests should be small and fast, which means, for example, that there is no need to test million 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.
	20	+* **Fast**: Tests should be small and fast, which means, for example, that there is no need to test million 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.
21	21	* **Specific Assertions**: For example, you should assert exactly what type of exception is thrown or what error (message) is returned. If the assertion isn't specific enough, it might not be able to distinguish between similar problems, such as two exceptions of the same type, so it can't detect potential problems.