Blog

This is part 2 in a series of 17. To start at the beginning, first read Agile vs Fragile: A Disciplined Approach or an Excuse for Chaos.
As an executive leader of a testing organization of around 750 testers, I had the opportunity to experience many different development methodologies.  Our organization supported multiple software development methodologies including everything from Waterfall to Scrum.  I found it interesting that each team approached the methodology differently.  I found that of the multiple teams that were Read Entire Entry

The server-side system requirements for HP ALM 11.5, HP ALM 11.5 Essentials and HP Quality Center Enterprise 11.5 are outlined in this article, including the minimum hardware requirements, recommended environment configurations, supported operating systems, database servers, application servers, web servers and virtual environments.

If you plan to install HP ALM 11.5, check out our article that provides step-by-step instructions for an ALM 11.5 installation and our article on the client-side system requirements for HP ALM 11 Read Entire Entry

On February 11-13, 2001, a group of seventeen people met at The Lodge at Snowbird ski resort in Utah.  This group shared a common desire to improve their skills on the ski slopes and to improve the software they developed. Their collaboration created the Agile Software Development Manifesto. The participants of this meeting represented different perspectives on software development, but they all agreed that they wanted to develop an alternative to long project cycles. They may have discussed the concepts of what makes a team agile Read Entire Entry

UPDATE:  Please visit the Jobs page for our latest job postings.
  Read Entire Entry

While delivering our HP UFT/QTP training course, I am frequently asked why it is necessary to launch the application under test (AUT) after QTP (QuickTest Pro) has launched (and the appropriate add-ins are loaded).

The simple answer is that UFT/QTP recognizes objects by “hooking” into the AUT. This is accomplished by “watching” for applications to hook into so UFT can interact with the AUT to support record and replay functionality as well as expose the underlying objects. The potential side effect of not launching QTP before Read Entire Entry

It’s no secret that mobile applications, native, hybrid and web based, are in high consumer demand. The world is moving from the desktop to mobile devices. Tablets are projected to outsell PCs by Q3 2012 and mobile devices outshipped PCs in 2011. Mobile devices and tablets are the technology of the future. If your organization is not already invested in mobile applications, there’s a strong chance you will be in the near future.

Our clients asked us for solution recommendations and requirements to tackle the task of automat Read Entire Entry

After the official release of HP ALM 11.5 (Application Lifecycle Management), previously known as HP Quality Center (QC), we detailed a step by step single server installation and noted the primary differences (relating to the installation) between version 11.0 and 11.5. The remainder of this article outlines a high level overview of the new features in ALM 11.5. You can also read HP’s official documentation on What’s New in HP ALM 11.5 (Application Lifecycle Management).
Editions
ALM has been divided into four editions:  HP AL Read Entire Entry

There are multiple testing considerations associated with each aspect of the BYOD implementation, End Point Testing, MDM Solution Testing, or Corporate Solution Testing.

Probably the most obvious strategy area is end point testing. This testing focuses on the mobile device itself and whether or not the device is able to access corporate applications, such as email, contacts, calendar, VPN, and so on, that are part of the corporate BYOD strategy.

The five suggestions that follow address what I consider to be the Top 5 testi Read Entire Entry

Several years back, I found this posting and thought it was interesting. I am just now getting around to sharing it. Try this code if you want. I use this LoadRunner utility code to assist in analyzing test data, or to write desired dynamic data from scripts to .csv files outside of LoadRunner scenario results folders.

This code requires some script parameters to be defined, and you have to pre-allocate your folder where you want to write your data. The code also checks to see if you are running from Vugen or the Controller. I Read Entire Entry

This is a basic scripting technique for enhancing your VuGen scripts to add error checking and detailed logging (in this case a web HTTP status code that is in the 4XX – 5XX range) for specific steps.

First, set up a parameter called {pIteration} that uses the Iteration Number type to automatically keep track of the iteration. At the beginning of my action.c I might start with something like this:
// Declare Variables
int rc = 0, iHttp;
lr_vuser_status_message(“Starting iteration Number: %s”,
lr_eval_string({pIterati Read Entire Entry