All Projects → no23reason → jest-trx-results-processor

no23reason / jest-trx-results-processor

Licence: MIT license
Jest results processor for exporting into TRX files for Visual Studio

Programming Languages

typescript
32286 projects
javascript
184084 projects - #8 most used programming language

Projects that are alternatives of or similar to jest-trx-results-processor

Vstest
Visual Studio Test Platform is the runner and engine that powers test explorer and vstest.console.
Stars: ✭ 624 (+2613.04%)
Mutual labels:  visual-studio, testing-tools
TfsCmdlets
PowerShell Cmdlets for Azure DevOps and Team Foundation Server
Stars: ✭ 75 (+226.09%)
Mutual labels:  visual-studio, vsts
Vstest Docs
Documentation for the Visual Studio Test Platform.
Stars: ✭ 165 (+617.39%)
Mutual labels:  visual-studio, testing-tools
Chutzpah
Chutzpah is an open source JavaScript test runner which enables you to run unit tests using QUnit, Jasmine, Mocha and TypeScript.
Stars: ✭ 549 (+2286.96%)
Mutual labels:  visual-studio, testing-tools
Objectexporter
Object Exporter lets you export out an object while debugging in Visual Studio, the object can be serialized in either C#, JSON or XML.
Stars: ✭ 240 (+943.48%)
Mutual labels:  visual-studio, testing-tools
FakeDataGenerator
fakedatagenerator.herokuapp.com/
Stars: ✭ 18 (-21.74%)
Mutual labels:  testing-tools
test junkie
Highly configurable testing framework for Python
Stars: ✭ 72 (+213.04%)
Mutual labels:  testing-tools
vsts-flutter-tasks
Flutter build tasks for Azure DevOps Pipelines/TFS.
Stars: ✭ 106 (+360.87%)
Mutual labels:  vsts
slntools
Solution Tools for Visual Studio - manages solution files
Stars: ✭ 25 (+8.7%)
Mutual labels:  visual-studio
Cake
Yummy syntax theme for Atom, Brackets, Sublime Text and Visual Studio Code
Stars: ✭ 47 (+104.35%)
Mutual labels:  visual-studio
ffbtools
Set of tools for FFB testing and debugging on GNU/Linux
Stars: ✭ 39 (+69.57%)
Mutual labels:  testing-tools
lyrebird-java-client
lyrebird-java-client 是Lyrebird的一个 Java SDK,通过调用Lyrebird本身提供的API实现在Java项目中控制 Lyrebird Services
Stars: ✭ 14 (-39.13%)
Mutual labels:  testing-tools
vsSolutionBuildEvent
🎛 Event-Catcher with variety of advanced Actions to service projects, libraries, build processes, runtime environment of the Visual Studio, MSBuild Tools, and …
Stars: ✭ 66 (+186.96%)
Mutual labels:  visual-studio
carina
Carina automation framework: Web, Mobile, API, DB etc testing...
Stars: ✭ 652 (+2734.78%)
Mutual labels:  testing-tools
TeeChart-for-.NET-CSharp-WPF-samples
Assorted WPF examples
Stars: ✭ 18 (-21.74%)
Mutual labels:  visual-studio
socketcluster-client-python
Python client for socket-cluster framework in node.js
Stars: ✭ 47 (+104.35%)
Mutual labels:  testing-tools
react-native-unit-tests
Example how to test React Native components
Stars: ✭ 79 (+243.48%)
Mutual labels:  testing-tools
EyeJS
A JavaScript testing framework for the real world
Stars: ✭ 68 (+195.65%)
Mutual labels:  testing-tools
dredd-rack
The Dredd API blueprint testing tool for your Rack applications.
Stars: ✭ 50 (+117.39%)
Mutual labels:  testing-tools
vscode-allautocomplete
Autocomplete from open files for VSCode
Stars: ✭ 90 (+291.3%)
Mutual labels:  visual-studio

Node.js CI npm version Dependency Status Commitizen friendly semantic-release

jest-trx-results-processor

This package is used to export a TRX file from Jest test runs to be used in Visual Studio and Visual Studio Team Services.

Migration from 0.x

Version 1.0.0 was rewritten to use reporters API. Either use that (see Usage), or update the require path in your configuration (see Usage as testResultsProcessor).

Installation

yarn add --dev jest-trx-results-processor

Usage

In your jest config add the following entry:

{
  "reporters": ["default", "jest-trx-results-processor"]
}

You can also pass additional arguments:

{
  "reporters": [
    "default",
    [
      "jest-trx-results-processor",
      {
        "outputFile": "relative/path/to/resulting.trx", // defaults to "test-results.trx"
        "defaultUserName": "user name to use if automatic detection fails" // defaults to "anonymous"
      }
    ]
  ]
}

Then run jest as usual.

Usage as testResultsProcessor

Notice: this method of use will be removed in the next major version. Please use the reporters API described above.

Create a jestTrxProcessor.js file somewhere in your project (for this example I'll assume the scripts folder). There you can configure the processor, as Jest does not allow you to pass custom parameters to the results processor:

// for jest-trx-results-processor >= 1.0.0
var builder = require("jest-trx-results-processor/dist/testResultsProcessor"); // only this has changed since v 0.x
// for jest-trx-results-processor < 1.0.0
var builder = require("jest-trx-results-processor");

var processor = builder({
  outputFile: "relative/path/to/resulting.trx", // this defaults to "test-results.trx"
  defaultUserName: "user name to use if automatic detection fails", // this defaults to "anonymous"
});

module.exports = processor;

Finally, point Jest to your results processor in the package.json:

{
  "devDependencies": {
    "jest": "^19.0.0",
    "jest-trx-results-processor": "~0.0.5"
  },
  "jest": {
    "testResultsProcessor": "./scripts/jestTrxProcessor"
  }
}

Then you just run Jest as you normally would.

Minimal working configuration can be seen in the examples folder.

Acknowledgements

This tool is heavily inspired by karma-trx-reporter and jest-junit.

License

jest-trx-results-processor is available under MIT. See LICENSE for more details.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].