Feedback: 2.1.2 Tests Types

[x] Unit Tests: "Test the separate pluggings, or independent software areas." What is a software area?
[x] Unit Tests: "100% code coverage is not practical, and also not necessary." Keep in mind that a lot of code is generated (by EMF), which does not need to be tested (unless modified). Also, what good does it do if we have 100% coverage, while we use Papyrus, which might have much less?
[x] Integration Tests: "The total coverage of the tested is greater than 80% of all modules" What is a module? How do you measure coverage?
[x] "Validate non-functional requirements. During the System testing will be checked: the speed, the security, the reliability. . . etc." Don't enumerate the non-functional requirements, provide a reference on where they are documented, including quantitative criteria.
[x] Functional Tests: "validating that the user’s workflows are correctly created and to provide clear evidence that the platform performs as it should in every possible environment." Please provide a reference on where this is documented.
[x] "preloaded data which is available on github repository." Where? Please be specific.
[x] "97% pass rate of Test Scripts" For functional tests, this must be 100%.
[x] "Validate tool chain still works perfectly after corrective actions or new functionality has been applied." How can this be achieved?!?
[x] User Acceptance Tests: "Check that designed use cases had the correct results" Where are these documented?

openETCS / toolchain