-
Notifications
You must be signed in to change notification settings - Fork 28
Llt 6812 move libfirewall dependent tests to gitlab #1620
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
base: main
Are you sure you want to change the base?
Llt 6812 move libfirewall dependent tests to gitlab #1620
Conversation
b89f0ba to
4347ad3
Compare
752768d to
9178835
Compare
9178835 to
c9dbfbd
Compare
c9dbfbd to
230adb4
Compare
230adb4 to
5f5d9e9
Compare
jjanowsk
left a comment
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.
How about moving firewall tests to the separate test target. You can do it by adding:
name = "firewall_tests"
path = "tests/integration_tests.rs"
test = false
to the Cargo.toml. This way you can run only those tests separately by running cargo test --test firewall_tests
This way if we want to have other integration tests still run here we can. (E.g. dns integration tests were the victim of current approach)
I have not tested this on telio-firewall so maybe there are some caveats but in theory it should work.
|
@jjanowsk Hmm, I considered that, but in the end it seemed that making the split that unit tests run on github while crate/integration test run on gitlab it kinda cleaner than making and exception for libfirewall - but if you think that would be much better, I can limit it to firewall tests only |
|
Personally I prefer separate target just for firewall tests. You can ask someone else for the 3rd opinion :) |
|
I also like the idea of a separate target. It will be slightly more complex, but I think it makes sense that since this is an open source repo we should keep as much open as we can |
5f5d9e9 to
876cad9
Compare
5b3c96c to
876cad9
Compare
|
@jjanowsk @mathiaspeters reduced the scope of the tests run on gitlab to firewall ones |
876cad9 to
260ccfa
Compare
260ccfa to
5fc3dc5
Compare
|
+1 The PR looks fine to me but if I understand correctly, the current approach requires libtelio-build to be aware of A more generic solution could be to use a feature so we could gatekeep multiple tests(if needed) to run only in CI with a single feature. Though, given that this is currently only for libfirewall tests there probably is not much difference at the moment. |
Problem
telio-firewall tests which depend on libfirewall.so should be moved to gitlab
Solution
Make them integration tests and then run all of the integration tests on gitlab
☑️ Definition of Done checklist