Changes for page Testing Principles

Summary

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

Details

Page properties

Content

...	...	@@ -1,3 +1,13 @@
	1	+What should be tested? ➡ Every functionality you expect the software to provide at any moment. You should test:
	2	+
	3	+* **User Cases**
	4	+** Defined in project requirements
	5	+** Use cases derived from the high-level project use cases. For example, expected behavior of functions, classes, modules and components that the user does not see.
	6	+* **Border cases** that could theoretically always occur, such as maximum/minimum values, nulls, invalid input, nulls, negative numbers, empty lists, values with special meaning, exceptions, etc.
	7	+
	8	+
	9	+=== Principles ===
	10	+
1	1	* **High Coverage**:
2	2	** **Code Coverage** Definition: The percentage of classes/methods/lines of code executed during testing. There is class coverage, method coverage and line coverage, the latter being the most important.
3	3	** **100% code coverage** is the goal. Untested code is insecure code and prone to bugs.