HP LoadRunner Version 12.02 Tutorials

LoadRunner Introduction tutorial: This video introduces HP LoadRunner and the loadrunner performance testing process. It also explains how to download and install LoadRunner.

LoadRunner business process and sample web application tutorial: First, we gather the requirements. This includes identification of the business processes to be tested. In this video, we understand what a business process is and see a sample business process. Then execute that business process in the sample web application provided with LoadRunner. This application is the HP Web Tours application. In performance testing, when we run the business process, we should choose the most common or at least realistic test data. Our requirement gathering should include finding this test data.

LoadRunner VuGen Vuser script tutorial: In this video, I have explained how to create the automated performance testing script in LoadRunner Virtual User Generator (VuGen). In VuGen, we can create a single protocol script and record the business process. We can edit the generated Vuser script to enhance it. VuGen user interface has several useful features like Solution Explorer, Step Navigator, Editor, Output pane, Errors pane, Bookmarks pane and Thumbnail Explorer.

LoadRunner Tutorial 4 - Vuser Script Replay: In this video, I have explained how to replay the recorded Vuser script. The results of the replay or playback are shown in the replay summary tab in the VuGen. These are shown in the test results window and the replay log. We can save the replay log as a text file. LoadRunner VuGen provides runtime settings, which are individual settings for each Vuser script. These runtime settings include run logic, pacing, log, think time, browser emulation and speed simulation. We can playback a Vuser script from the command prompt instead of VuGen.

LoadRunner Tutorial 5 – Parameterization parameters data-driven Vuser script: In this particular video, I have explained one of the concepts to make the Vuser script ready for load testing. This is parameterization. It means that instead of using a fixed value in our Vuser script, we can have a parameter. In the load test, different Vusers would use different values so this makes the Vuser script more realistic. Also, this separates the data from the script code making the Vuser script data-driven.

LoadRunner Tutorial 6 – text check and image check: In this video, we see one more concept to make the Vuser script ready for load testing. This is content checks. In order to verify that the server returns the correct responses, we can use text checks or image checks. The default is that the text checks and image checks are disabled during playback. This is because they consume more memory. We need to enable these in run-time settings. We can implement the text check with web_reg_find function. We can implement the image check with the web_image_check function.

LoadRunner Tutorial 7 – Transactions: In this video, we see one more important concept to make the Vuser script ready for load testing. It is transactions. A transaction is a part of a Vuser script. A transaction is used to measure the time it takes to complete one or more actions of a business process. We insert lr_start_transaction marker before the first step and an lr_end_transaction marker after the last step of our transaction. In HP LoadRunner VuGen, we can mark any number of transactions in a Vuser script. However, the name of each transaction has to be different. The LoadRunner Controller measures the time it takes to perform each transaction.

LoadRunner Tutorial 8 - Controller - Manual Scenario: In this video, we start with the LoadRunner component called Controller. Using Controller, we can set up the performance test, run it and monitor the performance test as it is running. The settings of a performance test are called a scenario. We can set up a Manual Scenario. Here we need to specify the number of virtual users. We add the Vuser scripts in the Scenario Groups pane and schedule the scenario in the Scenario Schedule pane. Our scenario settings should be as close as possible to what happens in the real production environment.

LoadRunner Tutorial 9 - Controller user interface and manual scenario continued: In this video, we understand the user interface of the Run tab in LoadRunner Controller. It has the panes for scenario groups, scenario status, available graphs, graph display and graph legends. In the Vusers dialog box, we can stop any vuser, add vusers, run vusers, see the tasks of any vuser and see the vuser log. We can see the errors, warnings and other messages in the output window.

LoadRunner Tutorial 10 - Controller goal oriented scenario explained: In this video, we understand the goal-oriented scenario in Controller. In a goal-oriented scenario, we specify the goal. For example, transaction response time or number of hits per second. LoadRunner creates a scenario based on the goal automatically. There are five types of goals, Vusers, transactions per second, transaction response time and for web applications, pages per minute or hits per second.

LoadRunner Tutorial 11 - Analysis and SLA: In this video, we learn about the Analysis component of LoadRunner. Analysis collects and consolidates the test logs from all the load generators. Using Analysis, we can see the performance test results. In Analysis, we can analyze the performance test results by comparing the measurements to our performance requirements. Or we can review multiple graphs or even merge several graphs into one graph. We also learn about SLA (Service Level Agreement). SLA are one or more goals specified for the load test scenario. Analysis compares the goals with the test results. Analysis finds out if the SLA statuses passed or failed.

LoadRunner Tutorial 12 - Analysis detailed explanation: In this video, we dive deeper into the Analysis component of LoadRunner. Analysis shows the summary report with sections of statistics summary, worst performing transactions, scenario behavior over time and transaction summary. We can view graphs. In addition, we can merge graphs together. In order to see the factors related to a transaction’s performance, we can use auto-correlate. In Analysis, both HTML report and Microsoft Word report are available.

Test Design Techniques - Equivalence Partitioning, Boundary Value Analysis, Decision Tables, Use Case Testing and State Transition Testing

Equivalence Partitioning and Boundary Value Analysis tutorial: This software testing tutorial explains the test design techniques and the benefits of using them (save time and find more defects). It explains equivalence partitioning and boundary value analysis test design techniques with a number of examples. So that you understand the EP and BVA techniques and remember them. Equivalence partitioning and boundary value analysis are used in both black box testing like system testing and white box testing like unit testing.

Decision Table Testing tutorial with examples: In this video, we understand a decision table. A decision table is a table of all possible conditions and corresponding actions. It is used to show complicated logic without forgetting any combination of conditions. Decision tables help in testing by listing all possible input conditions. First, we see a decision table example with conditions having binary values i.e. True or False values. Then we see another decision table example with conditions having multiple values. Then, we see the steps to simplify or minimize the decision table.

Use Case Testing - test design techniques tutorial: In this video, we understand use cases, review a sample use case and write test cases for the example use case. A use case is a list of steps to complete a task in the system. These steps define the sequence of interactions between the actor and the system under test. The actor can be a user of the system or it can be another system. The use case lists the main scenarios (and optional exceptional scenarios). A use case may be accompanied by a use case diagram, but not always.
In use case testing, we review the use case e.g. the ATM cash withdrawal use case should only have the steps related to cash withdrawal, not the steps to view balance or deposit cash because the latter steps belong to other use cases. The use case should list all the steps in the normal workflow (scenario). Each step in the use case should be testable. The use case should list each alternate workflow. We design test cases to test the normal workflow and each alternate workflow.  We can design the test data using other test design techniques like equivalence partitioning and boundary value analysis. When we run the test cases, we should look out for any missing workflow(s), any missing step(s) in any workflow, boundary value defects etc.

State Transition Testing - test design techniques tutorial: In this video, we understand state transition testing. A state is a particular condition in which the system can exist. A transition is movement from one valid state to another valid state. State transition testing is used when the system under test can be thought of being in a finite number of states. In state transition testing, we test all the valid transition between states. We can also test for invalid transitions to ensure that they are not allowed. State transition testing is explained in this video with the help of examples showing state transition diagrams, state tables and how to design test cases to test valid transitions 

 

Path Testing in Software Testing with Example

 

Data Flow Testing in Software Testing with Example

 

Mutation Testing in Software Testing

 

Orthogonal Array Testing in Software Engineering | Orthogonal Array Testing Example

 

Test Ideas, Test Requirements Design