software testing videos

software testing videos

Keyword view in QTP

Keyword view in QTP:

After recoding all the operations, QuickTest displays them as steps in theKeyword view and generates them as a script in the Expert view.

The Keyword View enables you to create and view the steps of your component in a keyword-driven, modular, table format.


Following are the various columns available in Keyword view:

1.   Item: 
2.   Operation: 
3.   Value: 
4.   Assignment: 
5.   Comment:
6.   Documentation: 

Keyword View Screenshots (Click on the picture to enlarge):

Click here to know more about -> Keyword view in QTP

Object Repository in QTP

Object Repository

Test objects: are stored representations of the actual objects (or controls) in your application. QuickTest creates test objects by learning a set of the properties and values of the objects in your application
Object Repositories 
QuickTest can store the test objects it learns in two types of object repository files, shared and local. 

                                      
                                                      Click on the image to enlarge
A shared object repository contains test objects that can be used in multiple actions. By associating a shared object repository with an action, you make the test objects in that repository available for use in the action. (.tsr)

                                      

                                                        Click on the image to enlarge

A local object repository stores test objects that can be used in one specific action. The objects in this type of repository cannot be used in any other action.

Local object repositories are useful for backing up your test objects, or for learning one or several objects (using the Navigate and Learn tool or by recording on them). (.mtr)

Click here to know -> More about QTP object repositories and the types

Checkpoints in QTP

Checkpoints:

Checkpoint is a verification point that compares a current value for a specified property with the expected value for that property.

When you add a checkpoint, QuickTest adds a checkpoint to the current row in the Keyword View and adds a Check Checkpoint statement in the Expert View. By default, the checkpoint name receives the name of the test object on which the checkpoint was created.

Types of QTP Checkpoints:

Screenshots of various Check points in QTP (Click on the images to enlarge):

1.      Standard Checkpoint:

2.      Image checkpoint:

3.      Bitmap checkpoint:

4.      Table Checkpoint:

5.      Text checkpoint:

6.      Text-Area checkpoint:

7.      Page Checkpoint:

8.      Database checkpoint:

9.      Accessibility checkpoint:

10.  XML checkpoint (from Application):

11.  XML checkpoint (from Resource)           

             

For more information go to More information on QTP Checkpoints           

File Types in QTP (File Extensions)

File Types in QTP (File Extensions)

QTP File Types:

QTP File	File Type
QTP Script File	.mts
Batch test File	.mtb
Environmental Variable Files	.txt,
Input/Output Data (Datatable)	.xls
Recovery Scenario Files	.qrs
Library Files	.vbs
Object repository (Shared)	.tsr
Object repository (Per Action/Local)	.mtr
Action File	.mst

Click here for the -> Complete list of all file types (extensions) in QTP

Testing Defintions

Black box testing
not based on any knowledge of internal design or code. Tests are based on requirements and functionality. 
White box testing
based on knowledge of the internal logic of an application's code. Tests are based on coverage of code statements, branches, paths, conditions. 
Unit testing
the most 'micro' scale of testing; to test particular functions or code modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done unless the application has a well-designed architecture with tight code; may require developing test driver modules or test harnesses. 
Incremental integration testing
continuous testing of an application as new functionality is added; requires that various aspects of an application's functionality be independent enough to work separately before all parts of the program are completed, or that test drivers be developed as needed; done by programmers or by testers. 
Integration testing
testing of combined parts of an application to determine if they function together correctly. The 'parts' can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems. 
Functional testing
black-box type testing geared to functional requirements of an application; this type of testing should be done by testers. This doesn't mean that the programmers shouldn't check that their code works before releasing it (which of course applies to any stage of testing.) 
System testing
black box type testing that is based on overall requirement specifications; covers all combined parts of a system. 
End-to-end testing
similar to system testing; the 'macro' end of the test scale; involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.
Sanity testing
typically an initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort. For example, if the new software is crashing systems every 5 minutes, bogging down systems to a crawl, or destroying databases, the software may not be in a 'sane' enough condition to warrant further testing in its current state. 
Regression testing
re-testing after fixes or modifications of the software or its environment. It can be difficult to determine how much re-testing is needed, especially near the end of the development cycle. Automated testing tools can be especially useful for this type of testing. 
Acceptance testing
final testing based on specifications of the end-user or customer, or based on use by end-users/customers over some limited period of time. 
Load testing
testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the systems response time degrades or fails. 
Stress testing
term often used interchangeably with 'load' and 'performance' testing. Also used to describe such tests as system functional testing while under unusually heavy loads, heavy repetition of certain actions or inputs, input of large numerical values, large complex queries to a database system, etc. 
Performance testing
term often used interchangeably with 'stress' and 'load' testing. Ideally 'performance' testing (and any other 'type' of testing) is defined in requirements documentation or QA or Test Plans. 
Usability testing
testing for 'user-friendliness'. Clearly this is subjective, and will depend on the targeted end-user or customer. User interviews, surveys, video recording of user sessions, and other techniques can be used. Programmers and testers are usually not appropriate as usability testers. 
Install/uninstall testing
testing of full, partial, or upgrade install/uninstall processes.
Recovery testing
testing how well a system recovers from crashes, hardware failures, or other catastrophic problems. 
Security testing
testing how well the system protects against unauthorized internal or external access, willful damage, etc; may require sophisticated testing techniques. 

Compatibility testing

testing how well software performs in a particular hardware/software/operating system/network/etc. environment. 
Exploratory testing
often taken to mean a creative, informal software test that is not based on formal test plans or test cases; testers may be learning the software as they test it. 
Ad-hoc testing
similar to exploratory testing, but often taken to mean that the testers have significant understanding of the software before testing it. 
User acceptance testing
determining if software is satisfactory to an end-user or customer.
Comparison testing
comparing software weaknesses and strengths to competing products.
Alpha testing
testing of an application when development is nearing completion; minor design changes may still be made as a result of such testing. Typically done by end-users or others, not by programmers or testers. 
Beta testing
testing when development and testing are essentially completed and final bugs and problems need to be found before final release. Typically done by end-users or others, not by programmers or testers. 
Mutation testing
a method for determining if a set of test data or test cases is useful, by deliberately introducing various code changes ('bugs') and retesting with the original test data/cases to determine if the 'bugs' are detected. Proper implementation requires large computational resources.

ISTQB syllabus & mock tests

ISTQB Syllabus for Foundation Level


ISTQB MOCK TESTS