chevron-thin-right chevron-thin-left brand cancel-circle search youtube-icon google-plus-icon linkedin-icon facebook-icon twitter-icon toolbox download check linkedin phone twitter-old google-plus facebook profile-male chat calendar profile-male
+1 vote
I run some test with Boost 1.72 and last version of isolator++.

The exit code returned to caller (cmd in my case) is alway 0 even if there is a failure.

When I remove all calls to isolator++, the return to code is well handled and can be an error value (like 201 as return Boost when there is a failure).

Do I need to do something to fix this ? There is a workaround ?

Thanks.
asked by lcarrera (1.1k points)

2 Answers

0 votes

Hi,

Our integration with Boost testing framework should work fine.

Can you please run a single test that fails with this errors, with logs enabled and send us the logs?

Enable the logs in Configuration utility in Isolator++ installation folder.

Cheers,

Alon Sapozhnikov

Support Specialist

answered by Alon_TypeMock (6.6k points)
Hi,

Ok you will find the result of log at :

https://fileshare.5asolutions.com/f.php?h=10r2-Zga&d=1

Thank you.

Best regards.
0 votes

Hi,

I just reproduced the same situation. I've been able to create a VS2017 project with native C++ that reproduce the problem.

I tried to add an image, but the upload process to the server transform the image so that it becomes unreadable. I keep it if necessary.
The project is based only on a main.cpp file (so that one can reproduce the problem even without my test project):

#include "isolator/isolator.h"

#include <iostream>

int demoFunction()
{
   return 0;
}

int main()
{
    std::cout << "Hello World! ";

    FAKE_GLOBAL(demoFunction);
    WHEN_CALLED(demoFunction()).Return(1);

    int returnCode;
    returnCode = demoFunction();

    std::cout << "return Code = " << returnCode;

    return returnCode;
}

Linked with the 4.1.3.0 version, compiled in x64 Debug, the returnCode variable values 1, but the executable exits with code 0.

This problem is annoying as I faced some tests crashing the test executable, but with the exit code 0, I only discovered the problem by reading the logs.

Let me know if you want me to send the project as well, or if there is a more dedicated process to report reproducible bugs.

Armand

answered by abolmont (650 points)
...