For customers using WebdriverIO with the Cucumber framework, the recommended integration with SpiraTest is to have WebdriverIO generate JUnit XML reports and then import those results into Spira using our generic xUnit integration. This approach uses the WebdriverIO native reporting model, supports deployment in CI/CD pipelines, and avoids coupling the test runtime directly to Spira-specific reporter logic. WebdriverIO officially supports a JUnit reporter for XML output, and our xUnit integration is designed to import xUnit/JUnit-style XML files into Spira.
This article explains the process for running Selenium WebDriver test scripts written in Java using JUnit, RemoteLaunch and Spira.
Note: This article has been updated to reflect the modern SpiraTest JUnit extension (contained in JUnitExtension.zip), which uses Annotations and Listeners rather than the deprecated SpiraTestTestCase inheritance model.
One of our customers was reporting that their instance of our TestNG plugin was reporting a 502 Connection Reset by Peer error. We did some debugging with them, and the issue appears to be a bug inside some versions of the Java Virtual Machine (VM) itself.