Skip to main content

Use Case Testing

Use Case Testing is the type of Black Box Testing in which Testers can understand the Test Scenario and check the all Business Transaction (Test Cases) step by step from start to finish.  This is Functional Testing type. In Use Case Testing there is an actor who perform all the Test Cases over the system so Use Cases testing is the interaction between the actor and the system.

Actor perform the Test cases to achieve the particular specified task. actors stand for users who perform interaction with the system.

Use Case Testing is the sequence of steps. These steps describe the interaction between the users and the system. Use Case are defined in terms of the actor not system. Use case describe what the user see and what the user does not what the system takes in input and what system provide output. Use Case Testing took the language not the technical terms.



Comments

Popular posts from this blog

What is API?

In general way, API (Application Programming Interface) is the intermediate software which is useful for two applications to communicate. API is the tool which is used for interaction of two applications. If developer developing any software which have multiple blocks (Modules) than developer use APIs to put them together.

Smoke Testing

In Smoke Testing, Testing team check the key feature or key bugs of the software. Smoke testing ensure that critical functionality of the software is working fine.If key features are not working then it is no needed to test the overall functionality because it is just waste of time. In Smoke Testing, test team check the basic feature of the software and if basic feature is not working it means software is broken very badly and further testing is unnecessary. If Smoke Testing failed then it is declared that build is unstable and revert back to developer team until smoke test is pass.

Difference between Error, Bug, Defect and Failure

Error: Any mistake in the coding called error. The mistake may be Syntax error, Logical errors or other GUI errors lead errors in any software. These are from developer side. Defect: The error which made by developer and during testing, Tester is able to find that errors,  means if actual result deviated from expected result then that error called defects. This is caught by testers. Bug: The defect which is developed by tester team, if expected by the developer team then that defect called an bug. Failure: If the Software does not meet the client requirement then this is called failure of the software.