Skip to content

Throwing test: wrong crash detection #110 #358

Description

@edenroz

I have a test that handles a throwed excecption but the exception seems not handled, maybe it's because Isolator++.

The adapter wrongly detect my PASSED tests as FAILED and prints the message "!! This test has probably CRASHED !!"

Raw output of google test follows

[==========] Running 3 tests from 2 test cases.
[----------] Global test environment set-up.
[----------] 2 tests from TestLPR_COMMOD_IM_IntegrityTilesModelOffset
[ RUN ] TestLPR_COMMOD_IM_IntegrityTilesModelOffset.When_Clean_Expect_CallTo_LxR_xxxMOD_IM_SecFeatSimulationModel_clean
[ OK ] TestLPR_COMMOD_IM_IntegrityTilesModelOffset.When_Clean_Expect_CallTo_LxR_xxxMOD_IM_SecFeatSimulationModel_clean (363 ms)
[ RUN ] TestLPR_COMMOD_IM_IntegrityTilesModelOffset.When_Clean_Expect_CallTo_LPR_COMMOD_IM_IntegrityTilesModel_Clean
[ OK ] TestLPR_COMMOD_IM_IntegrityTilesModelOffset.When_Clean_Expect_CallTo_LPR_COMMOD_IM_IntegrityTilesModel_Clean (44 ms)
[----------] 2 tests from TestLPR_COMMOD_IM_IntegrityTilesModelOffset (413 ms total)

[----------] 1 test from TestMbuLKIntaglioRefl
[ RUN ] TestMbuLKIntaglioRefl.When_Ctor_Expect_CallTo_AddModel

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions