-
Notifications
You must be signed in to change notification settings - Fork 722
Improve cli client tests #691
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
Conversation
To allow testing that client calls trigger expected RPC requests. Using a strict mock, to fail on unexpected calls. This currently makes client tests fail.
Use "fails" to follow convention used by the other tests and easily identify test type.
Covers list, start, stop, restart, and suspend calls.
Seems legit. bors r+ |
691: Improve cli client tests r=Saviq a=ricab This prepares the ground for the testing the pet-env feature in the CLI client. It improves CLI client tests, by checking - the expected RPC calls are triggered - no unexpected RPC calls are triggered A future step is to check that the request parameters correspond to expectations. Co-authored-by: Ricardo Abreu <ricab@ricabhome.org>
Build failed |
Sorry, didn't realize this was going into |
No worries, just changed base to master since the other one was merged anyway. |
Codecov Report
@@ Coverage Diff @@
## master #691 +/- ##
=======================================
Coverage 66.59% 66.59%
=======================================
Files 168 168
Lines 5943 5943
=======================================
Hits 3958 3958
Misses 1985 1985 Continue to review full report at Codecov.
|
bors r+ This conflicts on Mac, will take car of that in a moment. |
691: Improve cli client tests r=Saviq a=ricab This prepares the ground for the testing the pet-env feature in the CLI client. It improves CLI client tests, by checking - the expected RPC calls are triggered - no unexpected RPC calls are triggered A future step is to check that the request parameters correspond to expectations. Co-authored-by: Ricardo Abreu <ricab@ricabhome.org>
Thanks @Saviq. Is there a way to see the conflict in travis? Or have to try locally? |
@ricab not at the moment, it's a trivial one though. |
Build failed |
Fix symlink resolution when mounting
This prepares the ground for the testing the pet-env feature in the CLI client. It improves CLI client tests, by checking
A future step is to check that the request parameters correspond to expectations.