|
|
| sivapgr@gmail.com 2008-02-03, 5:40 am |
| How do i find the test cases covered all the requirements ?
| |
| H. S. Lahman 2008-02-03, 8:11 pm |
| Responding to Sivapgr...
> How do i find the test cases covered all the requirements ?
Do you mean:
How do I determine if the test cases in my test suite cover all the
requirements?
OR
How do I design a test suite whose test cases cover all the requirements?
--
There is nothing wrong with me that could
not be cured by a capful of Drano.
H. S. Lahman
hsl@pathfindermda.com
Pathfinder Solutions
http://www.pathfindermda.com
blog: http://pathfinderpeople.blogs.com/hslahman
"Model-Based Translation: The Next Step in Agile Development". Email
info@pathfindermda.com for your copy.
Pathfinder is hiring:
http://www.pathfindermda.com/about_us/careers_pos3.php.
(888)OOA-PATH
| |
| Ernie Englehart 2008-02-03, 8:11 pm |
|
<sivapgr@gmail.com> wrote in message =
news:87cc44a1-6866-44b2-9f87-ce5a181ac9f7@j20g2000hsi.googlegroups.com...=
> How do i find the test cases covered all the requirements ?
A traceability matrix. Makes sure that you have at least one test case =
for every requirement. This assumes that your requirements document is =
organized in some formal way and the requirements are numbered or =
tagged. In lieu of this, manual review of the test cases with the =
project team.
| |
| Michael Bolton 2008-02-04, 5:48 am |
| > How do i find the test cases covered all the requirements ?
You'd have to have all the requirements first. They /will not/ all be
written down.
I think you might better ask "how do I find the test cases covered all
the requirements /that matter/?" Start by telling us what you /
could/ do, and you'll get better answers here.
---Michael B.
| |
| Shrinik 2008-02-04, 5:48 am |
| >>>How do i find the test cases covered all the requirements ?
You can not. Better question would be "Can I by any means make sure
that test cases I have, covered all the requirement?" - the answer to
this also would be "you can not"
Test cases and requirements are two strange entities in our software
testing world. One important characterstic of these two is - they can
not be counted (conversly if you are counting them they not the
original things in their entiriety). Requirements and test cases are
mere ideas and counting ideas is a really bad idea.
To answer your question - first of all you can not have all
requirements captured, even if you claim that you have done that ...
you can not make sure that your test cases cover /all/ requirements.
Even simplest statement (requirement )like "Mary had a little lamb"
can have many many interpretations.
Shrini
| |
| Vladimir Trushkin 2008-02-08, 8:25 am |
| On Feb 4, 11:25=A0am, Shrinik <Shri...@gmail.com> wrote:
>
> You can not. Better question would =A0be "Can I by any means make sure
> that test cases I have, covered all the requirement?" - the answer to
> this also would be "you can not"
>
> Test cases and requirements are two strange entities in our software
> testing world. One important characterstic of these two is - they can
> not be counted (conversly if you are counting them they not the
> original things in their entiriety). Requirements and test cases are
> mere ideas and counting ideas is a really bad idea.
>
> To answer your question - first of all you can not have all
> requirements captured, even if you claim that you have done that ...
> you can not make sure that your test cases cover /all/ requirements.
> Even simplest statement (requirement )like "Mary had a little lamb"
> can have many many interpretations.
>
I agree with you that hoping that all requirements will be captured at
required level of details is rather a wishful thinking. Yet, from
another perspective, the intention to capture all requirements is
positive. It helps looking for way of how to accomplish this
challenging task. I see it as a goal and the motivation to improve
skills at requirement engineering. I saw many examples when the notion
that all requirements cannot be captured was used for the excuse for
not doing the best at requirement gathering. Same as the commonly
known statement that "all defects cannot be found" is used as an
excuse for not trying to find defects.
I would recommend an author of this thread to go for unique
requirement and test case IDs and traceability matrix that will map
one to another by means of those IDs.
----
Best Wishes,
Vladimir
|
|
|
|