element-call-Github/codecov.yaml

# Don't post comments on PRs; they're noisy and the same information can be
# gotten through the checks section at the bottom of the PR anyways
comment: false
github_checks:
  # Don't mark up the diffs on PRs with warnings about untested lines; we're not
  # aiming for 100% test coverage and they just get in the way of reviewing
  annotations: false
coverage:
  status:
    project:
      default:
        # Track the impact of changes on overall coverage without blocking PRs
        informational: true
    patch:
      default:
        # Encourage (but don't enforce) 80% coverage on all lines that a PR
        # touches
        target: 80%
        informational: true
Clean up our tests in preparation for the testing sprint (#2466) * Fix coverage reporting Codecov hasn't been working recently because Vitest doesn't report coverage by default. * Suppress some noisy log lines Closes https://github.com/element-hq/element-call/issues/686 * Store test files alongside source files This way we benefit from not having to maintain the same directory structure twice, and our linters etc. will actually lint test files by default. * Stop using Vitest globals Vitest provides globals primarily to make the transition from Jest more smooth. But importing its functions explicitly is considered a better pattern, and we have so few tests right now that it's trivial to migrate them all. * Remove Storybook directory We no longer use Storybook. * Configure Codecov Add a coverage gate for all new changes and disable its comments. * upgrade vitest --------- Co-authored-by: Timo <toger5@hotmail.de> 2024-08-27 21:45:39 +08:00			`# Don't post comments on PRs; they're noisy and the same information can be`
			`# gotten through the checks section at the bottom of the PR anyways`
			`comment: false`
Disable Codecov annotations Don't mark up the diffs on PRs with warnings about untested lines; we're not aiming for 100% test coverage and they just get in the way of reviewing. 2024-10-19 04:39:02 +08:00			`github_checks:`
			`# Don't mark up the diffs on PRs with warnings about untested lines; we're not`
			`# aiming for 100% test coverage and they just get in the way of reviewing`
			`annotations: false`
Clean up our tests in preparation for the testing sprint (#2466) * Fix coverage reporting Codecov hasn't been working recently because Vitest doesn't report coverage by default. * Suppress some noisy log lines Closes https://github.com/element-hq/element-call/issues/686 * Store test files alongside source files This way we benefit from not having to maintain the same directory structure twice, and our linters etc. will actually lint test files by default. * Stop using Vitest globals Vitest provides globals primarily to make the transition from Jest more smooth. But importing its functions explicitly is considered a better pattern, and we have so few tests right now that it's trivial to migrate them all. * Remove Storybook directory We no longer use Storybook. * Configure Codecov Add a coverage gate for all new changes and disable its comments. * upgrade vitest --------- Co-authored-by: Timo <toger5@hotmail.de> 2024-08-27 21:45:39 +08:00			`coverage:`
			`status:`
			`project:`
			`default:`
			`# Track the impact of changes on overall coverage without blocking PRs`
			`informational: true`
			`patch:`
			`default:`
Make the test coverage target non-blocking Sadly Codecov doesn't give us a way to relax the coverage requirements for changes that touch very few lines of code, which has been an invaluable feature of SonarCloud. I suggest we make the check non-blocking. 2024-09-04 04:03:43 +08:00			`# Encourage (but don't enforce) 80% coverage on all lines that a PR`
			`# touches`
Clean up our tests in preparation for the testing sprint (#2466) * Fix coverage reporting Codecov hasn't been working recently because Vitest doesn't report coverage by default. * Suppress some noisy log lines Closes https://github.com/element-hq/element-call/issues/686 * Store test files alongside source files This way we benefit from not having to maintain the same directory structure twice, and our linters etc. will actually lint test files by default. * Stop using Vitest globals Vitest provides globals primarily to make the transition from Jest more smooth. But importing its functions explicitly is considered a better pattern, and we have so few tests right now that it's trivial to migrate them all. * Remove Storybook directory We no longer use Storybook. * Configure Codecov Add a coverage gate for all new changes and disable its comments. * upgrade vitest --------- Co-authored-by: Timo <toger5@hotmail.de> 2024-08-27 21:45:39 +08:00			`target: 80%`
Make the test coverage target non-blocking Sadly Codecov doesn't give us a way to relax the coverage requirements for changes that touch very few lines of code, which has been an invaluable feature of SonarCloud. I suggest we make the check non-blocking. 2024-09-04 04:03:43 +08:00			`informational: true`