Handle empty suites #56

Sett17 · 2023-11-10T13:15:25Z

regards #55

…n testing

Provide a console warning utility for better logging granularity.

…ort generation Skip the generation of SonarQube XML reports when the test suite contains zero tests, adhering to compliance standards that require test results to be present in the reports. This ensures no empty reports are created, which would not comply with the expected report structure.

BBE78

Thanks @Sett17 for these changes, some small comments...

test/specs/Reporter.spec.js

src/ReporterUtils.js

src/SonarQubeCypressReporter.js

test/cypress/component/MyEmptyComponent.spec.js

test/cypress/integration/Empty.spec.js

test/cypress/component/MyEmptyComponent.spec.js

test/cypress/integration/Empty.spec.js

Refactoring to eliminate the redundant `totalTestCount` property in favor of checking the length of the `runner.suite.tests` array directly. This simplifies the logic for determining if the test suite is empty, making the codebase cleaner and easier to maintain.

Updated the console method in ReporterUtils to use `console.warn` for warning messages, ensuring the correct log level is used. Test suite descriptions were also standardized for consistency across test files, enhancing readability and maintainability of the test codebase.