npmpackage.info

Gathering detailed insights and metrics for karma-dedup-junit-reporter

Other packages similar to karma-dedup-junit-reporter

karma-junit-reporter

2.0.1

A Karma plugin. Report results in junit xml format.

junit-report-merger

7.0.0

Merges multiple JUnit XML reports into one.

jest-junit

16.0.0

A jest reporter that generates junit xml files

mocha-junit-reporter

2.2.1

A JUnit reporter for mocha.

Gathering detailed insights and metrics for karma-dedup-junit-reporter

karma-dedup-junit-reporter

Wrapper around the karma junit reporter that adds a number to each spec.

1.0.1

MIT

JavaScript

30,143 3

Installations

npm install karma-dedup-junit-reporter

Pull Requests

Open

0

Total

0

Closed

0

Issues

Open

0

Total

0

Closed

0

Releases

Unable to fetch releases

Developer

bodyloss

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

Typescript Support

No

Node Version

4.1.1

NPM Version

2.14.4 Statistics

4 Commits

2 Watching

1 Branches

1 Contributors

Updated on 10 Aug 2016

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

30,143

Last day

-46.2%

Compared to previous day

Last week

-22.7%

109

Compared to previous week

Last month

-0.2%

533

Compared to previous month

Last year

-26.3%

7,382

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

karma karma-junit-reporter

Versions

Karma No Duplicates JUnit Reporter

This is a really simple package that wraps up the karma-junit-reporter and adds a number to the end of duplicate spec names.

The reason this exists is some CI platforms (i.e. Bamboo) report the number of tests incorrectly if there are duplicate tests.

Usage

Use it exactly the same as karma-junit-reporter:

1reporters: ['counting-junit'],
2plugins: [
3  require('karma-dedup-junit-reporter')
4]

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

10

License

Determines if the project has defined a license.

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

SAST

Determines if the project uses static code analysis.

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

Score

3

/10

Last Scanned on 2024-11-25

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More