Use case vs Test Case

-
Difference between Use Case and Test Case



So what is a Use case and a Test Case. These terms frequently used in the software testing field, which are also closely related. A use case is used to specify how to use the system designed for performing a specific task. As against, a test case is a group of test inputs, execution conditions, and expected results developed for a particular test objective.

Furthermore, the use case does not run or execute as it is a textual or diagrammatic presentation of a document which specifies how to accomplish a certain task. Whereas, test cases are prepared by the software testers to validate the software and check whether it is working as per requirements or not.

What is a Use Case?
A use case is a description of how a person who actually uses that process or system will accomplish a goal.  It outlines, from a user’s point of view, a system’s behaviour as it responds to a request. Each use case is represented as a sequence of simple steps, beginning with a user's goal and ending when that goal is fulfilled.

What is a Test Case?
The test case is a set of inputs and expected output which is used for analysing the program behaviour. Use case description is fed as the input to the test case worksheet. A Test Case contains test steps, test data, precondition, postcondition developed for specific test scenario to verify any requirement.






    

Comments

Post a Comment

Popular posts from this blog

Explicit Wait, Implicit Wait, Fluent Wait in Selenium using C#

-
What are Wait commands? Waits are the command in Selenium which is very useful for the execution of the automated test scripts. During execution of automated test script, there might be some situation where issues may occur due to variations in time lag for loading web elements. In these situation Wait commands helps in troubleshooting these issues. Wait commands helps in directing a test script to pause for a certain time before throwing exception. Types of  Wait Commands Selenium WebDriver provides three types of wait commands to implement in tests. 1. Implicit Wait 2. Explicit Wait 3. Fluent Wait Implicit Wait Implicit wait directs the Selenium WebDriver to wait for a certain measure of time before throwing an exception. Once this time is set, WebDriver will wait for the webelement before throwing exception. So by implicitly wait, the WebDriver will wait for certain duration to find any webelement. This can helpful when certain elements on the webpage are not available immediately a
Read more

Assertion

-
PURPOSE OF ASSERT IN A TEST AUTOMATION SUITE  Assert plays vital role in automation testing. Without assertion we cannot provide the status of the test cases passed, failed etc. Assertion is used to validate the status of a test case. Let's take an example of a login page where a user logged in through valid username , valid password and clicking the login button. With valid credential it should login to the home page successfully. Now that a user has been logged in successfully there should be some sort of commands which helps to validate the user has successfully logged in. Hence assertion comes into picture, where we can use assertion command to validate whether the user has been successfully logged in by comparing any text in the homepage with the text provided in the command. eg. Assert.assertEquals(expected, actual) Here if the actual and expected matches , then the test case will be marked as a passed.
Read more

CI/CD Pipelines & DevOps

-
Image
CI/CD Pipelines & DevOps A CI/CD Pipeline implementation, or Continuous Integration/Continuous Deployment, is the backbone of the modern DevOps environment. It bridges the gap between development and operations teams by automating the building, testing, and deployment of applications. CI/CD is o ne of the best practices for DevOps teams to implement . It is also an  agile methodology  best practice, as it enables software development teams to focus on meeting business requirements, code quality, and security because deployment steps are automated. Before moving onto the CI/CD pipeline, let's start by understanding DevOps. DevOps is a software development approach which involves continuous development, continuous testing, continuous integration, continuous deployment, and continuous monitoring of the software throughout its development lifecycle. Let us now look at the DevOps lifecycle and explore how it is related to the software development stages.
Read more