Home/ Questions/Q 3958704
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T02:38:27+00:00

I am developing a DLL in C++ and want to perform unit testing of

  • 0

I am developing a DLL in C++ and want to perform unit testing of that DLL using the Boost Test Libraries. I read the Boost test manual thoroughly but since I am new, I have the following question:

Should I add test classes in the same VC project in which I am developing my DLL?. Ideally I want to do this but I am confused that a DLL has no main() and, on the other hand, the Boost test needs its own main() to execute. So where does the Boost test output go in this scenario? (In fact, I practically implemented this and don’t see any output 🙁 and almost spent two days I figuring out the problem, but didn’t succeed)

Regards,

Jame.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You have 3 ways to do this:

    1. You can definitely do what another reply suggest and build your lib as static. I wouldn’t recommend this way though.

    2. You can have one or more separate unit test projects in your solution. These projects will link with your library and with either static or shared version of Boost Test library. Each project will have a main either supplied by the Boost.Test library or implemented by you manually.

    3. Finally you have another option and you can put your test cases directly into your library. You’ll need to link with shared version of Boost Test. Once your library is built you can use it regularly as you do now plus you’ll have an ability to execute test cases built into it. To execute the test case you’ll need a test runner. Boost Test supplies one called “console test runner”. You’ll need to build it once and you can use for all your projects. Using this test runner you can execute your unit test like this:

      test_runner.exe –test “your_lib”.dll

      You should understand all the pluses and minuses of this approach. Your unit test code will be part of your production library. It’ll make it slightly bigger, but on the other hand you’ll be able to run the test in production if necessary.

    • 0