Timeline for Unit Testing against Detailed Design, How to perform requirements based tests ISO 29119? Traceability to Unit Requirements?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 17, 2020 at 9:24 | history | edited | Ewan | CC BY-SA 4.0 | deleted 8 characters in body |
| Jan 17, 2020 at 7:38 | comment | added | SoftwareTester | In automotive software, SW components are the lowest level software elements and specified in detailed design. We used to write blackbox software component requirements in these documents and trace the unit tests. Now, the requirements are moved up the V-Model and they plan to mark all tests as SW qualification test. and tests validating interfaces of a single SW component as integration tests and then they want developers to test how the component is implemented and mark them as unit tests. repeating 3 times with different mindsets. How can processes specify something like this? | |
| Jan 16, 2020 at 13:00 | comment | added | Thomas Owens♦ | Otherwise why are you testing unrequired behaviour! When you're in more critical systems (I saw this in aerospace, I wouldn't be surprised if it's also in automotive systems), the more fundamental question is why you have unrequired behavior implemented. The only place I've seen it is in reuse of a system, but in that case, there's traceability between the reuse of the component in different systems and traceability to the design and requirements in one of those reuse instances. | |
| Jan 16, 2020 at 10:59 | history | answered | Ewan | CC BY-SA 4.0 |