You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a Systems Engineer it is mandatory to have an overview of the whole system. For this architectural models are needed. If we want to start testing or continue testing the system it would be useful to have an overview of the whole testing process.
This includes not only how to start / execute / grade the tests but also an overview of the different test scenarios. If the car is changed to for example make perfect emergency brakes, we need to know if a test exists for this scenario and how to run it. Therefore we need a readme and documentation for the testing system.
It would be useful to insert the gained information in this document: architecture.md
Definition of Done
It is checked if a documentation is already existing
Obtain an overview if there exists specific test scenarios for edge cases (emergency breaking, bicycles, ...)
If not, check if it even possible to make specific tests for these scenarios
Detailed Description
As a Systems Engineer it is mandatory to have an overview of the whole system. For this architectural models are needed. If we want to start testing or continue testing the system it would be useful to have an overview of the whole testing process.
This includes not only how to start / execute / grade the tests but also an overview of the different test scenarios. If the car is changed to for example make perfect emergency brakes, we need to know if a test exists for this scenario and how to run it. Therefore we need a readme and documentation for the testing system.
It would be useful to insert the gained information in this document: architecture.md
Definition of Done
Effort Estimate
4 h
Testability
No response
Dependencies
#360
The text was updated successfully, but these errors were encountered: