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

Unit cases into integration suite #352

Closed
makslion opened this issue Jul 19, 2023 · 8 comments
Closed

Unit cases into integration suite #352

makslion opened this issue Jul 19, 2023 · 8 comments
Labels

Comments

@makslion
Copy link
Contributor

What

Currently, we have a number of unit tests that are focused on the .Reconcile() function. It was decided to delegate testing of the controllers mainly to the integration test suite hence some of the existing unit tests should be transitioned from the unit suite into integration.

How

Go through the unit suite and transition all relevant cases.

The catch

Not all tests could be transitioned.
The goal is to have controllers mainly tested by the integration suite, but some of the logic in the .Reconclile() ensures that we aren't crashing in case something goes wrong and integration isn't equipped well to deal with it. So should we still have a bunch of exception cases form the unit suite poking reconcilers or just get rid of them leaving certain parts of the code uncovered?

@makslion
Copy link
Contributor Author

derived from the #282

@philbrookes
Copy link
Contributor

This issue is stale because it has been open for 30 days with no activity.

@philbrookes
Copy link
Contributor

This issue was closed because it has been inactive for 30 days since being marked as stale.

@makslion
Copy link
Contributor Author

still valid issue

@makslion makslion reopened this Sep 26, 2023
@philbrookes philbrookes removed the stale label Sep 27, 2023
@philbrookes
Copy link
Contributor

This issue is stale because it has been open for 60 days with no activity.

@philbrookes
Copy link
Contributor

This issue was closed because it has been inactive for 30 days since being marked as stale.

@makslion makslion reopened this Mar 8, 2024
@philbrookes philbrookes removed the stale label Mar 9, 2024
@philbrookes
Copy link
Contributor

This issue is stale because it has been open for 60 days with no activity.

@philbrookes
Copy link
Contributor

This issue was closed because it has been inactive for 30 days since being marked as stale.

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

No branches or pull requests

2 participants