Important: This documentation covers Yarn 1 (Classic).
For Yarn 2+ docs and migration guide, see yarnpkg.com.

Package detail

testcafe-reporter-nunit3

NickLargen31.3kMIT-03.1.0

NUnit 3 TestCafe reporter plugin that supports screenshot attachments.

testcafe, reporter, plugin, nunit, nunit3, azure devops

readme

testcafe-reporter-nunit3

Release

This is the NUnit 3 reporter plugin for TestCafe. It currently implements the subset of attributes that Azure DevOps cares about and has not been tested for other scenarios.

Details of the NUnit format can be found at https://github.com/nunit/docs/wiki/Test-Result-XML-Format.

Features:

  • Video and screenshot paths included as test case attachments.
  • Quarantine mode support: passing tests that failed at least once are marked as Inconclusive instead of Passed. The result of each run is specified as text appended to the error message.
  • Fails the test run (via a new failed test case) if the TestCafe process exits without all tests finishing. The provided xunit reporter emits a blank file in these scenarios.
  • Emits fixture and test metadata as <property> elements.

Error details for every failed quarantine run are not currently supported by the TestCafe Reporter API.

Install

npm install testcafe-reporter-nunit3

Usage

An example .testcaferc.json entry that creates nunit3 reports along with standard console logging:

"reporter": [
    "spec",
    {
      "name": "nunit3",
      "output": "results/handy-dandy-report.xml"
    }
  ]

See the official reporter documentation for more information.

changelog

3.1.0 (2022-11-14)

Features

3.0.1 (2021-05-07)

Bug Fixes

3.0.0 (2020-07-16)

Features

  • include video paths as attachments (8748e1c), closes #5

BREAKING CHANGES

  • File paths are absolute so that they work seamlessly in the simple case of running tests from a different directory than the Build.SourcesDirectory where test results are uploaded from. This may impact usage if you are moving test result files around after they are generated, such as running tests in Docker.

2.0.2 (2020-07-16)

Bug Fixes

  • remove runtime dependency of tslib (3bcc104)

2.0.1 (2020-04-05)

Bug Fixes

  • remove implicit dependency on slash module, it is not part of node's standard library (de21462)
  • update dependencies for minor security vulnerability fixes (decb430)

2.0.0 (2020-03-16)

Bug Fixes

  • ::set-env not found during ci (7216c83)
  • improve file path calculations so that test outputs are OS agnostic (53beef9)
  • use GitHub syntax for sharing environment variables between steps (2e8b371)
  • use OS agnostic file paths (3a3fddc)

Features

  • add missing details to error messages and properly align stack traces, (f965994)
  • emit relative file paths instead of absolute (a46388b)
  • fail test run if not all tests complete (704700c)
  • test ci configuration with a prerelease minor version bump (3125801)
  • update TestCafe past 1.0 (f9b9b57)
  • use an emoji to emphasize the distinction between different errors in the same test (1182c88)

BREAKING CHANGES

  • Errors in the test process can no longer be detected by checking for a blank result file.
  • Screenshots and source locations use relative file paths. When uploading results make sure your current working directory relative to your screenshots directory is the same as when the tests ran.

2.0.0-beta.1 (2020-03-16)

Bug Fixes

  • improve file path calculations so that test outputs are OS agnostic (53beef9)
  • use OS agnostic file paths (3a3fddc)

Features

  • add missing details to error messages and properly align stack traces, (f965994)
  • emit relative file paths instead of absolute (a46388b)
  • fail test run if not all tests complete (704700c)
  • update TestCafe past 1.0 (f9b9b57)
  • use an emoji to emphasize the distinction between different errors in the same test (1182c88)

BREAKING CHANGES

  • Errors in the test process can no longer be detected by checking for a blank result file.
  • Screenshots and source locations use relative file paths. When uploading results make sure your current working directory relative to your screenshots directory is the same as when the tests ran.

1.1.0-beta.3 (2020-03-15)

Bug Fixes

  • ::set-env not found during ci (7216c83)

1.1.0-beta.2 (2020-03-15)

Bug Fixes

  • use GitHub syntax for sharing environment variables between steps (2e8b371)

1.1.0-beta.1 (2020-03-15)

Features

  • test ci configuration with a prerelease minor version bump (3125801)

1.0.5 -> 1.0.12 (2020-03-15)

  • Play around with CI configuration

1.0.4 (2020-03-14)

  • Update Handlebars to resolve security vulnerability
  • Start using GitHub Actions with Semantic Release for publishing

1.0.3 (2020-07-22)

Initial working release