Index:
1.Introducing QTP
Benefits of Automated Testing.
Testing Process
QuickTest Window
2. Recording Tests
Preparing to record a test.
Recording a Test
Analyzing the test tree
3. Running and Analyzing Tests
Running a Test
Analyzing Test results
4. Creating Checkpoints
Understanding Checkpoint types
Checking Objects
Checking pages
Checking Text
Checking Tables
Running and analyzing a test wiht checkpoints
5 . Parameterizing Tests
Defining a data table parameter
Adding parameter values to a data table
Modifying steps affected by parameterization
Running and Analyzing a parameterized test
6. Creating output values
Creating an output value
Running and analyzing a test with output values
7. Using Regular expressions
Regular expression syntax
Working with regular expressions
Running and analyzing a test with regular expressions
8. Dividing tests into multiple actions
Working with multiple actions
Creating new actions
Inserting existing actions
Parameterizing an action
Running and analyzing a multi-action Test
Wednesday, October 6, 2010
Saturday, February 20, 2010
Manual testing part-2 Testing life cycle
The testing life cycle looks like above image consist of the different stages
1. Analysing the requirement : Go through the requirement document and understand the requirement
The requirement document looks like below
The next activity will be preparing a test plan that is planning your testing activity ,the test plan document looks like below
Comming Soon......
Analyse the requirement document and prepare the test scenario's and test cases
Test Scenarios-Test scenario's are the possible ways the requirements will be used by the end users .
The test scenarios for the above requirement will be as follows
1.Test with UserName blank-Unsuccessful scenario for validation message
2.Test with Password blank-Unsuccessful scenario for validation message
3.Test with Invalid Username -Unsuccessful scenario for validation message
4.Test with Invalid Password-Unsuccessful scenario for validation message
5. Username with size greater than max size -Unsuccessful scenario for validation message
6.Username with size greater than min size -Unsuccessful scenario for validation message
7.Password with size greater than max size -Unsuccessful scenario for validation message
8.Password with size greater than min size -Unsuccessful scenario for validation message
9.Test scenario for 3 unsuccessful login locks user account -Unsuccessful scenario for validation message
10.Test with valid username and password-Successful scenarion with Username size -6 and password size -6
11.Test with valid username and password-Successful scenarion with Username size -10 and password size -10
Sunday, February 14, 2010
Manual Testing Part1-SDLC Models
Software Delopment Life Cycle is nothing but a Stages involved in software development process.
We have many software development life cycle models and only few are popular in indusrty we will take those models.
1.Water Fall model
2.V-model
3.Prototyping Model
4.Spiral Model
1.Water Fall Model
For What type of projects we use a water fall model :
When we have complete requirement.
We are not expecting any changes after starting a project.
Planning to complete with less resourse and less budget .
How it looks -->
Advantages
This model is very simple model to follow .
All the activities are done one after the other .
We get defined output at the end of each stages and one stage output will be input to next stage.
Can be completed with less resourses .
Tracing project progress is simple and easy.
Disadvantages
If requirement is changing frequently then we cannot use this model.
Since testing is post development activity , it take more time to complete the project.
2.V-Model
For What type of projects we use a V- model :
Used for most of the commercial project , even when requirements are not freezed in the begining.
How it looks ->
V-model is also called Verfication and Validation (V&V) model ,V-model is so powerful becouse of the these concepts .
3.Prototyping Model :
The spiral model is a software development process combining elements of both design and prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts.
The new system requirements are defined in as much detail as possible. This usually involves interviewing a number of users representing all the external or internal users and other aspects of the existing system.
A preliminary design is created for the new system.This phase is the most important part of "Spiral Model". In this phase all possible (and available) alternatives, which can help in developing a cost effective project are analyzed and strategies are decided to use them. This phase has been added specially in order to identify and resolve all the possible risks in the project development. If risks indicate any kind of uncertainty in requirements, prototyping may be used to proceed with the available data and find out possible solution in order to deal with the potential changes in the requirements.
A first prototype of the new system is constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the final product.
A second prototype is evolved by a fourfold procedure:
evaluating the first prototype in terms of its strengths, weaknesses, and risks;
defining the requirements of the second prototype;
planning and designing the second prototype;
constructing and testing the second prototype.
We have many software development life cycle models and only few are popular in indusrty we will take those models.
1.Water Fall model
2.V-model
3.Prototyping Model
4.Spiral Model
1.Water Fall Model
For What type of projects we use a water fall model :
When we have complete requirement.
We are not expecting any changes after starting a project.
Planning to complete with less resourse and less budget .
How it looks -->
This model is very simple model to follow .
All the activities are done one after the other .
We get defined output at the end of each stages and one stage output will be input to next stage.
Can be completed with less resourses .
Tracing project progress is simple and easy.
Disadvantages
If requirement is changing frequently then we cannot use this model.
Since testing is post development activity , it take more time to complete the project.
2.V-Model
For What type of projects we use a V- model :
Used for most of the commercial project , even when requirements are not freezed in the begining.
How it looks ->
Verfication-Static Testing technique used from beginning to end to impliment the quality aspects .
Reviews ,approvals and meetings are the verification activities .
Validation -Dynamic testing technique used in the testing phase ,validation is nothing but actual testing .
Testing the software by writing and executing test case are all validation actvities.
The V model attempts to give increased importance to testing related activities, by dividing the life cycle into development and testing phases.
The model relates each development phase to its associated testing phase. Thus in this life cycle model, work on the testing phases is carried out in parallel.
For example acceptance test phase may be carried out along with the requirements phase. Similarly system test planning activities of the system-testing phase needs not wait for unit testing to be computed.
Advantages :
1.Becouse of the two testing technique verification and validation ,this model help to acheive good quality software compare to other model .
2.Since there will be separate team for testing and development activities ,project progress will be fast .
Disadvantage :
1.Since more people are involved in software development ,it is more expensive model.
For What type of projects we use a Prototype- model :
We use prototype model when client is not able to give the complete requirement .
How it looks ->
The prototyping development process is explained in the following steps
1.Collect the initial requirement from the client .
2.Design the prototype by using SDLC
3.Demonstrate the prototype to client
4.Impliment client comments in the SRS ,then freez the SRS.
Advantages :
1.We will get the complete SRS.
Disadvantage :
1.The effort and investment invested for designing prototype will not be bared by client.
4.Spiral Model
The spiral model is a software development process combining elements of both design and prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts.
The steps in the spiral model iteration can be generalized as follows:
The new system requirements are defined in as much detail as possible. This usually involves interviewing a number of users representing all the external or internal users and other aspects of the existing system.
A preliminary design is created for the new system.This phase is the most important part of "Spiral Model". In this phase all possible (and available) alternatives, which can help in developing a cost effective project are analyzed and strategies are decided to use them. This phase has been added specially in order to identify and resolve all the possible risks in the project development. If risks indicate any kind of uncertainty in requirements, prototyping may be used to proceed with the available data and find out possible solution in order to deal with the potential changes in the requirements.
A first prototype of the new system is constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the final product.
A second prototype is evolved by a fourfold procedure:
evaluating the first prototype in terms of its strengths, weaknesses, and risks;
defining the requirements of the second prototype;
planning and designing the second prototype;
constructing and testing the second prototype.
Subscribe to:
Posts (Atom)