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

[Chore]: Get rid of integration tests for the /v3/builds endpoints #933

Closed
gcapizzi opened this issue Apr 8, 2022 · 2 comments · Fixed by #1964
Closed

[Chore]: Get rid of integration tests for the /v3/builds endpoints #933

gcapizzi opened this issue Apr 8, 2022 · 2 comments · Fixed by #1964
Labels
chore good first issue Good for newcomers

Comments

@gcapizzi
Copy link
Contributor

gcapizzi commented Apr 8, 2022

Background

In order to simplify our testing strategy, we want to get rid of envtest-based integration tests for our handlers.

Action to take

Impact

  • Make our unit tests comprehensive
  • Reduce overlap in our tests and thus cost of maintenance
@gcapizzi gcapizzi added the chore label Apr 8, 2022
@gcapizzi gcapizzi changed the title [Chore]: [Chore]: Get rid of integration tests for the /v3/builds endpoints [Chore]: Get rid of integration tests for the /v3/builds endpoints Apr 8, 2022
@gcapizzi gcapizzi added the good first issue Good for newcomers label Apr 8, 2022
@benjaminguttmann-avtq
Copy link
Contributor

@gcapizzi I would be interested in supporting here but have struggle how to takle it. Do we maybe have an example of similar task I can have a look into ?

@gcapizzi
Copy link
Contributor Author

gcapizzi commented Oct 27, 2022

@benjaminguttmann-avtq hello, sorry for the late reply!

The idea of these tasks is to remove a set of redundant tests. We believe our handlers should only be tested with unit tests (which use mocks for dependencies) and don't need to also be tested in integration (with real dependencies) using envtest. Before doing that though, we want to make sure that we don't lose any coverage by doing this.

So we want to:

  • check that our unit tests cover everything the integration tests do;
  • backfill the missing unit tests if needed;
  • remove the integration tests.

I can't find a PR doing something similar but every PR will look different, as every set of handler might have a different level of coverage in the two test suites.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore good first issue Good for newcomers
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants