Deliverable 4.0
In this final part of the project, you need to test the implementation provided by your partner team to make sure that it works in the scenarios described in the requirements document (SRS). You may also test other scenarios, as long as they can be reasonably inferred from other requirements you had prepared.
You do not have to prepare a formal document this time (though there are of course IEEE templates for that), a simple structured Markdown file will do.
There are some frameworks for integration testing, but their use is more varied, and generally a lot of projects have their own peculiar way of running integration tests. For the sake of not spending too much time on this phase, you do not need to make your tests automatic: it is enough if you check all scenarios manually. That said, if you feel comfortable enough will shell scripts, you may still find them useful.
You should add your testing report to the root directory of the same repository
as your SRS and SDS, with name testing_report.md
.
The general structure of your "testing report" Markdown file should be as follows:
# Test Summary Report
## Introduction
The overall verdict in brief.
## Scenarios tested
### Scenario 1 (PASSED/FAILED)
Short description of the expected behavior.
Result:
> Pass/Fail. (If fail, how the actual behavior is different from expected)
### Scenario 2 (PASSED/FAILED)
...
## Other concerns and comments
(If you wish to add anything)