9.10 - Selenium / TestNG

Selenium / TestNG — Knowledge Base articles.

Selenium / TestNG (Knowledge Base Articles)

Contents

Knowledge Base articles for Selenium and TestNG testing in Appvance IQ:

Best Practices for TestNG and Selenium Testing in AIQ

Best Practices for TestNG and Selenium Testing in AIQ

Use this page to maintain Selenium/TestNG projects that are executed through AIQ. Keep the framework deterministic, portable, and easy to diagnose.

When to use this guidance

  1. Keep tests independent and avoid hidden ordering dependencies.
  2. Externalize environment URLs, credentials, and test data.
  3. Use explicit waits and stable locators rather than fixed sleeps.
  4. Package dependencies consistently and validate the artifact before uploading or executing in AIQ.
  5. Log meaningful assertions and screenshots so failures can be triaged quickly.

Note: For new scriptless functional coverage, prefer Scenario Editor where it fits the use case.

Last updated: September 21, 2026

Difference between selenium and selenium rc

Selenium

Xpath
Fast less accurate.
Simple Pages
Maintained by Appvance,Gargoyle Soft


Selenium RC

XPaths, Link=,id=,css=
More accurate.
More resource consuming
Complex pages
Maintained by Selenium Community.

If you have any feedback on this topic, please contact us at documentation@appvance.ai

Last updated: October 15, 2026

Error: Missing bundle seleniumrc version

Problem

When I try to play my scenario, I see:

Error: Node testnode failing: Missing bundle: Missing bundle seleniumrc version 2.45

Issue

Selenium version mismatch exists.

A component of each scenario are its Resource bundle properties, one of which is the Selenium RC version (seleniumrc).

The Selenium RC version on the test node must match the version specified in the Resource bundle properties (assumes a Selenium RC script type is used)

Resolution

  1. On the TestNode machine, navigate to <utp install path>\TestNode\bundles\seleniumrc
  2. Note the name (version number) of the directory within the seleniumrc directory
  3. Open an existing scenario in the Scenario Builder.
  4. Select Resources
  5. Locate the seleniumrc listing in the Bundles section
  6. Confirm the version box contains the same version number as noted in step 2 (above)

Once the version in the Scenario Builder matches the installed version, save the scenario and run it again.

If you have any feedback on this topic, please contact us at documentation@appvance.ai

Last updated: October 15, 2026

How to Create a Class in Eclipse?

How to Create a Class in Eclipse?
a.Create a new Project in Eclipse.
b.Right Click Project Name and click Package and provide the package name.
c.Right Click Package Name and click Class and provide the Class name

If you have any feedback on this topic, please contact us at documentation@appvance.ai

Last updated: October 15, 2026

How to Create a TestNG Class in Eclipse?

*To install TestNG in Eclipse: http://toolsqa.com/selenium-webdriver/install-testng/
a.Right Click package Name
b.Select Build Path->Configure Build path->Select Libraries tab
c.Click Add External Jars -Browse and add downloaded selenium standalone jar file.
d.Create a TestNG class with TestNG annotations (DataProvider to read data from csv file)

If you have any feedback on this topic, please contact us at documentation@appvance.ai

Last updated: October 15, 2026

Run a JAR with Dependencies from Scenario Editor

Run a JAR with Dependencies from Scenario Editor

This page replaces the obsolete “Scenario Builder” wording with current Scenario Editor terminology. Use this guidance only when a Java artifact must be executed as part of an existing AIQ workflow.

Before execution

Validation workflow

  1. Run the JAR in a controlled non-production environment.
  2. Check exit code, stdout, stderr, and generated files.
  3. Run a small AIQ validation execution before scheduling or scaling.
  4. Attach troubleshooting details to the related maintenance ticket if execution fails.

Last updated: September 8, 2026

How to run CSV Enabled TestNG DPL scenario in Appvance IQ using TestNG Data Provider

Below article explains about Data Enabling using TestNG Data Provider.
It covers below mentioned topics:

If you have any feedback on this topic, please contact us at documentation@appvance.ai

Last updated: October 15, 2026

Run Data-Enabled TestNG Scenarios

Run Data-Enabled TestNG Scenarios

Use TestNG data providers for maintained Java/TestNG assets that still run through AIQ. For current Scenario Editor tests, prefer DPLs or approved AIQ test data sources when they can meet the same need.

Validation workflow

  1. Run the TestNG suite locally or in CI with a small data set.
  2. Confirm dependency packaging and Java version compatibility.
  3. Execute from AIQ with a controlled data sample.
  4. Review output for data, classpath, and environment failures before scaling.

Last updated: September 8, 2026

Run Functional Scenarios from a TestNG JAR in AIQ

Run Functional Scenarios from a TestNG JAR in AIQ

Use this guidance for existing TestNG class JARs that are still required by an AIQ workflow. For new functional automation, use current Scenario Editor patterns unless a Java/TestNG integration is specifically required.

Pre-run checklist

Validation steps

  1. Run the JAR in the CI or local maintenance environment.
  2. Execute a small AIQ validation run.
  3. Review output for classpath, driver, locator, and data errors.
  4. Document whether the asset remains maintained or should be migrated to Scenario Editor.

Last updated: September 8, 2026

Run Selenium Java Page Object Projects in AIQ

Run Selenium Java Page Object Projects in AIQ

Use this page for maintained Selenium Java Page Object Model projects that still need AIQ execution. Treat these projects as specialized or legacy assets and prefer Scenario Editor for new functional coverage when possible.

Maintenance checklist

AIQ validation

  1. Build the project through the approved CI process.
  2. Run a focused AIQ execution with a small data set.
  3. Review output for driver, locator, data, and environment failures.
  4. Record artifact version and execution ID for traceability.

Last updated: September 8, 2026

Running Selenium Script on a Linux machine.

I was trying to run a selenium script on one of the Linux Red hat machine and was getting the below message:

Firefox console output:
Error: no display specified
Error: no display specified

Note: The Linux Red Hat was configured earlier to work with XVFB Firefox.

Solution:

Linux natively does not have capability to run any application that launches UI.

Below 2 steps needs to be executed for the browsers to launch and run the test.

Xvfb :99 -ac -screen 0 1280x1024x24 &

export DISPLAY=:99

If you have any feedback on this topic, please contact us at documentation@appvance.ai

Last updated: October 15, 2026

TestNG: Unable to run tests in Eclipse using Firefox 43

Last updated: October 15, 2026