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.

Sign up for GitHub

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

Jump to bottom

Integration tests #5

Open
marcomicera opened this issue Jan 13, 2021 · 2 comments · May be fixed by #10
Open

Integration tests #5

marcomicera opened this issue Jan 13, 2021 · 2 comments · May be fixed by #10
Assignees
@marcomicera

Comments

@marcomicera
Copy link
Member

marcomicera commented Jan 13, 2021 •
edited
Loading

The builder should be at least able to communicate with the master/orchestrator.

Python and CMake builders do this with the qmstr run ... wrapper.
Maven builders do this by patching the root pom.xml file, injecting the Quartermaster Maven plugin.

A docker-compose.yml file can help to instantiate such an integration test, even though it'd be a manual one.
@marcomicera marcomicera self-assigned this Jan 13, 2021
@marcomicera
Copy link
Member Author

Modules must be able to communicate with:

@marcomicera
Copy link
Member Author

💡 Idea: include the test in the CI (the last step should execute the test script and expect 0 as the return code).

@marcomicera marcomicera linked a pull request Jan 15, 2021 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@marcomicera marcomicera

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Added integration test endocode/module
1 participant
@marcomicera