Working with iTest -- Videos that will empower you

New features in iTest 4.1

Web Services Module — Test and automate your enterprise applications (EMS, OSS/BSS etc.) directly through the programming API using SOAP or RESTful Web Services.

Virtual testbeds -- VTB -- Controlling emulation for any device in a topology — You can control how emulation is used for any device in a topology in any test case that uses the device:

Test report diff feature -- Comparing two test reports — Quickly compare test results side-by-side to identify key differences in your tests.

Swing -- Latest feature enhancements — Watch demonstrations of the latest feature enhancements

Selective step reporting — By default, each step that executes in a test is added to the test report. You have the option to specify that a particular step should not appear in test reports (the step executes normally, it simply is not reported).

iTestRT support for Quality Center — The qc options for iTestRT cause iTest to publish the test report to the Quality Center server, domain, and project that you specify at the command line

Including charts when exporting test reports — When you export test reports as HTML, iTest includes all charts as JPEG images in the first step of the test case.

Spirent Avalanche -- Run scripts directly — You can run a test using the Tcl scripts generated by Avalanche

HP Quality Center 10 adds parameters directly — QC 9.2 has technical limitations that did not allow iTest to add parameters to the default location in QC 9.2. Instead, the parameters were added to a special design step. QC 10.0 does not have this limitation, so iTest can now publish parameters to the proper location in QC.

VNC sessions — Drive OS-related controls (Windows, Mac, or Linux) as part of your overall system test (for example, triple-play testing, VOIP testing, VPN connection tests, and so on).

VMWare vSphere sessions — Automate virtual machines using iTest: Create, retrieve, update, delete, start, stop your VMs as part of testing and automating your virtualized environments

NTAF — iTest supports an alpha NTAF integration.

Refactoring iTest resources -- renaming, moving, or deleting files — iTest auto-updates dependency relationships when you refactor files

