Datadriven test is used to test the multinumbers of data in a data-table using this we can easy to replace the paramerers in the same time from deferent locations.

e.g: using .xsl sheets.

Ans. Re-execution of our test with different input values is called Re-testing. In validate our Project calculations test engineer follows retesting manner through automation tool.Re-teting is also called DataDriven Test.There are 4 types of datadriven tests.

1) Dynamic Input submissiion ( key driven test) : Sometines a test engineer conducts retesting with different input values to validate the calculation through dynamic submission.For this input submission test engineer use this function in TSL scriipt-- create_input_dialog ( label );

2) Data Driven Files Through FLAT FILES ( .txt .doc) : Sometimes testengineer conducts re-testing depends on flat file contents. He collect these files from Old Version databases or from customer side.

3)Data Driven Tests From FRONTEND GREAVES : Some times a test engineer create automation scripts depends on frontend objects values such as (a) list (b) menu (c) table (d) data window (5) ocx etc.

4)Data Driven Tests From EXCEL SHEET : sometimes a testengineer follows this type of data driven test to execute their script for multiple inputs. These multiple inputs consists in excel sheet columns. We have to collect this testdata from backend tables .

2) Data Driven Files Through FLAT FILES ( .txt .doc) : Sometimes testengineer conducts re-testing depends on flat file contents. He collect these files from Old Version databases or from customer side.

Can you elaborate more on this above type of testing. I might be doing that very soon!! How does it work?

Thanks

A P

Once the Test Script is created we want to check how behaves on multiple set of data So we can introduce DDT or parameter test.its involved in three steps

1 open and close data table

2 Data reterived from the Db

3 Change the static value.

Data Driven Testing: Testing in which the action of a test case is parameterized by externally defined data values maintained as a file or spreadsheet. This is a common technique in used in automated testing.

Sunil Kumar Nanda

New Delhi

Once u have successfully debugged and run your tests u may want to see how the same test performs with multiple tests of data which is nothing but datadriven testing.To do this you convert your test to datatdriven test and create a corresponding data table with the sets of data you want to test.

Converting your test to a data-driven test involves the following steps:

Adding statements to your script that open and close the data table.

Adding statements and functions to your test so that it will read from the data

table and run in a loop while it applies each set of data.

Replacing fixed values in recorded statements and checkpoint statements with

parameters known as parameterizing the test.

You can convert your test to a data-driven test using the DataDriver Wizard or

you can modify your script manually.

Data Driven Testing is our simple BLACK BOX FUNCTIONAL testing to validate the functional requirement.

nothing more or less than above defination. it is not paramaterization.

-- When we test our application we may want to check how it performs the
same operations with multiple sets of data.

For Example:-

Suppose we want to check how our application responds to multiple sets of data
we should record multiple separate tests each with it s own set of data. We
should create a data driven test with a loop that runs multiple times (how much
we should specify).

In fact we can say that testing the functionality with more test-cases
becomes laborious and time consuming as functionality grows. For multiple sets
of data or Test-cases. We can execute the test once in which we can figure out
for which data it has failed and which data the test has passed. The features is
available in the Winrunner with Data Driven Test where the data can be taken
from excel sheet or notepad.

For non-data-driven tests the testing process is performed in these steps:

Step1--- Creating a Test

Step2--- Converting to a data driven test and Preparing a data table

Step3-- Running the Test

Step4-- Analyzing Test Results

The procedure for converting a test to a data-driven test is composed of the
following main steps:

1)Replacing fixed value in checkpoints statements and in recorded statement
and in recorded statements with parameters and creating a data table containing
values for the parameters this is known as parameterising the test.

2)Adding statements and functions to our test so that it will read from data
table and run in loop while it reads each iteration of data.

3)Adding statement to our script that open and close the data table.

4)Assigning a variable name to the data table.