forked from eclipse-edc/Connector
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Automated Tests for Sample 04.3 #198
Comments
Decision required whether we have tests for samples in the first place. Issue currently is that samples break all the time. |
Backlog refinement: Samples 4.0 to 4.3 should have automated tests to prevent that these samples get broken. |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature #194
upstream: eclipse-edc#1045
After #252
Description
Automated integration tests that run in CI should be added for samples to prevent the samples breaking due to changes in the EDC.
The scope of this story is to add automated integration tests for sample 04.3.
Sample 04.3 is based on a docker-compose + commands specified in the readme.
Having tests running the docker-compose + the commands to make sure that the sample is not broken would help avoiding breaking it.
The existing client-side integration test can be used:
FileTransferAsClientIntegrationTest
Note: it was decided that EDC integration tests should not rely on samples. However, it is desirable to have additional tests to make sure that the samples don't get broken.
Acceptance criteria
Tasks
The text was updated successfully, but these errors were encountered: