-
Notifications
You must be signed in to change notification settings - Fork 22
Integration tests with devenv as backend. #215
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #215 +/- ##
==========================================
- Coverage 43.44% 43.01% -0.43%
==========================================
Files 45 45
Lines 5467 5521 +54
Branches 47 47
==========================================
Hits 2375 2375
- Misses 3091 3145 +54
Partials 1 1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
cbc51aa
to
abddb42
Compare
@friedger Almost there. I just added clarinet deployments. I may add a deposit or withdrawal test tomorrow based on the script you shared a few days ago. |
abddb42
to
9f178af
Compare
a0d3aa0
to
9c56930
Compare
Where would I see the result of the test? |
When you run the tests. You will see the container id such as:
You can use the container id with I recommend another terminal watching specific services or the testing container itself while you wait for it to finish.
If the tests fails the script will print the logs for you, which is the case so far ^^. |
9c56930
to
b65d28f
Compare
b0ccfef
to
079fd12
Compare
e651c91
to
aed33a2
Compare
5bf3c15
to
e07fd1c
Compare
Summary of Changes
Testing
Replicate behavior in
deposit.sh
Risks
Low risk, break devenv due to changes in configuration.
How were these changes tested?
Manual testing of the integration pipeline.
Follow the Readme to replicate.
What future testing should occur?
The tests I included are not complete. I don't assert on pre and post-conditions. In another PR we need to enable integration CI and finish the tests.
Checklist: