|
Functional Testing
 |
ManageEngine QEngine Web Functional Test tool
automates the functional testing of your web applications
that use standard technologies such as, J2EE(JSP), ASP,
.NET, PHP, and other HTML based formats including JavaScripts/VBScripts.
This tool provides simple Record and Playback technique
to recognize all the controls in your web application. It
supports different browsers such as IE, Mozilla, and Firefox
on Windows and Linux platforms. |
| Compare
QEngine with other Functional Testing Tools |
Web Functional Test Tool Features
Powerful and simplified script creation
- Simplifies script creation, enabling you to record and replay
every action performed on the web application, such as selections,
string input, frames, table data, pop-up windows including alerts
and prompts, multiple window mode, checkings/uncheckings, etc.
It tests any web application developed using HTML, DHTML, ASP,
Java, JavaScript, etc with a minimal learning curve.
- "Object-based recording" recognizes page elements
and controls symbolically rather than with raw screen coordinate.
- Keyword-driven test using pre-defined keywords to define actions
for a test case.
- Secure Recording on password fields.
- Ability to record and playback Flash elements in Internet Explorer.
- The web-based script editor displays line numbers and highlights
the currently executing line number during playback. This enables
you to view and track the lines being replayed in the script editor
parallel to the actions being replayed in the web browser.
Standard Scripting Language - Jython
- Web browser events are recorded using standard scripting language
- Jython which gives you the flexibility to extend script functionality.
It provides the fastest and easiest way to manipulate test scripts,
allowing testers to focus on application testing and eliminating
the need to learn the scripting language.
- Jython scripts provide more control over testing and have the
ability to invoke regular Java classes. It also provides support
for conditional statements and looping constructs such as, For,
if…else, While, etc. to meet the most complex test requirements.
Multiple Verification Points
- Add multiple checkpoints in a test case for any HTML object,
such as, GUI checkpoint (for HTML Element, HTML Table or Web Text)
and database checkpoints (to verify database values). This is
done using the Test Case Configuration screen, by just clicking
on the respective GUI object from the web browser. This allows
you to verify if the data and multiple attribute values of a GUI
object behave as expected by comparing the actual and expected
results.
- Add single checkpoints to validate a single property value
of a GUI object using the Insert Single Checkpoints screen.
- To test a functionality completely, you can add a combination
of checkpoints (Element, Table and DB checkpoint or Text, DB and
Element checkpoint) in a test case and set criteria to check for
AND, OR, NOT conditions or use expressions for the test case to
pass.
Data-Driven Testing
Data-Driven test scripts and checkpoints enable you to test the
web application in different scenarios by just changing the test
data in an external datasource. Thus, enabling you to extensively
test all the aspects of the web application in terms of test data.
- Create data-driven test scripts to add variables or parameterize
lines in your test scripts using the Data Configuration Screen.
A single test script can be created to test with multiple sets
of data where the values are substituted at runtime from an external
database, CSV file or using user-defined variables, or reserved
variables. This facilitates maximum script resusability and eliminates
the need to re-create test scripts for each set of data.
- Create test cases or verification points in scripts with multiple
sets of data. A single test case (Element or Table checkpoint
in a test case) can be created to test the attribute values with
multiple sets of data where the values are substituted at runtime
from an external database, CSV file or using user-defined variables,
or reserved variables. This facilitates test case re-usability
and eliminates the need to re-create test cases for each set of
data.
GUI Object Mapping
- The GUI Object map stores all the window and element objects
that represent the actual objects in the tested web page. When
web sites and web applications change frequently, the object property
values in the recorded test script may also need to change. This
would enable QEngine to recognize the changed object during playback.
Rather than re-recording the script, you can change the property
values in the GUI Map file using the Application Map Object Editor.
This Editor provides a tree-view of all the window and element
objects in the left pane. The right-pane displays all the properties
of the selected window or element object which can be edited.
- Option to include specific conditions such, starts with, ends
with, etc using the Condition column in the right-pane of Application
Map Object Editor to meet specific testing requirements.
Rich library of built-in functions
- Easy-to-use Function Generator tool provides a non-erroneous
way to insert specific functions from a rich library of verification
functions. This will help you to extend the testing functionality
and analyze the test results.
- Verification functions can be added to check or get property
values of any HTML Object specific to the web page, verify database
values, check file contents, verify any string, XML validation,
etc. The various categories of functions include:
- Window Functions
- XML Validation Functions
- String Functions
- HTML Element Functions
- HTML Check Functions
- HTML Get Functions
- HTML Table Functions
- HTML General Functions
- Database Functions
- File Operations
- General Functions
- Default Functions
Internationalization Support
- Uni-code enabled script allows you to test your web applications
in multiple languages. A single recorded script can be replayed
in any locale by setting the required language and country in
the Play Settings option. Multi-lingual and localized testing
increases your web applications reliability and accountability
worldwide.
- Provides a library of functions to enable localized testing.
- changeLocale - To dynamically modify the localized language
in the recorded script.
- getLocalizedString - To get the localized string for a
given key.
- getLocaleCountry - To get the selected locale country.
- getLocaleLanguage - To get the selected locale language.
Multi-Browser Support
- QEngine allows you to validate web applications in popular
browsers (Microsoft Internet Explorer/Firefox/Mozilla) and supports
interoperability between browsers. Scripts recorded in Microsoft
Internet Explorer can be replayed in Mozilla, Firefox and viceversa.
This eliminates the need to re-record scripts in each browser
and thus saves time.
Cross-Platform Support
- Test scripts recorded in Windows can be replayed in Linux without
re-creating the scripts, allowing you to quickly validate Web
Application Functionality in multiple platforms.
Runtime Settings
Provides considerable flexibility, enabling testers to configure
a wide range of options using the Settings tab that affects the
playback of functional test scripts. All these configurations are
optional.
- Option to playback the recorded script in the normal user recorded
speed or to execute in fast mode.
- Option to change the order of script execution using the automatic
or manual sequencing mode.
- Options to handle web and popup exceptions.
- Option to e-mail test case failures to team members and other
related statff.
- Option to send summary reports to configured e-mail IDs.
- Option to playback the recorded script with any language and
country, supporting internationalization.
- Option to change the default local GUI map file to a global
map file. This maintains a single map file for the entire suite.
- Option to playback the recorded script with any server and
port.
Debugger and Multiple Play Modes
Provides a wide range of play modes to run and debug test scripts.
The play modes include:
- Verify mode to continuously playback the entire script without
any breakpoints.
- Execute From and Execute UpTo modes to set breakpoints and
execute script from a specified line or upto a specified line
to catch errors from a specific point.
- Execute Step mode to step through each line in the script,
repeat steps, stop execution at a particular line or continue
playback of script from a specified line, lets you to easily debug
and diagnose errors in test scripts.
- Update mode to update the web element properties in test cases
before test execution in case they have changed since the last
execution.
Environment-Independent Scripting
- To make test scripts more flexible and environment independent,
many things can be configured on a global basis. This will help
you to make the common settings in one screen and pass variables
from one script to another, enabling users to adapt their test
scripts to new test environments without the need to make changes
in each test script. This includes:
- Globally set variables and get variables using the Global
Variables Editor screen or use the setGlobalVariable(), getGlobalVariable()
and use it across scripts using the callScript().
- Use reserved variables such as $localhost, $date(dd_mm_yyyy),
$nexthour, $nextday, etc or create user-defined variables
using the Data Configuration screen and use it in any test
script with "$" symbol prefixed in the variable
name.
Dynamic Host-Port Variations
- Re-use single script to efficiently test web applications with
different servers and port numbers. Host-Port Settings screen
allows you to specify the server name and port number to dynamically
playback the test scripts with any server and port number without
re-recording the test script. This will also let you to test and
compare the same web application hosted in different servers and
ports.
Automatic Error Recovery System
- Automatic error recovery system to capture unexpected popup
exceptions, web exceptions, script exceptions and object exceptions
during a test run. This provides the ability to automatically
recover from errors and move to the next test run, facilitating
unattended testing.
- Provides a wide range of error recovery options to report exceptions,
capture screenshots for unexpected popups, stop play, close unexpected
popups or call another script when exceptions occur during a test
run.
QEngine Issue Tracking Software
- In addition to test automation of your web applications and
web services, QEngine provides built-in issue tracking software
that helps you to track product defects and manage product enhancement
requests. It enables users to log in defects / requests from any
geographic location and allows all the team members to access
the tracking system from anywhere, anytime. Click here, to learn
more.
Interoperability with Issue Tracking Software
- QEngine allows you to integrate any third-party Bug Tracking
Systems to help you track bugs the way you are used to. Click
here, to know the customization details.
Clear and Powerful Reports
- HTML-based reports are provided to indicate the status of the
test execution. Hyperlinks allow easy navigation through the report. This helps you to quickly identify application failures and clearly
assess application quality.
| Script Summary |
 |
Script Summary Report displays the passed and failed details
for each script executed in the test suite. Provides summary details
of the passed, failed, incomplete, error and total number of test
cases in each script. Hyperlink provided in Script Report navigates
to the detailed failure and complete report for each line executed
in the test script. Links are also provided to view the testout.txt
and testerr.txt files. |
| |
| Script Report |
 |
Script Report displays the details of the scripts executed,
such as, script name, status, debug info, number of lines
passed/failed and detailed passed/failed report for each line
in the test script. |
| |
| Test Case Report |
 |
Test Case Report provides the details of the test cases executed
in the script such as, severity, debug info, actual and expected
result, passed and failed cases, etc. |
| |
| Page Property Report |
 |
Page Property Report displays the properties of the executed
page, such as, Window Title, Window Name, Status, Response
Time, URL, etc. |
| |
|
|
Web
Performance Testing
