DERIVING TEST CASES

Presenter Name | Company Name

A test case, in software engineering, is a set of conditions or variables under which a tester will determine whether an application, software system or one of its features is working as it was originally established for it to do.

To prove that the system or changes being implemented is ready for day to day business use without any error or adverse impact on the functionality.

 Identify the

use-case scenarios

For

each scenario, identify one or more test cases.

For

each test case, identify the conditions that will cause it to execute.

Complete

the test case by adding data values.

 Identify the different possible use case scenarios that are relevant to the software context. There can be multiple flows for covering the same scenarios. All the different used cases need to be covered by the test cases.

 The use cases developed for implementation are not 100 percent exhaustive and are written at a level of detail that may be insufficient for testing. The test team's review process should create new discoveries and additional scenarios that may result from executing the use case. Some of these may not even have been considered in the design and may thus require design modifications.

From the previously identified scenarios i.e used cases,we have to identify one or more test cases.

The test cases may not neccesarily be in the exact sync with the use case.

Here come the RESPONSIBILITY of QA team to create test cases accordingly.

For example:-

Retailer Application:
Scenario :- Making a Sale Object Involved:- cash sales, credit sales
Test case to check for the Inventory update. Test Case to validate Customer information. Test Case to Update Credit Standing of a customer.

Test Conditions are simply anything that you can think of to test, they are typically a one or two line description of the test you want to run.

While identifying the test conditions we want to identify as many conditions as we can.

Test conditions also known as VALIDATION.

Validations check the consitencies of the use case.

For eg. - Placing a purchase order

Data sent from the client side should be reflected on the distributor application.

Distributor table should get populated with the same data.

Validation

A test case cannot run without test data.

Consistency of test data plays a major role.

There should be a demarcation between manual test data and automated test data.

There should be a provision for mass data creation for rigorous testing to test the performance the system

The Status of the test case should not be considered blindly to determine the Success % of the system

REASON :

The failure of the test case may not necessarily be because of

the bug in the testing system.

It may be because of the inconsistent data.