Make integration tests have debug asserts
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
Research direction
Start with tests/utils/bazel/unit_test.bzl at the linked line, then find the Bazel definition used by integration tests and compare how unit tests enable debug asserts. Update the integration test setup to enable them and provide an assertion handler that prints the message. Done when integration tests run with debug asserts and every integration test has that handler.
Written by the indexing model from the issue text.
Description
What
Our code has a bunch of DBG asserts that would be useful to also check on the integration test level.
Add the define to allow debug asserts to run in integration tests, similar to the unit tests.
https://github.com/eclipse-score/lifecycle/blob/0bfc812bc1fe0e282d9d65c7e26fe8369b1be100/tests/utils/bazel/unit_test.bzl#L38
Acceptance Criteria (DoD)
Integration tests run with debug asserts, and all have an assertion handler that prints the message.
How
No response
- Dominant language
- C++
- Stars
- 7
- Forks
- 37
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 117
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from eclipse-score/lifecycle
-
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
eclipse-score/lifecycle#880 ·
Maintainers usually reply within 1 day
-
Move all "Default" asserts to debugPossibly taken @hskang-amelia claimed this 10 days ago. Opencleanup good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
eclipse-score/lifecycle#842 ·
Maintainers usually reply within 1 day
-
cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
eclipse-score/lifecycle#375 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
eclipse-score/lifecycle#952 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
eclipse-score/lifecycle#951 ·
Maintainers usually reply within 1 day
All issues in eclipse-score/lifecycle
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NVIDIA-RTX/NRI#312 ·
Maintainers usually reply within 1 day
-
permute_q_b_proj / permute_wv_proj accept scale factors from another devicePossibly taken @0z5a claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
deepseek-ai/FlashMLA#247 ·
Maintainers usually reply within 1 day
-
Linux npm packaging leaves workspace files that block subsequent CI checkoutPossibly taken @Spockkk0225 claimed this today. Openci
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
alibaba/neug#1195 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 3 days