Skip to main content

Difference between Use Case and Test Case in Table




                  Use Case
                       Test Case
1
Use Case is prepared by business analyst.
Test case is prepared by test engineer and in small companies sometimes it is prepared by quality analyst too.
2
Based on test cases use cases cannot be prepared means it is not derived from test cases.
Based on use cases test cases can be prepared means it is derived from use cases.
3
Use case describes step by step instructions means how to use functionality.
Test case verifies the functionality means it is as per the instructions mentioned in use case or not.
4
Use case cannot be executed means it is only designed.
We design the test cases and later execute them.
5
It is derived from the BRS (Business requirement specification.)
It is derived from the use case.
6
It is a pictorial representation of client requirements or you can say customer requirements.
It is not represented diagrammatically it is only documented in excel sheet and in big companies it is also documented in some test case management tools.
7
It is a document which always describes the flow of events of an application.
It is a document which always contains an action, event and an expected result of particular feature of an application.
8
Use Cases can be written by BA (business analyst.) on the basis of client requirements or customer requirements.
Test cases are written by test engineer or quality analyst on the basis of use case document.
9
It always tells us about the story of how people interact with a software system to achieve a goal.
It verifies the goal to see it is as per the instructions of use case or not.
Labels:

Comments

Post a Comment

Popular posts from this blog

Difference Between Verification And Validation With Example?

Verification and Validation example is also given just below to this table.                Verification               Validation 1. Verification is a static practice of verifying documents, design, code and program. 1. Validation is a dynamic mechanism of validating and testing the actual product. 2. It does not involve executing the code. 2. It always involves executing the code. 3. It is human based checking of documents and files. 3. It is computer based execution of program. 4.  Verification uses methods like inspections, reviews, walkthroughs, and Desk-checking etc. 4.  Validation uses methods like black box (functional)  testing, gray box testing, and white box (structural) testing etc. 5.  Verification  is to check whether the softwar...
66 comments
Read more

Endurance Testing with Example, Meaning and Definition

Endurance Testing is a type of Performance Testing which is usually used to determine how much a system can sustain the continuous expected load. During the period of Endurance Testing memory utilization is always monitored to detect any potential leaks. In short we can say that judging/studying the memory leak of a server under the period of stability is known as Endurance Testing . Due to its judgment and study on memory leak that is the reason why Endurance Testing is also known by the name Soak Testing . As you know in Endurance Testing memory utilization is monitored so it very important for us to know about memory leak means what it is all about. When memory allocated to objects are not being freed by the system/application than definitely the memory leak occurs. Endurance Testing Example – Real Time Below is given the real time example of Endurance Testing and hope after seen these real time example your knowledge on Endurance Testing should definitely b...
Post a Comment
Read more

Regression Testing with Example and Strategies

Regression Testing is done to ensure that fixed bug does not affect the remaining functionality of the modules and also the functionality of the same module. In short you can say regression testing  is always done to verify that modified code does not break the existing functionality of the application and works within the requirements of the system. Regression Testing Example  For Example there are three Modules in the Project named Admin Module, Personal Information, and Employment Module and suppose bug occurs in the Admin Module like on Admin Module existing User is not able to login with valid login credentials so this is the bug.  Now Testing team sends the above - mentioned Bug to the Development team to fix it and when development team fixes the Bug and hand over to Testing team than testing team checks that fixed bug does not affect the remaining functionality of the other modules (Admin, PI, Employment) and also the functionality of ...
31 comments
Read more