Changes for page Testing

Summary

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

Details

Page properties

Content

...	...	@@ -1,7 +1,18 @@
1		-* **Ultimate Goal**: Reduce costs and increase productivity.
	1	+=== Foreword ===
	2	+
	3	+(% style="text-align: justify;" %)
	4	+The chapters presented here are a concise summary of more theoretical and high-level knowledge. It is recommended that you are familiar with writing very basic tests and mocks, and understand the concepts of polymorphism and [[dependency injection>>doc:Software Architecture.Dependency Injection.WebHome]].
	5	+
	6	+=== ===
	7	+
	8	+=== General ===
	9	+
	10	+* **Ultimate Goal** of testing: Reduce costs and increase productivity.
2	2	* **Definition 'Production Code':** Code that provides functionality to meet project requirements.
3	3	* **Definition 'Test Code':** Often referred to as "tests", it is written to verify the correct functionality of the production code.
4	4
	14	+=== ===
	15	+
5	5	=== Benefits of Testing ===
6	6
7	7	* **Quality Assurance**
...	...	@@ -11,6 +11,16 @@
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		-)))
	25	+** Tests serve as the most current form of code documentation, capturing the expected behavior of the production code in its present state.
	26	+
	27	+=== ===
	28	+
	29	+=== What should be tested? ===
	30	+
	31	+(% style="text-align: justify;" %)
	32	+Every functionality you expect the software to provide at any moment. You should test:
	33	+
	34	+* **Use Cases**
	35	+** Use cases defined in project requirements
	36	+** Lower-level use cases derived from the high-level project use cases. For example, expected behavior of functions, classes, modules, and components that users of the software do not see.
	37	+* **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.