Learning and Technology

This is my second post from the HP LoadRunner series. As I discussed earlier, here I will be discussing an overview of LoadRunner Controller . So before going into detail, let me recap the prerequisites. Create script – Checked Replay Script – Checked Updating script if required (Add transaction, Parameterization and Content Check) – Checked  Runtime settings and Iterations – Checked Assuming the script is absolutely fine i.e. error free and ready to be passed on Controller, let us get familiar with the UI first. I will be using LoadRunner 9.5, the screens may vary at your end depending on the version you are using.   The UI The Controller has a Title bar, Menu bar, tool bar and a Status bar. After these we have multiple sections or panes.   The first is Scenario Groups pane. We can add multiple scripts or a single script and name them as a Group.  Next is Scenario schedule, here we define how the load will be passed and executed. We have two types of scenario group. Manual

As the name suggests, LoadRunner is an automated performance testing product by HP . It works by generating actual load on the server, by replacing human users with the virtual user also know as a VU.    Let us understand and create a load test. In this post I will be working on LoadRunner version 9.5 so the UI may vary with the latest version 11.5x . As I discussed in my earlier post, the LoadRunner is categorized in four components.  The product is so vast that it cannot be covered in a single post. So, I will be covering LoadRunner in multiple posts. Keep visiting for updates!! Virtual user Generator (VuGen) Also known as VuGen, this component allows capturing end user business processes by generating an automated script against the performed actions. To open VuGen, Click on Start button >> Programs >> LoadRunner >> Applications >> Virtual User Generator. Let us get familiar with the interface. On opening the VuGen, you will see a screen a

With the ongoing technology advancements and digitization, everyone is trying to go online. The web traffic is increasing day by day. And this directly impacts on an application’s performance. Load testing of an application has become a necessity now. An application must be at least accessible or one may say stable up to 5,000 users.    Conducting a load test manually requires a lot of human and machine efforts, which increases cost. To overcome this cost. A lot of automated performance software’s are made, which I have already discussed in my previous post .  Before working on any of the automated software, one should first understand the load testing process. Here in this post I will be sharing the process of load testing using HP LoadRunner . You may find similar words like Plan, Create, Define, Run and Analyze as presented in the functional testing process (QTP). So the theme remains same and the parameter(s) varies with the type of testing you are about to perform.

Being a part of software industry for many years, I have came across multiple group of people having diverse thoughts. Being a QA I often share my experiences with fellow colleagues and friends. One important question whose answer is typically vague and not convincing to me is over the ‘LOAD / STRESS TESTING’.  Recently I was engaged in a project which requires load testing, so I shoot a message in my social and professional circle to know, if anyone can suggest and guide me over a good tool. I was little shocked to hear most of the replies that they have never performed a load testing activity. Okay I admit load testing can be expensive, but being an expert and experienced resource in the field and still have no knowledge is quite unpleasant for me (No offence to anyone). So there I pull my socks up, grab a cup of tea and started little research over the top available load testing tools. Here I will be sharing my recommendations and experiences over the top load testing tools. 

You may find thousands of articles on the discussed topic so what’s so new and catchy in my post?? Below are the lists of to-do’s I have learned from my experience under the field of being a quality assurer. So let’s start. Viewers are most welcome to share their thoughts, experiences following a comment below :) So here we go with some quick tips. Its just a initial draft, as there are many things which needs to be tested, some are scenario dependent, some application, so we have alot f constraints. I will be adding things time to time whenever i recall things, so keep checking. Exploratory testing – think like a dumb user who just have started using the computer and have no idea where and what to click. Test all possible unrealistic scenarios. [NOTE : Exploratory testing varies as per target audiences, if your software is meant for the professionals than exploratory testing level varies, you need to focus more on functional, Client requirements than, focusing on system fa