Home/ Questions/Q 6467853
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T05:50:07+00:00

Please note that this is NOT a duplicate of How write a unit test

  • 0

Please note that this is NOT a duplicate of How write a unit test for verifying compiling error? as I’m not concerned about testing the correctness of external libraries or the compiler itself.

It is typical in C++, particularly when dealing with templates, to employ techniques that prevent some particular piece of code from being compiled. As these can get convoluted, what is the best way to ensure that particular pieces of code do indeed generate compiler errors?

As the test shouldn’t even get compiled, you can’t rely on things such as , so I guess it should be integrated in the build system? How are these issues usually approached?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Do it in the similar way compiler tests are written. You will have a bit of testing code in some scripting language (shell, perl, tcl etc.) that will run compiler on given snippets of code and check whether the right ones compiled and the right ones did not.

    • gcc uses DejaGnu, which is built on top of expect, which is itself built on top of Tcl.
    • If you use shell script (probably easier, DejaGnu is probably overkill), you might want to look at shUnit2.
    • Perl’s Test::Harness system should be mostly easy to use as is.
    • After all, it’s not that much more work to run process from C++, so writing a function to try to call compiler on a given string and check whether it outputs error for line where you expect it would not be that hard and than you can integrate it into the other boost.test-based tests.
    • 0