Skip to content

Unit testing support #320

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

Closed
killwing opened this issue Jun 19, 2018 · 2 comments
Closed

Unit testing support #320

killwing opened this issue Jun 19, 2018 · 2 comments

Comments

@killwing
Copy link

killwing commented Jun 19, 2018

Because the operator-sdk wraps controller functions in a high level, it's hard to inject test data (e.g.: add test data to the index cache directly) or add some mocks for unit testing.
Any idea? Or any plan to make the operator-sdk more UT friendly?

related: #284

@killwing killwing changed the title unit testing support Unit testing support Jun 19, 2018
@hasbro17
Copy link
Contributor

@killwing We're currently working on removing the global state and designing the right objects and interfaces that should make it easier to write unit tests and inject test data to the handler and controller #169
However that's a major redesign which will take some time.

@killwing
Copy link
Author

Glad to hear that it's in progress.

m1kola pushed a commit to m1kola/operator-sdk that referenced this issue Jun 7, 2024
…istency-openshift-4.14-openshift-enterprise-ansible-operator

Updating openshift-enterprise-ansible-operator images to be consistent with ART
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

No branches or pull requests

2 participants