Web sessions -- iTest captures link IDs whenever possible — To ensure that test cases are as robust as possible, iTest captures the ID for a link (rather than

SOAP Attachment Support — Attachments are supported for the SOAP Web Services module.

Showing first 15 of 22 results

Developing test cases

Creating Your First Test Case — Watch as we use iTest to capture the steps of a manual test, and then save them into an automated test case.

Adding Simple Analysis — Watch the video to learn how to add analysis rules to a test case to specify pass/fail criteria and to control execution based on the response.

Making an existing test case portable — This video demonstrates how to make an existing test case portable (that is able to run in various topologies). This example starts with the test case that we created to automate traffic generator testing.

Parameters files — You can define parameters and their values in several places in iTest. One powerful way to cause iTest to use a particular set of parameter definitions when executing any test case is to create a parameter file. This video provides a brief introduction to parameters files.

Procedure Enhancements in iTest 3.3 — This video provides a brief introduction to procedure enhancements that were introduced in iTest 3.3.

XPath for iTest Users — This video provides an overview on using XPath queries in iTest.

Parameters -- Managing and verifying source and merge settings — Quickly identify merged parameters and view the values that will be used for execution. Double click to change parameter values and descriptions in grid. Click to reveal source of parameters in test cases.

Emulating responses -- Enhancements to Virtual Testbeds (VTB) — Generate and save multiple emulations for the same step/device within a response map library. Easily edit responses and/or add field substitution to quickly create a more robust emulation engine for comprehensive testing of existing or upcoming features.

Synchronization Commands — iTest supports multi-threaded execution: Run tests (of the same session type) in parallel without conflict.

QuickCalls -- Custom actions in automated tests and during manual testing — You can add custom actions to the built-in iTest actions. QuickCalls are custom actions that you define for a session profile or device. QuickCalls make it easy to execute a predefined set of steps---either as a single QuickCall step in a test case or as a single button click in an interactive session. The result is a simpler, cleaner test case that automation teams can quickly transition to regression.

Using the iTest Tool Development SDK to create new session types — iTest supports writing custom tools that you can integrate into iTest - with all of the same power as all of the other tools that ship with iTest itself. You can define your own sets of actions, can create your own user interfaces, and all of this will support full automation without your users have to write any script.

URI syntax in iTest — One of the main benefits of using URIs rather than URLs is that field replacements are supported in URIs. Watch the video to learn about the specific encoding changes associated with the transition from URLs to URIs.

Emulating responses from sessions -- Virtual Testbeds (VTB) — iTest can emulate the behavior of one, multiple, or all of your devices when executing a test case. As the test executes, if you have enabled emulation on certain steps or sessions, iTest will execute those steps by emulating how the device would have responded, but without even attempting to communicate with the device.

iTest commands for working with lists and strings — Commands for working with lists and strings:

Scheduling execution -- Test suites and jobs — A "test suite" document allows you to define one or more test groups.

Showing first 15 of 21 results

Test execution

Creating Your First Test Case — Watch as we use iTest to capture the steps of a manual test, and then save them into an automated test case.

Parameters files — You can define parameters and their values in several places in iTest. One powerful way to cause iTest to use a particular set of parameter definitions when executing any test case is to create a parameter file. This video provides a brief introduction to parameters files.

XPath for iTest Users — This video provides an overview on using XPath queries in iTest.

Parameters -- Managing and verifying source and merge settings — Quickly identify merged parameters and view the values that will be used for execution. Double click to change parameter values and descriptions in grid. Click to reveal source of parameters in test cases.

iTest HTTP sessions -- Performing GET and POST — Using an HTTP session, a test case can talk directly with a device using the HTTP protocol operations GET and POST.

Thread-safe (sync) operations in iTest test cases — iTest supports multi-threaded execution and provides tools for managing thread synchronization.

Virtual testbeds -- VTB -- Controlling emulation for any device in a topology — You can control how emulation is used for any device in a topology in any test case that uses the device:

Including charts when exporting test reports — When you export test reports as HTML, iTest includes all charts as JPEG images in the first step of the test case.

Display Current Step During Test Execution — During execution and when you pause execution, the Test Case editor highlights the currently executing step and indicates it with a yellow arrow in the left column. You can turn this feature on and off with a preference setting in Fanfare > General > Execution.

Test reports in iTest

External database for iTest reports — Configure iTest to store all execution data on an external database, making it easier to share detailed test report data with team members. tr

Finding text, patterns, or execution issues in test reports — Press Ctrl+F in the Test Report editor (or click Edit > Find/Replace in the menu). Specify the text and use options to narrow the search to certain fields, specify regex search, or include other views in the Find operation.

Test Reports view — Test Reports view: You can filter reports by test case name or group reports by time, result, and more.

Test report diff feature -- Comparing two test reports — Quickly compare test results side-by-side to identify key differences in your tests.

Selective step reporting — By default, each step that executes in a test is added to the test report. You have the option to specify that a particular step should not appear in test reports (the step executes normally, it simply is not reported).

Including charts when exporting test reports — When you export test reports as HTML, iTest includes all charts as JPEG images in the first step of the test case.

Analysis rules: Validating responses and returning data from responses

Adding Simple Analysis — Watch the video to learn how to add analysis rules to a test case to specify pass/fail criteria and to control execution based on the response.

Analysis rule enhancements — This video provides a brief introduction to new analysis rule features that were added in iTest 3.2.

Response Filtering -- Filter a response before analysis or validation — Response filtering allows you to define a set of filters that will be applied to a response before it goes further into response mapping and analysis.

Analysis rules & events in test reports — {color:black}Previously, the Test Report editor did not contain analysis rules, actions or events resulting from test case execution. This made it difficult for testers to debug what actually happened and what, if anything, went wrong during test case execution. The Test Report editor now displays the information.{color}

Response Maps: Auto-generating powerful queries in iTest

Adding Simple Analysis — Watch the video to learn how to add analysis rules to a test case to specify pass/fail criteria and to control execution based on the response.

Auto Response Mapping — The Auto response mapping feature causes iTest to take a best-try on auto-generating a response map and the associated queries.

XPath for iTest Users — This video provides an overview on using XPath queries in iTest.

Emulating responses -- Enhancements to Virtual Testbeds (VTB) — Generate and save multiple emulations for the same step/device within a response map library. Easily edit responses and/or add field substitution to quickly create a more robust emulation engine for comprehensive testing of existing or upcoming features.

Response Filtering -- Filter a response before analysis or validation — Response filtering allows you to define a set of filters that will be applied to a response before it goes further into response mapping and analysis.

Creating a "block" response map — Block mapping is a technology that we reserve for responses that have more complex structures than either a pattern or a table.

Topologies

Emulating responses -- Enhancements to Virtual Testbeds (VTB) — Generate and save multiple emulations for the same step/device within a response map library. Easily edit responses and/or add field substitution to quickly create a more robust emulation engine for comprehensive testing of existing or upcoming features.

Graphical Topology Editor — Create and edit graphical topologies in iTest using industry-standard TBML files.

Emulating responses from sessions -- Virtual Testbeds (VTB) — iTest can emulate the behavior of one, multiple, or all of your devices when executing a test case. As the test executes, if you have enabled emulation on certain steps or sessions, iTest will execute those steps by emulating how the device would have responded, but without even attempting to communicate with the device.

Virtual testbeds -- VTB -- Controlling emulation for any device in a topology — You can control how emulation is used for any device in a topology in any test case that uses the device:

General iTest topics

Workspace Overview — An overview of the iTest workspace for beginners.

Building a session profile — Watch as we create a session profile (the set of session configuration settings) that lets us interact with a DUT.

Activity-based UI (Activities Perspective) — The Activities perspective gives you easy access to your most comman tasks (for example, developing test cases or browsing test reports). Watch the video for a quick tour.

Using the iTest Tool Development SDK to create new session types — iTest supports writing custom tools that you can integrate into iTest - with all of the same power as all of the other tools that ship with iTest itself. You can define your own sets of actions, can create your own user interfaces, and all of this will support full automation without your users have to write any script.

Detecting missing prompts in CLI sessions — While a test is executing, iTest will attempt to detect the case where an unknown prompt has been received. Rather than waiting forever, iTest will signal this situation to the user - giving them a chance to confirm that a new unknown prompt has, indeed, been received - causing the new prompt to be added to the session profile, and allowing the execution to proceed.

Tips and Tricks -- Little-known features

What's New in iTest 4.0 -- PDF document

Using the iTest scriptGet and scriptGet actions — Using 'scriptGet' to get and 'scriptSet' to set the value of a Tcl variable

Thread-safe (sync) operations in iTest test cases — iTest supports multi-threaded execution and provides tools for managing thread synchronization.

Using source control with iTest

Virtual testbeds -- VTB -- Controlling emulation for any device in a topology — You can control how emulation is used for any device in a topology in any test case that uses the device:

Including charts when exporting test reports — When you export test reports as HTML, iTest includes all charts as JPEG images in the first step of the test case.

Configuring iTest sessions: Session profiles

iTest session type video tutorials – Telnet, Web, and so on

iTest session types -- Video tutorials

Building a session profile — Watch as we create a session profile (the set of session configuration settings) that lets us interact with a DUT.

Ixia Traffic

Web sessions

Java Swing — This video provides a brief introduction to Java Swing, which was added in iTest 3.2.

Wireshark sessions — Watch a brief introduction to Wireshark sessions in iTest.

AptIxia IxLoad — This video provides a brief introduction to IxLoad sessions in iTest.

Syslog sessions — This video provides a brief introduction to Syslog sessions in iTest.

Agilent N2X -- Configuring a session profile — Starting Agilent N2X sessions from iTest

SSH -- Configuring a session profile — Port forwarding allows iTest to securely connect to devices in a remote network through SSH tunneling.

Aptixia IxNetwork — This video provides an overview of IxNetwork sessions in iTest.

Flex (Flash) Module — You can now use iTest to test your Adobe® Flash® applications developed using Adobe Flex®. iTest captures and automates one or more Flash applications hosted from a web page, similar to the native capture, targeting, and analysis concepts used in other iTest GUI tools such as Web and Java Swing..

Spirent TestCenter GUI — You can drive and automate the most common functions of TestCenter directly within iTest. Capture configuration changes in real time, eliminating the need to upload additional configuration files.

Spirent Avalanche Integration — iTest Avalanche sessions provide a rich user interface for users to interact directly with Avalanche. And, as always, these interactions can be captured and integrated into automated tests quickly and easily. The tool takes care of interpreting and displaying the vast amount of information returned by Avalanche from its runs. And all of this data is nicely structured, making it easy to analyz the data in iTest test cases.

Java Swing Native Capture — In iTest 3.4, we've added native capture support to Java Swing applications launched via iTest's "swing" application. You are still able to use the "remote control" ability if and when you want to. But now you can also perform these actions directly within the application-under-test.

Showing first 15 of 27 results

iTestRT

Sharing iTest assets -- iTar files, iTestRT, and project dependencies — As iTest gets integrated into large deployments, it becomes more and more important that there are clean ways to share and hand off iTest test cases (and other assets like response map libraries, procedure libraries, etc.)

Sharing iTest assets

Workspace Overview — An overview of the iTest workspace for beginners.

Sharing iTest assets -- iTar files, iTestRT, and project dependencies — As iTest gets integrated into large deployments, it becomes more and more important that there are clean ways to share and hand off iTest test cases (and other assets like response map libraries, procedure libraries, etc.)

HPQC -- Using iTest with HP Quality Center

Publishing test cases to HP Quality Center — This video shows how to publish test cases to HP Quality Center.

HPQC Test Execution — This video shows how to execute iTest test cases from within HPQC, a new feature that was added in iTest 3.3.

HPQC -- Brush up on some important features — iTest supports HPQC parameters, automated sync-up of new test cases, ability to attach reference files to test cases, and collecting and attaching artifacts for test runs. Watch the videos to accelerate your work day!

HPQC -- Publishing tests and test reports in batches — You can do a whole batch of work in iTest and then update QC with all of your work (rather than having to ask iTest to update QC one test or one report at a time).

HPQC Overview -- Working with Quality Center and iTest — iTest is strongly integrated with Quality Center. You can start test execution and monitor the results in both applications.

HPQC -- Working with iTest while using Quality Center as the primary user interface — If you start with a new or existing test of type ITEST in QC, add design steps and define custom properties as needed. Then click a button to open the iTest Test Case editor so you can create the associated test case in iTest.

HPQC -- Working with Quality Center while using iTest as the primary user interface — Work on a new or existing executable iTest test case and then publish it to a new or existing associated test in QC.

HPQC -- Artifacts folder — Some test cases may produce artifacts (like log files) during execution. If you specify an Artifacts location, then when iTest publishes the test report to QC, the contents of the specified folder are uploaded to QC as attachments to the report.

HPQC -- Auto-renumbering or naming test steps — You can cause iTest to auto-generate step names for the QC test.

HPQC -- Creating a test case — While using the New Test Case wizard to create a new test case document, if you select Associate this test case with a test in Quality Center, then the wizard presents additional pages where you configure the connection to the QC server and specify the QC test and test instance to associate with the test case.

HPQC -- Sharing parameters between Quality Center and iTest — When you publish a test case to QC, iTest publishes the parameters as they would be used at runtime – parameters defined in the test case, in the associated testbed (if specified), and in the parameter file (if specified) – all after inheritance/merging.

HPQC -- Storing test case information in Quality Center — You can store project variables (project main, project path, and so on) in test execution issues.

HPQC -- Associating reference files with a test — To fully define a test and to describe it for coworkers, you might want to associate files with the test (a config file and a topology diagram, for example).

iTestRT support for Quality Center — The qc options for iTestRT cause iTest to publish the test report to the Quality Center server, domain, and project that you specify at the command line

HP Quality Center 10 adds parameters directly — QC 9.2 has technical limitations that did not allow iTest to add parameters to the default location in QC 9.2. Instead, the parameters were added to a special design step. QC 10.0 does not have this limitation, so iTest can now publish parameters to the proper location in QC.

iTest licensing

Borrowing iTest licenses for use offline — Borrow an iTest license to continue test development offline. Does not require an active connection to license server.

Maintaining and managing iTest

Activity-based UI (Activities Perspective) — The Activities perspective gives you easy access to your most comman tasks (for example, developing test cases or browsing test reports). Watch the video for a quick tour.

New Builder and Dependencies — In iTest 3.4, the build system has been greatly improved. Now the builder not only understands what files any given file is dependent on, but also understands the nature of these dependencies. So now when a file is modified, only those files that would be affected by that specific change will be revalidated.

iTest testbeds

Testbeds — This video provides a brief introduction to new testbed features that were added in iTest 3.2.

Emulating responses -- Enhancements to Virtual Testbeds (VTB) — Generate and save multiple emulations for the same step/device within a response map library. Easily edit responses and/or add field substitution to quickly create a more robust emulation engine for comprehensive testing of existing or upcoming features.

Emulating responses from sessions -- Virtual Testbeds (VTB) — iTest can emulate the behavior of one, multiple, or all of your devices when executing a test case. As the test executes, if you have enabled emulation on certain steps or sessions, iTest will execute those steps by emulating how the device would have responded, but without even attempting to communicate with the device.

HA (high availability) test cases

HA -- High availability test cases — HA devices are special in that any number of redundant processors (nodes) can perform system operations (that is, act as the master). iTest enables you to test HA devices in a simple, intuitive way.

New features in iTest 4.0

External database for iTest reports — Configure iTest to store all execution data on an external database, making it easier to share detailed test report data with team members. tr

Activity-based UI (Activities Perspective) — The Activities perspective gives you easy access to your most comman tasks (for example, developing test cases or browsing test reports). Watch the video for a quick tour.

Web Enhancements in 4.0 — Utilize X, Y coordinates, capture page URLs, and perform clear cache / clear cookies operations as part of your web testing. iTest can now also capture cookies and to enable cookie tests. Browser proxy settings can also be configured as preferences.

HPQC -- Brush up on some important features — iTest supports HPQC parameters, automated sync-up of new test cases, ability to attach reference files to test cases, and collecting and attaching artifacts for test runs. Watch the videos to accelerate your work day!

Parameters -- Managing and verifying source and merge settings — Quickly identify merged parameters and view the values that will be used for execution. Double click to change parameter values and descriptions in grid. Click to reveal source of parameters in test cases.

Emulating responses -- Enhancements to Virtual Testbeds (VTB) — Generate and save multiple emulations for the same step/device within a response map library. Easily edit responses and/or add field substitution to quickly create a more robust emulation engine for comprehensive testing of existing or upcoming features.

SSH -- Configuring a session profile — Port forwarding allows iTest to securely connect to devices in a remote network through SSH tunneling.

Borrowing iTest licenses for use offline — Borrow an iTest license to continue test development offline. Does not require an active connection to license server.

Synchronization Commands — iTest supports multi-threaded execution: Run tests (of the same session type) in parallel without conflict.

Graphical Topology Editor — Create and edit graphical topologies in iTest using industry-standard TBML files.

QuickCalls -- Custom actions in automated tests and during manual testing — You can add custom actions to the built-in iTest actions. QuickCalls are custom actions that you define for a session profile or device. QuickCalls make it easy to execute a predefined set of steps---either as a single QuickCall step in a test case or as a single button click in an interactive session. The result is a simpler, cleaner test case that automation teams can quickly transition to regression.

What's New in iTest 4.0 -- PDF document

HPQC Overview -- Working with Quality Center and iTest — iTest is strongly integrated with Quality Center. You can start test execution and monitor the results in both applications.

HPQC -- Working with iTest while using Quality Center as the primary user interface — If you start with a new or existing test of type ITEST in QC, add design steps and define custom properties as needed. Then click a button to open the iTest Test Case editor so you can create the associated test case in iTest.

HPQC -- Working with Quality Center while using iTest as the primary user interface — Work on a new or existing executable iTest test case and then publish it to a new or existing associated test in QC.

Showing first 15 of 21 results

New features in iTest 3.4

Aptixia IxNetwork — This video provides an overview of IxNetwork sessions in iTest.

Flex (Flash) Module — You can now use iTest to test your Adobe® Flash® applications developed using Adobe Flex®. iTest captures and automates one or more Flash applications hosted from a web page, similar to the native capture, targeting, and analysis concepts used in other iTest GUI tools such as Web and Java Swing..

Spirent TestCenter GUI — You can drive and automate the most common functions of TestCenter directly within iTest. Capture configuration changes in real time, eliminating the need to upload additional configuration files.

Spirent Avalanche Integration — iTest Avalanche sessions provide a rich user interface for users to interact directly with Avalanche. And, as always, these interactions can be captured and integrated into automated tests quickly and easily. The tool takes care of interpreting and displaying the vast amount of information returned by Avalanche from its runs. And all of this data is nicely structured, making it easy to analyz the data in iTest test cases.

Java Swing Native Capture — In iTest 3.4, we've added native capture support to Java Swing applications launched via iTest's "swing" application. You are still able to use the "remote control" ability if and when you want to. But now you can also perform these actions directly within the application-under-test.

Reference session profiles and reference testbeds — Base session profiles now support both "reference session profiles" and "reference testbeds" to allow better management of test assets.

Using the iTest Tool Development SDK to create new session types — iTest supports writing custom tools that you can integrate into iTest - with all of the same power as all of the other tools that ship with iTest itself. You can define your own sets of actions, can create your own user interfaces, and all of this will support full automation without your users have to write any script.

Detecting missing prompts in CLI sessions — While a test is executing, iTest will attempt to detect the case where an unknown prompt has been received. Rather than waiting forever, iTest will signal this situation to the user - giving them a chance to confirm that a new unknown prompt has, indeed, been received - causing the new prompt to be added to the session profile, and allowing the execution to proceed.

URI syntax in iTest — One of the main benefits of using URIs rather than URLs is that field replacements are supported in URIs. Watch the video to learn about the specific encoding changes associated with the transition from URLs to URIs.

Response Filtering -- Filter a response before analysis or validation — Response filtering allows you to define a set of filters that will be applied to a response before it goes further into response mapping and analysis.

Finding text, patterns, or execution issues in test reports — Press Ctrl+F in the Test Report editor (or click Edit > Find/Replace in the menu). Specify the text and use options to narrow the search to certain fields, specify regex search, or include other views in the Find operation.

HPQC -- Publishing tests and test reports in batches — You can do a whole batch of work in iTest and then update QC with all of your work (rather than having to ask iTest to update QC one test or one report at a time).

Database Client — The Database Client provides a simple user interface where users can enter SQL queries - SELECT, UPDATE, INSERT, DELETE, etc. - anything supported by their database. And the tool allows for predefined query templates so that end-users don't have to remember the syntax and schemas involved.

Emulating responses from sessions -- Virtual Testbeds (VTB) — iTest can emulate the behavior of one, multiple, or all of your devices when executing a test case. As the test executes, if you have enabled emulation on certain steps or sessions, iTest will execute those steps by emulating how the device would have responded, but without even attempting to communicate with the device.

Test Reports view — Test Reports view: You can filter reports by test case name or group reports by time, result, and more.

Showing first 15 of 25 results

New features in iTest 3.3

Publishing test cases to HP Quality Center — This video shows how to publish test cases to HP Quality Center.

Auto Response Mapping — The Auto response mapping feature causes iTest to take a best-try on auto-generating a response map and the associated queries.

Procedure Enhancements in iTest 3.3 — This video provides a brief introduction to procedure enhancements that were introduced in iTest 3.3.

HPQC Test Execution — This video shows how to execute iTest test cases from within HPQC, a new feature that was added in iTest 3.3.

New features in iTest 3.2

Testbeds — This video provides a brief introduction to new testbed features that were added in iTest 3.2.

Analysis rule enhancements — This video provides a brief introduction to new analysis rule features that were added in iTest 3.2.

Publishing test cases to HP Quality Center — This video shows how to publish test cases to HP Quality Center.

Working with iTest -- Videos that will empower you

New features in iTest 4.1

Developing test cases

Test execution

Test reports in iTest

Analysis rules: Validating responses and returning data from responses

Response Maps: Auto-generating powerful queries in iTest

Topologies

General iTest topics

Configuring iTest sessions: Session profiles

iTestRT

Sharing iTest assets

HPQC -- Using iTest with HP Quality Center

iTest licensing

Maintaining and managing iTest

iTest testbeds

HA (high availability) test cases

New features in iTest 4.0

New features in iTest 3.4

New features in iTest 3.3

New features in iTest 3.2

Labels:

Children (75)