Software Testing approach and strategy:

When the new project get assigned and you are the owner of the module, the approach first start with the understanding of the module and its functionality.

1. Getting the complete exposure of the functionality in the module
2. Setting up the environment and making sure that there is no change in the testing environment as far as the testing is going on.
3. Defining and seting up the processes like

a. the dependencies on other teams

b. the work flow

4. Reviewing of test cases and activities done by testing team every day
5. We also need to take the back up of our data for every days work.
6. During the testing phase we also have to make sure that we have the maximum coverage of feature.
7. If we are filing any adhoc bug we have to make sure that we have added its test case too.
8. Addition of test with every product fix or every new patch is must.

I hope you guys find this information helpful. Let me know, if any thing you would like to update if I am missing it.

Free Download QTP

Download QTP 9.0

How will you perform data driven testing inQTP

In automation, data driven testing is very inportant and if you are using QTP then you must be master of Keyword driven testing as well as data driven testing.

In QTP, data driven testing can be done by two ways
1. Using Global Sheet
2. Importing Excel Sheet in your script and fetching each row in a loop

The most professional and acceptable method is by importing excel sheet.

The following example uses the ImportSheet method to import the first sheet of the name.xls table to the name sheet in the test's run-time Data Table(I hope every body aware of run time data table)

DataTable.ImportSheet "C:\name.xls" ,1 ,"name"

To simply import excel sheet to run time data table then use.

Datatable.Import("c:\name.xls")

In order to fetch the current row you can make use of following method.

Datatable.GetCurrentRow

You can create one varible and store the value of current row and can use it, further in your script. This is more convienent in practice.

When will you use Keyword Driven Testing?

Recording Steps: When the application is new or major new functionality has been added to the module or when you have short span of time and the business requirement is not yet fulfilled and need to quickly create a test.

Keyword : It enables the user to create a test at business level rather than at object level. So we can modify the scripts easily as per the requirement and necessity.

Keyword Driven Testing

Generally people get confused with the Keyword driven testing and data driven testing.

Friends Keydriven testing is generally for QTP as we can develop script in QTP using keywords. Simply you can say it is technique which seaprates the programming work from the actual test steps. So we can develop the test using the already shared repositories and function libraries.

It divides test creation in two stages.

1. Preparing test automation infrastructure - It includes one ore more shared object repositories as well as function libraries
2. Creating test in Keyword view

Basic of QTP

QTP : Quick Test Professional

It is a Mercury Interactive Functional Testing Tool and uses VB scripting. QTP is based on two concept
1. Recording
2. Playback

It has three types of recording context/standard/normal recording, analog recording, low level recording. Novice user should know the process of testing in QTP

1. Application should be testable
2. Preparing a set of testing reseources(object respositories, function libraries)
3. Recording session
4. Enhancing your test
5. Debugging Test
6. Running Test
7. Analayzing Test Result
8. Reporting defects