The CloudBees Smart Tests CLI includes built-in integrations for test runners and build tools that execute tests built using various frameworks. This means that CloudBees Smart Tests can be used with any test framework, as long as a supported test runner or build tool is used to kick off tests. The primary integration point for CloudBees Smart Tests is your team’s build tool or test runner (for example, the CLI invoked to actually kick off your tests), not the test framework itself. However, some frameworks have their own test runners. For more information about test runners or to view the full list, refer to Integrations.
The following list identifies the supported test frameworks and their corresponding test runners or build tools that integrate with CloudBees Smart Tests.
Appium
If using the Appium framework, check which tool is used to kick off your tests. For instructions to add CloudBees Smart Tests to your CI pipeline, refer to the following integrations:
Cucumber
The Cucumber framework has its own test runner. For more information, refer to Cucumber integration.
GoogleTest
The GoogleTest framework has its own test runner. For more information, refer to GoogleTest integration.
Jest
The Jest framework has its own test runner. For more information, refer to Jest integration.
minitest
The minitest framework has its own test runner. For more information, refer to minitest integration.
nose
The nose framework has its own test runner. For more information, refer to pytest integration.
NUnit
The nunit framework has its own test runner. For more information, refer to .NET test integration.
prove
The prove framework has its own test runner. For more information, refer to prove for Perl integration.
Robot
The Robot framework has its own test runner. For more information, refer to Robot integration.
RSpec
The RSpec framework has its own test runner. For more information, refer to RSpec integration.