doc/user/unit-testing.md: explain fake client and unit test example #757
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
estroz
added
area/testing
openshift-ci-robot
added
the
size/L
estroz
force-pushed
the
fake-client
branch
2 times, most recently
from
d4c5a6e to
0459cad
Compare
Member
Author
|
The unit test here is less thorough than that in |
hasbro17
reviewed
Nov 27, 2018
hasbro17
reviewed
Nov 27, 2018
hasbro17
reviewed
Nov 27, 2018
hasbro17
reviewed
Nov 27, 2018
hasbro17
reviewed
Nov 27, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the change: doc on using
controller-runtime's fake client library to mock API calls in unit tests.Motivation for the change: users should be writing unit tests for custom operator code. The fake client is useful for doing so.