Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/bbe78/cypress-sonarqube-reporter
A SonarQube XML reporter for Cypress
https://github.com/bbe78/cypress-sonarqube-reporter
cypress javascript reporting sonarqube
Last synced: about 1 month ago
JSON representation
A SonarQube XML reporter for Cypress
- Host: GitHub
- URL: https://github.com/bbe78/cypress-sonarqube-reporter
- Owner: BBE78
- License: mit
- Created: 2019-11-28T19:55:06.000Z (almost 5 years ago)
- Default Branch: master
- Last Pushed: 2024-09-27T08:42:56.000Z (about 2 months ago)
- Last Synced: 2024-10-12T22:20:56.950Z (about 1 month ago)
- Topics: cypress, javascript, reporting, sonarqube
- Language: JavaScript
- Homepage:
- Size: 2.41 MB
- Stars: 18
- Watchers: 1
- Forks: 11
- Open Issues: 19
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
README
A SonarQube XML reporter for Cypress.
Generated XML reports are compliant with Generic Execution described in https://docs.sonarqube.org/latest/analysis/generic-test/
## Why another one?
Since this Cypress issue: , spec filename are not available for reporters in a Cypress environnement.
\[**EDIT** 02-14-2020]: despite the correction of this issue since Cypress v3.8.3 (see [Release Notes](https://github.com/cypress-io/cypress/releases/tag/v3.8.3)), the problem is still there and the below reporters are still not working...
So this reporter provides a workaround (simplified as possible) in order to be able to generate these SonarQube reports.
A SonarQube test execution report is created for each Cypress spec file.
Other existing Mocha SonarQube reporters:
* [danmasta/mocha-sonar](https://github.com/danmasta/mocha-sonar)
* [mmouterde/mocha-sonarqube-reporter](https://github.com/mmouterde/mocha-sonarqube-reporter)
## Tested with Cypress
Take a look at the Actions tests matrix results: tested with Node.js v\[~~12.x~~, ~~14.x~~, 16.x, 18.x, 20.x] and Cypress v\[4.x, 5.x, 6.x, 7.x, 8.x, 9.x, 10.x, 11.x, 12.x, 13.x]
[](https://github.com/BBE78/cypress-sonarqube-reporter/actions/workflows/ci.yml)
### Compatibility with Cypress Component Testing
With the integration of the recent changes in #47, the reporter now supports Cypress component testing. Users can leverage the functionalities of `cypress-sonarqube-reporter` for both end-to-end tests and component tests conducted through Cypress.
## Example
The following Cypress/Mocha spec...
```js
describe("The root suite", () => {
it("Test case #1 (must pass)", () => {
expect(true).to.be.true;
});
describe("A sub suite", () => {
it("Test case #2 (must pass)", () => {
expect(true).to.be.true;
});
it("Test case #3 (must fail)", () => {
expect(true).to.be.false;
});
});
describe("Another sub suite", () => {
xit("Test case #4 (must be skipped)", () => {
expect(true).to.be.false;
});
it("Test case #5 (must raise an error)", () => {
undefined.toString();
});
});
});
```
...will provide the following generated SonarQube report (with default options)
```xml
(http://localhost:62294/__cypress/tests?p=test\cypress\integration\Sample.spec.js-285:37:17)]]>
```
## Sample
A sample project demonstrating the use of this reporter in a React App with Cypress and SonarQube is available in [example](./example/) folder
## From Mocha tests result to SonarQube Generic Execution report
The following table explains the association between test states and the generated XML part:
| Mocha test state | SonarQube Execution `testCase` child node |
| --------------------------------------------------- | ----------------------------------------- |
| `"passed"` | none |
| `"pending"` | `` short message is always "skipped message" |
| `"skipped"` | `` |
| `"failed"` and `test.err.name === "AssertionError"` | `` |
| `"failed"` and `test.err.name !== "AssertionError"` | `` |
## Installing
In Node.js environnement, use your favorite command:
`npm install --save-dev cypress-sonarqube-reporter`
`yarn add --dev cypress-sonarqube-reporter`
## Usage
### As a single Cypress reporter
As described in [Cypress documentation](https://docs.cypress.io/guides/tooling/reporters#Reporter-Options), single configuration:
With Cypress version >= v10.x
```javascript
// File: cypress.config.js
const { defineConfig } = require('cypress')
module.exports = defineConfig({
reporter: 'cypress-sonarqube-reporter',
reporterOptions: {
// see "Reporter Options" section
}
});
```
With Cypress version < v10.x
```json
// File: cypress.json
{
"reporter": "cypress-sonarqube-reporter",
"reporterOptions": {
// see "Reporter Options" section
}
}
```
### Using Cypress multiple reporters plugin
As described in [Cypress documentation](https://docs.cypress.io/guides/tooling/reporters#Multiple-reporters), multi configuration:
```json
// File: cypress.json
{
"reporter": "cypress-multi-reporters",
"reporterOptions": {
"reporterEnabled": "cypress-sonarqube-reporter, mochawesome",
"mochawesomeReporterOptions": {
// mochawesome options...
},
"cypressSonarqubeReporterReporterOptions": {
// see "Reporter Options" section
}
}
}
```
### Spec files update
EDIT: since v1.11.0, this code snippet is useless if you're using Cypress v6+.
~~The magic behind the scene is the use of `Cypress.spec` object (see [Cypress documentation](https://docs.cypress.io/api/cypress-api/spec.html#Syntax)) that is only available on spec files (ie not on reporter scope), so the drawback of this workaround is to use the function `specTitle(title: string)` from `specTitle.js` instead of the suite title:~~
```js
const specTitle = require('cypress-sonarqube-reporter/specTitle');
describe(specTitle('The root suite'), () => {
...
});
```
~~This `Cypress.spec` object is only available since Cypress v3.0.2 (see [Cypress changelog](https://docs.cypress.io/guides/references/changelog.html#3-0-2))~~
~~To avoid suite title pollution in other reporters (like the great [mochawesome](https://github.com/adamgruber/mochawesome#mochawesome)), make sure that `cypress-sonarqube-reporter` is the first one in the list.~~
### Merging reports into a single report
Since v1.10.0, you could merge all the generated reports into a single report. It could ease the configuration of your SonarQube analysis.
This feature is only available on Cypress version >= 6.2.0, since the `after:run` plugin event does not exist on previous versions (see [Cypress changelog](https://docs.cypress.io/guides/references/changelog#6-2-0)).
The merge operation has to be configured in Cypress plugins:
```javascript
// File: cypress/plugins/index.js
module.exports = (on, config) => {
// https://docs.cypress.io/api/plugins/after-run-api
on('after:run', (results) => {
// /!\ don't forget to return the Promise /!\
return require('cypress-sonarqube-reporter/mergeReports')(results);
});
};
```
or if you need to specify plugin's options:
```javascript
// File: cypress/plugins/index.js
module.exports = (on, config) => {
// https://docs.cypress.io/api/plugins/after-run-api
on('after:run', (results) => {
// /!\ don't forget to return the Promise /!\
return require('cypress-sonarqube-reporter/mergeReports')(results, {
// see "Merge Plugin Options" section for all available options
mergeFileName: 'another-name.xml'
});
});
};
```
## Reporter Options
| Name | Type | Default | Description |
| --------------------- | --------- | ------------------------------------- | ----------- |
| `outputDir` | `string` | `"./dist"` | folder name for the generated SonarQube XML reports, will be automatically created if not exist |
| `preserveSpecsDir` | `boolean` | `true` | specify if tests folders structure should be preserved |
| `overwrite` | `boolean` | `false` | specify if existing reporters could be overwritten; if `false` then an error is raised when reports already exist |
| `prefix` | `string` | `""` | file prefix for the generated SonarQube XML reports |
| `useFullTitle` | `boolean` | `true` | specify if test case should combine all parent suite(s) name(s) before the test title or only the test title |
| `titleSeparator` | `string` | `" - "` | the separator used between combined parent suite(s) name(s); only used if `useFullTitle` is `true` |
| `useAbsoluteSpecPath` | `boolean` | `false` | specify if the absolute path of a spec file should be written to the report |
| `mergeOutputDir` | `string` | `` | folder name for the merged SonarQube XML report, will be automatically created if not exist. If not specified, `outputDir` is used |
| `mergeFileName` | `string` | `"cypress-sonarqube-reports.all.xml"` | merged SonarQube XML report name |
## Merge Plugin Options
| Name | Type | Default | Description |
| --------------------- | --------- | ------------------------------------- | ----------- |
| `reportsOutputDir` | `string` | `"./dist"` | folder name for the generated SonarQube XML reports. If not specified, reporter options are used |
| `mergeOutputDir` | `string` | `` | folder name for the merged SonarQube XML report, will be automatically created if not exist. If not specified, `reportsOutputDir` is used |
| `mergeFileName` | `string` | `"cypress-sonarqube-reports.all.xml"` | merged SonarQube XML report name |
## Issues & Enhancements
For any bugs, enhancements, or just questions feel free to use the [GitHub Issues](https://github.com/BBE78/cypress-sonarqube-reporter/issues)
## Licence
[](https://github.com/cypress-io/cypress/blob/master/LICENSE)
This project is licensed under the terms of the [MIT license](/LICENSE).
[](https://app.fossa.com/projects/git%2Bgithub.com%2FBBE78%2Fcypress-sonarqube-reporter?ref=badge_large)