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

Add sync status tests #443

Closed
wants to merge 3 commits into from
Closed

Conversation

runcom
Copy link
Member

@runcom runcom commented Feb 16, 2019

- What I did

This PR builds on #442 so let's hold until that merges.
The sync status is one of the most important thing we need NOT to regress on.
What the last commit really does is setting up a way to easily add more unit tests for the sync calls to avoid regression. I've modified the test in #442 to use the new way and added 2 other smoke tests. The aim is to add even more to cover the majority of the cases. (if not all)

For now, just review the last commit until #442 merges

- How to verify it

Run the unit tests

- Description for the changelog

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: runcom

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 16, 2019
@runcom
Copy link
Member Author

runcom commented Feb 16, 2019

holding caues waiting on #442

/hold

@openshift-ci-robot openshift-ci-robot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Feb 16, 2019
@runcom runcom force-pushed the add-sync-status-tests branch 2 times, most recently from f7e19f9 to 1c9501f Compare February 16, 2019 14:12
Fix a bug reported in openshift#406 (comment)
where we weren't properly resetting the failing status.

Signed-off-by: Antonio Murdaca <runcom@linux.com>
Specifically, add a test to verify that we're clearing out the failing
condition on subsequent sync operations (covering a bug reported here
openshift#406 (comment))

Signed-off-by: Antonio Murdaca <runcom@linux.com>
Signed-off-by: Antonio Murdaca <runcom@linux.com>
@runcom
Copy link
Member Author

runcom commented Feb 16, 2019

please take a look at ac3eb7f and identify other cases if you can as well

@runcom
Copy link
Member Author

runcom commented Feb 16, 2019

those units are too important actually, the code added is just in testing anyway. Adding this to #442

@runcom runcom closed this Feb 16, 2019
@runcom runcom deleted the add-sync-status-tests branch February 16, 2019 17:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants