Skip to main content

Use Cases and Test Cases

 

What is a Use Case

In Software Development Environment Use Case is identified as the list of actions or steps typically defining the interactions between actors and the system in order to perform a feature of the software. The actor can be a human or an external system. 


What is a Test Case

A Test Case is a document which consists of a set of conditions or actions which needs to perform on the software in order to verify expected functionality of the feature.

When comparing these two terms we can see a few clear differences between these two as below

Use Case

 

Test Case

Components - Use Case name,

Actors, Pre Conditions, Assumptions, Post Conditions, Business Rules, Normal Process flow, Alternative process flow

Components - Test Case ID, Test Case Title, Pre-Conditions, Test Case Description, Expected Results, Actual Results, Priority, Complexity, Bug ID

Describes the overview of the software functions to reach the final feature

Demonstrates the test progress and the step by step interaction between the software and the user

Includes different paths to complete a certain function or a feature

Always tests one case at a time. And shows the clear result after the testing process to make decisions

This can combine different case or one case at a time

As it tests one case at a time, there is no chance to combine the results

The root of the use case is the requirement of the business

The root of the test case if the framework of the use case

Creates to understand the whole feature clearly, so the execution is not possible

Creates the results by testing each function inside the main function as well as the main feature.


Comments

Post a Comment

Popular posts from this blog

Defect Management Process

Importance of the defect management process in software development teams Provide developers and other parties with feedback about the problem to enable identification, isolation and correction as necessary; Provide test leaders means of tracking the quality of the system under test and the progress of the testing; Provide ideas for test process improvement Fields in a bug report Bug ID: A bug number or an identification number makes bug reporting and referring to a bug much easier Bug Title: A bug title is read more often than any other part of the bug report. It should say all about what comes in the bug. Also, the bug title should be suggestive enough that the reader can understand it. Priority: Based on the severity of the bug, a priority can be set for it. A bug can be a Blocker, Critical, Major, Minor, Trivial, or a suggestion. A bug priority from P1 to P5 can be given so that the important ones are viewed first. Platform/ Environment: The OS and browser configuration is nece...
Post a Comment
Read more

Stakeholders of SDLC

  The different stake holders involved in different phases of SDLC: Clients/Customers Business Analysts Architects Project Managers Developers Testers Customer Support Officers   Role of Business Analyst in different phase of SDLC Requirements Analysis and Planning: Makes appointments with the clients and start interviewing about the requirements of the project which is called Requirement Gathering or Requirement Elicitation. Interviewed information is documented using documented prepare Use Cases, Use case Diagrams, Activity Diagrams, Data Flow Diagram Designing Review the solution documents and wok closely with designer and architects to ensure requirements are clear Manage the changes to requirements both from the business and from the designer’s point of view through the change control process. Developing Conductus frequent meetings with development team in case of clarifications to e=make sure the project is in the right track. Testing Makes an appointment with clien...
Post a Comment
Read more

End to End Test vs Component Test

E2E Test E2E - End to End Tests help verify high value paths in an application. In other words, they help verify user stories as they often represent in the application. The main purpose of E2E testing is to test from the end user’s experience by simulating the real user scenario and validating the system under test. Basically these tests check the complete end-to-end process flow - The one happy scenario   Below are the E2E test cases we can write for the Graph feature Scenario 1 : User can add a Graph Scenario 2 : User can rename the Graph Scenario 3: User can add data to the Graph Scenario 4: User can remove the data from the Graph Scenario 5: User can manage the time zone Scenario 6: User can delete the Graph As an example, let’s say we need to write E2E test for Rename Graph scenario. Below is the flow we should cover. Log in as an Admin → Navigate to the Data Studio → Click on a Dashboard → Click on the graph ellipsis menu → Click on “Rename Graph” → Ent...
Post a Comment
Read more