Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitHubAction: tests have unnecessary output #3735

Closed
de-jcup opened this issue Dec 13, 2024 · 0 comments · Fixed by #3734
Closed

GitHubAction: tests have unnecessary output #3735

de-jcup opened this issue Dec 13, 2024 · 0 comments · Fixed by #3734
Assignees

Comments

@de-jcup
Copy link
Member

de-jcup commented Dec 13, 2024

Situation

Following tests provide unnecessary output:

  • configuration-builder.test
  • shell-arg-sanitizer.test
  • client-version-helper.test
  • init-scan.test

The verbose output (for green tests) becomes problematic on CI/CD when it comes to failure tracing.

Wanted

A npm run test shall have at least output as possible.
The results progress shall be the only output.

Solution

The output shall only appear when a debug flag is enabled inside the relevant test.
To do this, we mock core.error, core.info or core.debug (depending what is used) and
introduce a debug flag inside the tests. When debug is enabled, the mock shall do an output.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant