Quality of Test Cases is directly proportional to Use Cases : Why to Review Use Case thoroughly
From the Blog for Project Management Practices by Pravin Blog
by Pravin Kumar Shrivastava
Quality of Test Cases is directly proportional to Use Cases : Why to Review Use Case thoroughly
As a principle, every QA Engineer follows the use cases to design Test Cases irrespective of methodology they adopt.
Completeness and coverage within Test Cases fully depends on how the Use Cases are written and organized.
It always recommended having a QA review of Use Cases before releasing and freezing it for next usage, i.e. development or writing test cases. The focus should be bring sufficient business cases and identify gaps as early as possible to help teams in avoiding defects.
A lot written on use cases and what it should contain, primarily, it should have:
- All business and attributes clearly defined
- Clearly identified entities involved
- Alternate cases clearly defined with complete cycle
- Business analysts tend to link the Use Cases to avoid redundancy; it should not be done at the cost of clarity.
Once QA does a comprehensive review of use case, it certainly got value added and qualifies for writing test cases. A nicely written use case always makes job easy for QA Engineers and Developers.
More to cover about test cases in next blog.....
Posted on: November 17, 2017 11:14 PM |
Permalink
Comments (9)
Please login or join to subscribe to this item
QA with comprehensive review of use case will definitely make the project fruitful and more sustainable
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates
New Westminster, British Columbia, Canada
Sergio Luis Conte
Helping to create solutions for everyone| Worldwide based Organizations
Buenos Aires, Argentina
Use Cases must be part of a quality assurance process. The quality assurance checklist you can use is inside the IEEE standards. If you follow the checklist you will get well written Use Cases. Is not about the form, is about the content.
Yes, it is more about contents since Forms can be tailored based on organization specific guidelines. The content review is must to ensure the completeness or a case.
Stéphane Parent
Self Employed / Semi-retired| Leader Maker
Prince Edward Island, Canada
How have you integrated use cases in Scrum projects? Do you have them separate from the use stories or do you blend them?
Sergio Luis Conte
Helping to create solutions for everyone| Worldwide based Organizations
Buenos Aires, Argentina
I will answer you Stéphane but I am very interested on Pravin answer and other answers too. I have made two different experiences: 1-replacing user stories by use cases. I mean, we use uses cases instead of user stories. 2.using both where we use user stories to define requirements related to the product and use cases for all related to the system where system is not software system in this case.
Stéphane Parent
Self Employed / Semi-retired| Leader Maker
Prince Edward Island, Canada
Interesting, Sergio. Your answer makes sense: use either use case or user story but use one for each requirement.
Sergio Luis Conte
Helping to create solutions for everyone| Worldwide based Organizations
Buenos Aires, Argentina
It is what I have experienced after working with them. If you ask me, I prefer Use Cases but at the end I always push to use what best fit for the initiative.
Please Login/Register to leave a comment.
|
"Maybe this world is another planet's hell."
- Aldous Huxley
|
