paatestaussuunnitelma.md

@@ -32,32 +32,34 @@ Main functionalities are tested via Robot Framework, FMBT and manual testcases.
 Each test scenarios are created by following imaginary stories about clients using the application. For effective automation testing the stories follow an common storyline for a normal user.
 
 # TEST LEVELS
-1. Unit testing
-The programmer creates functional tests during the coding phase with Karma. Created test can be found here(functional testing).
-2. System testing
-Functional testing
+## 1. Unit testing
+* The programmer creates functional tests during the coding phase with Karma. Created test can be found here(functional testing).
+## 2. System testing
+### Functional testing
 
-Automated Robot Framework scenarios are performed in "SUT(System under test)" to find any new failures before integration(regressio).
+* Automated Robot Framework scenarios are performed in "SUT(System under test)" to find any new failures before integration(regressio).
 
-Manual test case pool is also created, executed and can be found here. "Contriboard" is the selected test project.
+* Manual test case pool is also created, executed and can be found here. "Contriboard" is the selected test project.
 
-Explorative testing is done during the development phase by programmers.
+* Explorative testing is done during the development phase by programmers.
 
-Regressio testing methods are fMBT. Model based testing formula can be found here
+* Regressio testing methods are fMBT. Model based testing formula can be found here
 
-Non-functional testing
+### Non-functional testing
 
-Stability will be tested with looped automation test running Robot Framework scenario tests. These tests are run in local client. All the stability test stats are saved for later inspecting and analyzing. Reliability and functionality is tested in addition.
+* Stability will be tested with looped automation test running Robot Framework scenario tests. These tests are run in local client. All the stability test stats are saved for later inspecting and analyzing. Reliability and functionality is tested in addition.
 
-Locust is used to test performance. Application is stressed with users and then tested how much the system can handle. This testing is done in Foreman test environment for realistic results.
+* Locust is used to test performance. Application is stressed with users and then tested how much the system can handle. This testing is done in Foreman test environment for realistic results.
 
-Security testing
+### Security testing
 
-Security
-3. Acceptance testing
-Collaborative Testing Sessions are used to validate product quality before moving it in production mode.
-Automated Robot Framework scenarios are again performed in SUT(System under test) or in "Foreman" environments to find any new failures before acceptance(regressio). This is also the smoke test phase.
-TEST ENVIRONMENT
+* Security
+
+##3. Acceptance testing
+* Collaborative Testing Sessions are used to validate product quality before moving it in production mode.
+* Automated Robot Framework scenarios are again performed in SUT(System under test) or in "Foreman" environments to find any new failures before acceptance(regressio). This is also the smoke test phase.
+
+#TEST ENVIRONMENT
 Testing tools
 Same scenarios are used for stability tests...