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

Consider using mocks generator where feasible #6886

Open
2 of 3 tasks
czeslavo opened this issue Dec 20, 2024 · 0 comments
Open
2 of 3 tasks

Consider using mocks generator where feasible #6886

czeslavo opened this issue Dec 20, 2024 · 0 comments
Labels
area/maintenance Cleanup, refactoring, and other maintenance improvements that don't change functionality.

Comments

@czeslavo
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Does this enhancement require public documentation?

  • I have added an Acceptance Criteria item for adding and/or adjusting public documentation (if applicable)

Problem Statement

We use hand-written mocks in our tests. In most cases, they're simple enough so they could be auto-generated with tools like mockery. The goal of this issue is to convert hand-written mocks to mockery-generated ones where feasible.

Proposed Solution

No response

Additional information

No response

Acceptance Criteria

  • Simple mocks are replaced with mockery-generated ones
@czeslavo czeslavo added the area/maintenance Cleanup, refactoring, and other maintenance improvements that don't change functionality. label Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/maintenance Cleanup, refactoring, and other maintenance improvements that don't change functionality.
Projects
None yet
Development

No branches or pull requests

1 participant