What is the difference between Use Case, Test Scenario and Test Case?

 Use case, test case, and test scenario are all related to software testing.

  • Use case is a document that describes how a user interacts with a system to achieve a specific goal.
  • Test case is a set of inputs, execution conditions, and expected results developed for a particular objective.
  • Test scenario is a series of actions that are associated together. It represents a thread of operations.
  • Test Cases are derived from test Scenarios which are derived from Use case.

What is a Use Case?

A Use Case is used to define the system that how to use the system for performing a specific task. A use case is not a part of execution it is only a diagrammatic presentation of a document that specifies how to perform a certain task.

  • The actor simulates the end-user interaction, and it can be portrayed by human or external software.
  • Use cases are also visualized with an overview diagram.
  • The diagram should contain all components that are involved when interacting with the system.
  • Among the components, there are different actors, a list of actions, relationships between them, and so on.

What is a Test Case?

A Test Case is defined as a group of test inputs, execution conditions, and expected results that further lead to developing a particular test objective.  If we talk about test cases it is used to validate the software which is developed by testers for validating whether the software is in working as per requirement or not. 

  • Test cases cover fields like test descriptions, test steps, anticipated results, etc.
  • These are useful in providing good testing coverage.
  • Test case documentation helps to keep the team on track with upcoming tasks.
  • These can be reused for future use.
  • Example of Test Cases

  • Test cases for the Test Scenario: “Check the Login Functionality” would be

    1. Check system behavior when valid email id and password is entered.
    2. Check system behavior when invalid email id and valid password is entered.
    3. Check system behavior when valid email id and invalid password is entered.
    4. Check system behavior when invalid email id and invalid password is entered.
    5. Check system behavior when email id and password are left blank and Sign in entered.
    6. Check Forgot your password is working as expected
    7. Check system behavior when valid/invalid phone number and password is entered.
    8. Check system behavior when “Keep me signed” is checked.
A Test Scenario is defined as any functionality that can be tested. It is a collective set of test cases which helps the testing team to determine the positive and negative characteristics of the project.

Test Scenario gives a high-level idea of what we need to test.


Example of Test Scenario

For an eCommerce Application, a few test scenarios would be

Test Scenario 1: Check the Search Functionality

Test Scenario 2: Check the Payments Functionality

Test Scenario 3: Check the Login Functionality






Comments

Post a Comment

Popular posts from this blog

What are the different types of Non-Functional Tests

Image
Non Functional Testing Non-Functional Testing  is defined as a type of Software testing to check non-functional aspects (performance, usability, reliability, etc) of a software application. Following are the most common  Types of Non Functional  Testing: Performance Testing Load Testing Failover Testing Compatibility Testing Usability Testing Stress Testing Maintainability Testing Scalability Testing Volume Testing Security Testing Disaster Recovery Testing Compliance Testing Portability Testing Efficiency Testing Reliability Testing Baseline Testing Endurance Testing Documentation Testing Recovery Testing Internationalization Testing Localization Testing 1) Security: The parameter defines how a system is safeguarded against deliberate and sudden attacks from internal and external sources. This is tested via Security Testing. 2) Reliability: The extent to which any software system continuously performs the specified functions without failure. This is tested by R...
Read more

What are the benefits of using Scrum?

  Scrum in Agile  is a process that allows software development teams to focus on delivering business values in shortest time by rapidly and repeatedly inspecting actual working software. It focuses on accountability, teamwork and iterative progress towards well-defined goals. Scrum Framework usually deals with fact that requirements are likely to change or mostly not known at the beginning of project. Scrum Scrum is one of the implementations of agile methodology. In which incremental builds are delivered to the customer in every two to three weeks’ time. Scrum is ideally used in the project where the requirement is rapidly changing. Scrum teams are self-organizing, cross-functional team. The biggest advantage of Scrum is its flexibility as it quickly reacts to changes. In Scrum, collaboration is achieved in daily stand-up meetings with a fixed role assigned to scrum master, product owner, and team members. Not too many changes needed while implementing scrum proces...
Read more