Software Testing using HP tools with videos.

1. HP SOFTWARETESTING PROJECT

2. What is testing?
 Testing is the process of executing a program with the intent
of finding errors and verifying that the program satisfies the
specified requirements
 Testing is done for following reasons:
• To detect errors in a software product
• To verify that a software product conforms to its requirements
• To establish confidence that a program or system does what it is
supposed to do
• To evaluate an attribute or capability of a software product and
determine that it meets the required results

3. Types of testing
Based on test execution, testing can be classified into two categories.
 ManualTesting: Manual testing is a testing technique where the test engineer prepare
test cases manually and execute them to identify defect in the software.
 Automation Testing: Automating software testing involves developing test scripts
using scripting languages such as Python, Java script orTCL(Tool Command Language),
so that test cases can be executed by computers with minimal human intervention and
attention.

4. Unified functional testing
• UFT: HP Unified FunctionalTesting (UFT) software, formerly known as HP
QuickTest Professional (QTP), provides functional and regression
test automation for software applications and environments. HP UFT enables
functional tests to be carried out automatically to increase the speed and cost
effectiveness of application development and delivery.
• Recording
• Object Recognition
• Checkpoints
• Parameters

5.  UFT is a combined solution for GUI and API service testing.
 UFT enables testing functionality across multiple layers, such as the front-end GUI
layer as well as back-end service layers.
 UFT helps you to cut time-to-market by starting automated functional testing earlier
in your process.
 GUITesting:
• UFT’s GUI testing solution deploys the concept of keyword-driven testing to enhance
test creation and maintenance.
• Keyword-driven testing is a technique that separates much of the programming work
from the actual test steps.
• Using the keyword-driven approach, test automation experts have full access to the
underlying test and object properties.
Unified functional testing

7. Working with UFT tool
Step 1: click the application.
Step 2: select add-in i.e.(Web, Active-X etc.).
Step 3: click file-> new test -> give the name -> click create.
Step 4: set up recording.
Step 5: start recording of an application.
Step 6: after recording VB script will be generated.
Step 7: Run and check result.

8. Action Flow :

9. Login into application:
Description –
Manual testing is the process of manually testing software for defects. It requires a tester to play the role of
an end user and use most of all features of the application to ensure correct behaviour.

10. Booking flight :

11. GeneratedVB script of an application :

12. ResultView of the generated script :

13. Replay of simple tested Desktop application(Video) :

14. Test Cases for login page :

15. Breakpoint in AUT :

16. Replay of tested application with breakpoint (Video):

17. Checkpoints in AUT :
Applying checkpoint

18. Checkpoint :

20. Replay of tested application with checkpoint(Video) :

22. Action Flow :
1. Sign-In
2. Compose Mail
3. Delete Mail
4. Sign-Out

23. Login into Gmail application :

24. Replay of simple tested web application(video) :

25. Test cases of login for Gmail web application

26. Application Lifecycle Management
 ALM is a set of pre-defined processes that start somewhere in the business as an idea,
a need, a challenge or a risk and then pass through different development phases such
as Requirements definition, design, development, testing, deployment, release and
maintenance spanning across an entire lifecycle of a product.Throughout the ALM
process, each of these steps is closely monitored and controlled, followed by proper
tracking and documentation of any changes to the application
 ALM is a broader perspective than the Software development lifecycle, which is
limited to the phases of software development such as requirements, design,
coding, testing, configuration, project management, and change management.
ALM continues after development until the application is no longer used, and
may span many SDLCs.

27. • This is the little tricky part to explain. Generally this is where lot of
debates happened. To most of us the test scripts are the automation
scripts written in any of the programming language like VB script,
Java, python etc. which can be interpreted and executed automatically
by a testing tool.
• Yes this is 80% correct by not 100%. To my definition a test script is
nothing but a test case fabricated with test data. A single test case can
be fabricated with the combination of multiple set of test data to form
multiple test scripts of the same test case.
• Which means, a test script can be,
• Manual test scripts – are the manual test cases fabricated with the multiple
set of test data to enable even a layman to do the testing as per the
documentation
• Automation test Script – are the programmed test cases with the
combination of test data which can be executed by a tool
Test Script:

28. ALM test result :

29. Load Runner
 HPE Load Runner is a software testing tool from . It is used to test applications,
measuring system behavior and performance under load.
 HPE Load Runner can simulate thousands of users concurrently using application
software, recording and later analyzing the performance of key components of
the application.
 Load Runner simulates user activity by generating messages between
application components or by simulating interactions with the user interface
such as key presses or mouse movements.The messages/interactions to be
generated are stored in scripts. Load Runner can generate the scripts by
recording them, such as logging HTTP requests between a client web browser
and an application's web server.

30. Load Generator generates the load against the application by following scripts
 VuGen (Virtual User Generator) for generating and editing scripts
 Controller controls, launches and sequences instances of Load Generator - specifying which
script to use, for how long etc. During runs the Controller receives real-time monitoring data
and displays status.
 Agent process manages connection between Controller and Load Generator instances.
 Analysis assembles logs from various load generators and formats reports for visualization of
run result data and monitoring data.

31. LoadRunner different component