Skip to main content

NUnit

Submit and collect your NUnit results in Testiny to track automated test runs. By integrating NUnit with Testiny, you can gain valuable insights into your testing process. Track automation results over time, identify frequently failing tests, and detect patterns in test failures to fix CI failures and find flaky tests.

NUnit

Running NUnit Tests & Generating Reports​

There are several ways to run your NUnit tests, for example using common IDEs, such as Visual Studio or Rider, or to use dotnet test. Depending on the framework there might be different settings needed to save result files, e.g. you might need to set TestOutputXml to an output folder and/or install the NUnitXml.TestLogger package and specify it as a reporter.

Testiny supports the NUnit 3.0 XML format, so you don't need to transform your report file to another format.

Import Results to Testiny​

Make sure you've generated an API key and use the Testiny CLI to import the results to Testiny:

export TESTINY_API_KEY=****
npx @testiny/cli automation --project ID_OR_KEY --source "frontend" --nunit output/*.xml

In the above example, the environment variable TESTINY_API_KEY is set to authenticate the request. The --project flag specifies the target Testiny project using its ID or key and the --source flag categorizes the test results (e.g., frontend, backend, integration tests, ...). The --nunit flag specifies the format of the specified test result file(s).

Once executed, the Testiny CLI will automatically create a new automated test run in Testiny and import all results from the specified report(s).

More resources​

Here are some further resources to help you get started with integrating NUnit with Testiny, including CI/CD integration examples, a full automation guide, and the Testiny CLI.