-
Notifications
You must be signed in to change notification settings - Fork 17
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
Missing Control API Unit Tests #473
Conversation
Signed-off-by: Jordan Rash <jordan@synadia.com>
Signed-off-by: Jordan Rash <jordan@synadia.com>
Signed-off-by: Jordan Rash <jordan@synadia.com>
Signed-off-by: Jordan Rash <jordan@synadia.com>
Signed-off-by: Jordan Rash <jordan@synadia.com>
Signed-off-by: Jordan Rash <jordan@synadia.com>
Signed-off-by: Jordan Rash <jordan@synadia.com>
Signed-off-by: Jordan Rash <jordan@synadia.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The bulk of the review are comments on a handful of practices to improve the testing structure which will help simplify the tests and remove some redundancy.
Signed-off-by: Jordan Rash <jordan@synadia.com>
Signed-off-by: Jordan Rash <jordan@synadia.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. My only other comment would be whether it would make sense to consolidate some of the tests as subtests to remove the need to spin up all the boilerplate each time for the simpler interactions. For example, Ping
and DirectPing
are not state changing, so those could combined as subtests. As another example, the only difference between the AuctionDeployAnd*
tests is finding the workload vs. listing, but all the other boilerplate is the same. The CopyWorkload
test could also be a subtest.
Now that there is an assertion lib in there, I agree with this. I thought before subtest made it too difficult to read....let me see if I can clean it up EDIT: I think what I am going to do is merge this and move to the subtest approach in the next few weeks |
Merging this branch will increase overall coverage
Coverage by fileChanged files (no unit tests)
Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code. Changed unit test files
|
No description provided.