Changes for page Testing

Summary

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

Details

Page properties

Content

...	...	@@ -1,7 +1,9 @@
1	1	* **Ultimate Goal**: Reduce costs and increase productivity.
2		-* **Definition 'Production Code':** Represents the actual software functionality designed to fulfill project requirements.
3		-* **Definition 'Test Code':** Often referred to as "tests," is written to verify the functionality of production code.
	2	+* **Definition 'Production Code':** Code that provides functionality to meet project requirements.
	3	+* **Definition 'Test Code':** Often referred to as "tests", it is written to verify the correct functionality of the production code.
4	4
	5	+=== ===
	6	+
5	5	=== Benefits of Testing ===
6	6
7	7	* **Quality Assurance**
...	...	@@ -11,6 +11,15 @@
11	11	* **Testable Design**
12	12	** Writing tests automatically enforces design best practices, resulting in a 'testable design' and higher quality code. Good code and architecture are testable, and vice versa.
13	13	* **Documentation**
14		-** (((
15		-Tests serve as the most current form of code documentation, capturing the expected behavior of the production code in its present state.
16		-)))
	16	+** Tests serve as the most current form of code documentation, capturing the expected behavior of the production code in its present state.
	17	+
	18	+=== ===
	19	+
	20	+=== What should be tested? ===
	21	+
	22	+Every functionality you expect the software to provide at any moment. You should test:
	23	+
	24	+* **User Cases**
	25	+** Defined in project requirements
	26	+** 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.
	27	+* **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.