What is the difference between use case and test case? give
example.
Answer Posted / krish
Test Case:
A test case is a set of conditions or variables under which
a tester will determine whether an application or software
system is working correctly or not.
Use Case:
A use case is a technique for capturing functional
requirements of systems and systems-of-system. Each use
case provides one or more scenerios that convey how the
system should interact with the users called actors to
achieve a specific business goal or function.
| Is This Answer Correct ? | 6 Yes | 0 No |
Post New Answer View All Answers
What is bottom-up approach?
Tell some examples of bug severity and bug priority?
What is a code walk through?
hi, I m looking for a career in manual web testing. so PLZ anybody who have the practical knowledge of dis field help me. GIVE ME UR MAIL ID so that i can ask regarding some doubts. my MAIL ID is ankurtester819@gmail.com
what are all the things we will include in " what to be tested and what not to be tested" in Test Plan
Explain compatibility testing with an example.
Pls u can u r mail id to my personal mail id also if they dont want to give u r mail id n comman place
Which of these techniques is not useful for partition testing at the class level Option 1 attribute-based partitioning Option 2 category-based partitioning Option 3 equivalence class partitioning Option 4 state-based partitioning
what is data guidelines
3. In a system designed to work out the tax to be paid: An employee has £4000 of salary tax free. The next £1500 is taxed at 10%. The next £28000 after that is taxed at 22%. Any further amount is taxed at 40%. To the nearest whole pound, which of these groups of numbers fall into three DIFFERENT equivalence classes?
How do you determine user soad for a perf test of a Web application?
how to connect oracle with test director? in testdirector we will be getting only reports? pls answer Thanks in Advance
how will you test transfer funds module...explain in detail
Should testing be done only after the build and execution phases are complete?
When to stop testing? (Or) how do you decide when you have tested enough?