Attifunel process req test description added#679
Conversation
|
The created documentation from the pull request is available at: docu-html |
| Note that requirement-based testing derivation is typically covered by other techniques | ||
| mentioned here, such as Boundary Values, Equivalence Classes, Fuzzy Testing, Interface | ||
| Testing and Fault Injection. |
There was a problem hiding this comment.
| Note that requirement-based testing derivation is typically covered by other techniques | |
| mentioned here, such as Boundary Values, Equivalence Classes, Fuzzy Testing, Interface | |
| Testing and Fault Injection. | |
| Note that requirement-based testing derivation is typically covered by other techniques | |
| and methods mentioned here, such as Boundary Values, Equivalence Classes, and Fuzzy Testing. |
Interface testing is verification method, but according to the iso not a derivation technique. Same holds true for Fault injection.
There was a problem hiding this comment.
Mhmhm... I have this opinion that ISO 26262 makes a bit of mixed bag there by mixing "derivation methods" and "techniques". I wanted to stay generic speaking of "techniques" without derivation, but maybe this causes confusion?
There was a problem hiding this comment.
My point of concern is where it says typically covered by do you mean it gets extended by or enhanced by? With the current wording it sounds much more like being included in the other techniques.
There was a problem hiding this comment.
Changed to "Note that requirement-based dervied test case may also cover other techniques". Agree?
| be also considered: i.e. testing what happens when input x = C (if not already specified | ||
| in other requirements). | ||
|
|
||
| Note that requirement-based derived test case may also cover other techniques and derivation methods |
There was a problem hiding this comment.
Thats not an "may"! It depends on the ASIL Level according to the ISO Norm. For ASIL B the "Generation and analysis of equivalence classes" and "Analysis of boundary values" are highly recommended (what means mandatory). Fault injection is for ASIL C.
Added requirement method with description