Repository navigation
fix: test assertion macros reporting false passes - #87
Conversation
I made a few changes to address issue tecnolgd#83. For the first part, I fixed the `ASSERT_THROW` macro by adding a check to ensure that the expected exception is actually thrown. For the second part, I modified the `EXPECT_*` macros so that the test continues running even when an expectation fails. I also added a counter to track the number of failed expectations and made sure that these failures are reflected in the final test results. I haven't been able to run the tests locally yet, so these changes have not been verified locally. Feedback and testing are welcome!
|
If there's any issues do not hesitate to tell me ! |
|
Hey @vovosta, thanks for the fix! Before we get this merged, could you please update your pull request title to something more descriptive (for example: Fix test assertion macros reporting false passes)? It helps keep our commit history clean. Check the relevant boxes in the checklist as per the changes. |
|
Hey, i'll change the name right now. Sorry to bother you, |
No worries at all! I totally understand. The CI is completely green, but I just need some time to perform local tests to double-check everything before merging. |
|
Hey, i think i found a way to compile it locally. |
|
After all, i'll let you do it because i'm having some issues rn, sorry. |
|
I verified the changes locally. Everything LGTM. Thanks again! |
|
Thanks so much ! I'm so happy to contribute to the project ! |
I made a few changes to address issue #83.
I haven't been able to run the tests locally yet, so these changes have not been verified locally. Feedback and testing are welcome!
What's Changed
ASSERT_THROWmacro by adding a check to ensure that the expected exception is actually thrown.EXPECT_*macros so that the test continues running even when an expectation fails. Added a counter to track failed expectations and ensured that these failures are reflected in the final test results.Related Issue
Checklist