pre-test-plan.md

@@ -51,8 +51,8 @@
 | Usability | There are two games too close to eachother. The game view that's closer activates and the other doesn't. |
 | Stability | A game view crashes or loses power. The user can still go to other game views. |
 ## Back-end(Raspberry & RuuviTag)
-## Non-Functional Tests
-### Raspberry pi 3
+### Non-Functional Tests
+#### Raspberry pi 3
 | Target | Description | Additional information |
 | -------- | -------- |-------- |
 |Raspberrys Hardware|Testing Raspberry pis fucntion under maximum stress||
@@ -64,7 +64,7 @@
 |Raspberrys Software|Testing the distance from which the tag registers to the raspberrys interface||
 |Raspberrys Software|Security testing|Network security testing and software exploitation testing|
 
-### RuuviTag
+#### RuuviTag
 | Target | Description | Additional information |
 | -------- | -------- |-------- |
 |Ruuvitags Firmware|Testing different firmwares on ruuvitags||
@@ -75,14 +75,16 @@
 |Ruuvitags Hardware|Bluetooth signal distance testing||
 |Ruuvitags Hardware|What happens if the battery power goes too low or battery fails otherwise|eg. battery explosions|
 
-## Functional tests
-### Raspberry pi 3
+### Functional tests
+#### Raspberry pi 3
 | Target | Description | Additional information |
 | -------- | -------- |-------- |
 |Raspberrys Hardware|Benchmarking with phaser games||
 |Raspberrys Software|Testing software performance with games|Performance must be over 25fps|
 |Raspberrys Software|Testing software compatibility with different raspberry pi operating systems||
 
-### RuuviTag
+#### RuuviTag
+| Target | Description | Additional information |
+| -------- | -------- |-------- |
 |Ruuvitags Physical test|Drop-test||
 |Ruuvitags Physical test|Testing water resistance||
\ No newline at end of file