Moving instruction before code in order for it to be more clear to th… (#85) (#86)

* Moving instruction before code in order for it to be more clear to the user that the test will fail

* cleanup

Co-authored-by: kevin-f-ortega <[email protected]>

Author: LeStarch

docs/system-testing.md

@@ -109,14 +109,13 @@ In `test_blinking()`, after turning blinking on, add the following the check tha
 Run `pytest` and make sure the new assertion passes.
 
 Now, add the similar assertion to verify the BlinkingState is set OFF after stopping blinking
+Run `pytest` again. **Notice that this new telemetry check should fail.**
 
 ```python
 # Assert that blink command sets blinking state off
 #TODO: use fprime_test_api.assert_telemetry to check that "LedBlinker.led.BlinkingState" is off
 ```
 
-Run `pytest` again. **Notice that this new telemetry check should fail.**
-
 Events in fprime are emitted immediately, but telemetry is only emitted periodically. In the LedBlinker deployment, telemetry channels are sent once per second.
 
 The `fprime_test_api.assert_telemetry` check will immediately search for a matching `LedBlinker.led.BlinkingState` telemetry value.