Tag Archive: checkpoint

Jan 08 2018

A Simple Function to Return the Result of a “Negative” Checkpoint

Negative tests check that the application or system under test (AUT/SUT) can handle gracefully invalid inputs, such as an invalid username at login, or an invalid ID number when creating a new customer. There is some controversy around the term “negative” for such tests, as pointed by Alon LInetzki here. To me, the term “Negative Testing” …

Continue reading »

Jan 20 2014

Implementing a Generic Verification Function

The following function yields tremendous code savings, as it can evaluate any comparison between a pair of values (e.g., observed vs. expected) in a generic fashion. It accepts three (3) arguments: 1. sOperator – The logical binary operator, such as ‘=’ (equals), ‘=>’ (greater than or equal to), etc. 2. sObserved – A variant value. …

Continue reading »

May 04 2013

Using a Test Object Custom Property as a Function Pointer

In previous posts (1, 2) we’ve discussed the possibility of using custom TO properties. To recap, such properties can be used to: Enhance QTP’s ability to identify certain object classes; To serve as temporary storage for important object metadata that is collected during runtime; To enable global action interoperability (as opposed to output parameters which …

Continue reading »

Sep 08 2012

Using a Test Object Custom Property in Runtime

This article complements the previous post on Using a Test Object Custom Property, in which we discussed the possibility given by QTP to add a custom TOProperty through its Object Identification dialog. Such a property may be used to improve the tool’s capacity to identify Test Objects of particular classes, after implementing its population with data by the AUT’s development team. […] Sometimes, however, we may find it handy to use custom properties just during the runtime session.