-
Notifications
You must be signed in to change notification settings - Fork 23
Attifunel process req test description added #679
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from 4 commits
fb3d3ba
9bb64b2
0eeb805
859aef8
dc7dca5
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -172,10 +172,31 @@ Derivation Techniques | |||||||||||
|
|
||||||||||||
| Following derivation techniques are explained | ||||||||||||
|
|
||||||||||||
| * :ref:`Requirements analysis <ver_req_anal>` | ||||||||||||
| * :ref:`Boundary Values <ver_boundary>` | ||||||||||||
| * :ref:`Equivalence Classes <ver_equivalence>` | ||||||||||||
| * :ref:`Fuzzy Testing <ver_fuzzy>` | ||||||||||||
|
|
||||||||||||
| .. _ver_req_anal: | ||||||||||||
|
|
||||||||||||
| Requirements analysis | ||||||||||||
| """"""""""""""""""""" | ||||||||||||
|
|
||||||||||||
| Requirements analysis is a testing technique where tests are designed based on the | ||||||||||||
| requirements assigned to the software element under test (component, module, unit etc.). | ||||||||||||
| If available, the verification method defined for each requirement should be used as | ||||||||||||
| the basis of the test cases design. | ||||||||||||
|
|
||||||||||||
| Requirements should always be tested against their "nominal" behaviour: i.e. "if input | ||||||||||||
| x = A, the output y of SW component X shall be equal to b". This leads to a test case | ||||||||||||
| injection value x = A and verifying that output y = B. "Negative" testing technique should | ||||||||||||
| be also considered: i.e. testing what happens when input x = B (if not already specified | ||||||||||||
| in other requirements). | ||||||||||||
|
attifunel marked this conversation as resolved.
Outdated
|
||||||||||||
|
|
||||||||||||
| 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. | ||||||||||||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Interface testing is verification method, but according to the iso not a derivation technique. Same holds true for Fault injection.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 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?
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. My point of concern is where it says
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Changed to "Note that requirement-based dervied test case may also cover other techniques". Agree? |
||||||||||||
|
|
||||||||||||
| .. _ver_boundary: | ||||||||||||
|
|
||||||||||||
| Boundary Values | ||||||||||||
|
|
||||||||||||
Uh oh!
There was an error while loading. Please reload this page.