Blog

Part 16 in a series of 17. To start at the beginning, first read Agile vs Fragile: A Disciplined Approach or an Excuse for Chaos.
In the traditional development space we are all very familiar with the testing tools that are available. We know about industry leaders such as HP Quality Center, QuickTest Professional and Performance Center.  We understand the value they add to large projects and how they are essential to ensuring that the testing process is well managed and delivered.  But what about Agile?  Do these same tool Read Entire Entry

Part 15 in a series of 17. To start at the beginning, first read Agile vs Fragile: A Disciplined Approach or an Excuse for Chaos.
Often times teams make the argument that Agile means that there is no longer a need for  “independent” teams of testers that verify that the solution was built correctly according to the requirement specifications.  They argue that this is now the role of the “super developer”, and the business representative, who are both embedded into the team.  After all, the business knows what they Read Entire Entry

Part 14 in a series of 17. To start at the beginning, first read Agile vs Fragile: A Disciplined Approach or an Excuse for Chaos.
If you were to survey a group of very frustrated testers about why they have problems with their Agile teams, you would find that in almost all cases they get frustrated trying to get any documentation that helps them identify what to test.  Every time they request even minimal documentation, the development team pushes back and says that documentation isn’t needed because Agile eliminates the need Read Entire Entry

Part 13 in a series of 17. To start at the beginning, first read Agile vs Fragile: A Disciplined Approach or an Excuse for Chaos.
The last Agile principle is all about retrospectives. This is one area where a lot of teams have dropped the ball. They don’t take the time to do retrospectives because people don’t understand the value they bring. They are perceived as a waste of time that could be spent on the next development sprint.  What they fail to realize is that on a long marathon, it is the small corrections in the Read Entire Entry

This is the fourth installment in a multi-part series to address the basics of performance testing applications. It’s for the beginner, but it is also for the experienced engineer to share with project team members when educating them on the basics as well. Project Managers, Server Team members, Business Analysts, and other roles can utilize this information as a guide to understanding performance testing process, the typical considerations, and how to get started when you have never embarked on such a journey.
Let’s use a case Read Entire Entry

Part 12 in a series of 17. To start at the beginning, first read Agile vs Fragile: A Disciplined Approach or an Excuse for Chaos.
Agile principle eleven deals with the team itself. This principle focuses on the enablement of the team to leverage their unique position as the closest people to the problem manage the work.  It also enables the team to safely take risks. The team is typically creating new solutions, and doing it in a rapid fashion. Agile promotes the team trying new things without worrying about being chastised for Read Entire Entry

QTP 11 (and versions 9-10) installs Microsoft Script Debugger to provide the debugging features in QuickTest Pro scripts. Without the debugging engine, all of the QTP debug features are unavailable. Microsoft Script Debugger ships with an archaic version (7.10.3077) of Process Debug Manager (PDM).

Out of the box, QTP provides limited VBScript debugging capabilities. An automation engineer does not have the ability to view the properties/methods of variables/objects in their full extent. Objects, like Object Repository obje Read Entire Entry

Part 11 in a series of 17. To start at the beginning, first read Agile vs Fragile: A Disciplined Approach or an Excuse for Chaos.
The tenth Agile principle focuses on keeping the solution as simple as possible while maximizing value and quality. Agile processes focus on finding the simplest way possible of solving a business problem with quality, not finding the fastest way to code the solution.  Sprints are kept as simple as possible to ensure that all work gets prioritized by using the backlog as the gatekeeper.  In the Read Entire Entry

HP recently released Knowledge Base article KM00211140 for LoadRunner, dealing with decoding the encoded user name and password in a flex call when recording against HP’s Service Manager Service Request Catalog (SRC). SRC  uses both flex and web to communicate to the back end.  The encoding used is Base64. Their example is good,  and could be used as a starting point for encoding/decoding BASE64 for other applications. To pull this off, you will need to include mic_socket.h in the  Globals.h section of the VUgen script . Then Read Entire Entry

One of our customers experienced issues when trying to run TruClient IE over a firewall using the LoadRunner MI Listener component. To narrow the issue down, they tried running other scripts based on different protocols, which worked fine. It was specific to the TruClient protocol. The TruClient script would time out after several minutes. The only error was “initialization failed: reason – timeout”.  To correct the issue, they implemented the following steps:

Modify <LG>\dat\mdrv\mdrv_webIE.datfile. Add the followi Read Entire Entry