It is important to documented the test made on the software, to show that each functionality works as expected. This is done by used for test cases. A test case defines how the functionally should be tested and what the requirements are for it to pass the tests. It is important to documented the result of each test. Test cases are normally made in a table format, a example is provide below:
Case ID
Objective
Prerequisite
Steps
Expected behavior
Actual behavior
Status
TC_01
Forward movement
Correct version of code flash on MCU
Turn on the forklift
The forklift moves in forward direction
The forklift did not move
Failed
TC_02
Detected obstacle
Correct version of code flash on MCU
1. Turn on the forklift. 2. Place a obstacle in its path
The forklifts stops and wait for obstacle to be moved, then resume normal movement
The forklift detected the obstacle and waited until it was moved then resumed normal movement
Pass
The test cases will be include in the report, so it is a good idea to make them in LaTeX using a modular table.
If any support is required for any of the above, then contact @N0hen.
Estimated time: 4h
Task goals
Create test cases for stage 1
Prepare the table for stage 2 & 3 (but don't write them)
Description
It is important to documented the test made on the software, to show that each functionality works as expected. This is done by used for test cases. A test case defines how the functionally should be tested and what the requirements are for it to pass the tests. It is important to documented the result of each test. Test cases are normally made in a table format, a example is provide below:
The test cases will be include in the report, so it is a good idea to make them in LaTeX using a modular table.
If any support is required for any of the above, then contact @N0hen.
Estimated time: 4h
Task goals