External tools

HCL OneTest API is primarily GUI-based, but you can also run or view tests, suites, and stubs outside of the HCL OneTest API.

Several methods of externally running or viewing HCL OneTest API test artifacts are available:
  • Command-line: After they are created in the GUI, tests, stubs, and suites can be run manually or in an automated fashion from the command line. For details, see Running tests by using the command line.
  • Apache Ant: HCL OneTest API can generate a custom Apache Ant script that runs selected tests or suites as part of your overall build process. For details, see Generating Ant scripts to run tests or suites.
  • VAPI-XP: HCL OneTest API can generate a VAPI-XP Java script that can be pasted into HP Quality Center to run the selected test, suite, or stub as part of your Quality Center test plan. For details, see Generating VAPI-XP scripts with HP Quality Center.
  • HP QuickTest Professional: You can run resources from HCL OneTest API from QuickTest Professional (and vice versa) by using scripting and command-line options in both the tools.
  • Jenkins: You can run or view tests and suites within Jenkins. For details, see HCL OneTest API and Jenkins.
  • Maven: HCL OneTest API can generate a Maven script that runs selected stubs, tests, or suites as part of your Maven build process. For more information, see Generating Maven scripts to run stubs, tests, or suites.
Note: If command line or Apache Ant execution is used in projects that use permissions, single sign-on must be configured. For single sign-on configuration, add a properly configured krb5.ini file (one that includes your realm and key distribution center) to your Windows directory (typically C:\WINDOWS). Alternatively, provide these details as arguments in Library Manager (for command line) or within the Apache Ant script (manually added). For more information, see Working with Library Manager.