Before explaining Use case Testing lets first understand what is a Use Case?
1. A Use case is a description of a particular use of the system by the end user of the system.
2. Use cases are a sequence of steps that describe the interactions between the user and the software system.
3. Each use case describes the interactions the end user has with the software system in order to achieve a specific task.
What is Use case Testing?
Use case testing is a technique that helps us identify test cases that exercise the whole system on a transaction by transaction basis from start to finish.
Use cases are defined in terms of the end user and not the system, use case describe what the user does and what the user sees rather than what inputs the software system expects and what the system outputs.
Use cases use the business language rather than technical terms.
Each use case must specify any preconditions that need to be met for the use case to work. Use cases must also specify post conditions that are observable results and a description of the final state of the system after the use case has been executed successfully.
1. A Use case is a description of a particular use of the system by the end user of the system.
2. Use cases are a sequence of steps that describe the interactions between the user and the software system.
3. Each use case describes the interactions the end user has with the software system in order to achieve a specific task.
What is Use case Testing?
Use case testing is a technique that helps us identify test cases that exercise the whole system on a transaction by transaction basis from start to finish.
Use cases are defined in terms of the end user and not the system, use case describe what the user does and what the user sees rather than what inputs the software system expects and what the system outputs.
Use cases use the business language rather than technical terms.
Each use case must specify any preconditions that need to be met for the use case to work. Use cases must also specify post conditions that are observable results and a description of the final state of the system after the use case has been executed successfully.