CLion 2017.3 EAP: Boost.Test support

Anastasia Kazakova


Welcome our new CLion 2017.3 EAP, build 173.2696.23!

In late 2016 and early 2017 we polled over 5,000 developers to identify the State of Developer Ecosystem. This covered C and C++ development and showed many interesting results.

Among other questions we’ve asked about unit testing framework used by the respondents on a regular basis. For C language the top three unit test frameworks are: Google Test (37%), Boost.Test (8%), CppUnit (8%). For C++ – Google Test (45%), Boost.Test (26%), CppUnit (11%).


CLion already supports Google Test and Catch unit test frameworks. And now it comes with the Boost.Test support! The support includes:

  • Special Boost.Test Run/Debug configurations
  • Built-in test runner with the progress bar and a tree view of all the tests running
  • Ability to re-run failed tests, export test results, open previously saved results
  • Ability to navigate to the source code of a particular test
  • Gutter icons to Run/Debug unit tests and show the status of the tests


Besides, we’ve eliminated false warning for MSVC specific pragmas (CPP-9549).

Full release notes are available by the link.

Download CLion 2017.3 EAP

Your CLion Team
The Drive to Develop

Comments below can no longer be edited.

22 Responses to CLion 2017.3 EAP: Boost.Test support

  1. Roman says:

    September 27, 2017

    Any plans to support CTest soon? Or any other way to specify build / run configurations in a text file?

  2. marco says:

    September 27, 2017

    thanks! Now please consider CppUTest, which is the only one that can be used to mock also C functions or C++ free-standing functions. See for details.

    • Anastasia Kazakova says:

      September 28, 2017

      I guess we’ll be able to provide a public API for unit testing frameworks sometime in future soon. And community will be able to add any framework to CLion with ease.

      • Pwera says:

        September 28, 2017


  3. Roman says:

    September 29, 2017

    Well, I’ve experimented with using Google Test in Clion. Surprisingly it is not usable today:
    1) Tests output is messed-up. Most likely because of
    2) Test results window shows some random icons: (for example some passing tests shown as failed)
    3) Console output is gray instead of colored (I use colored output in some tests)

    Running tests outside of Clion works fine

  4. Daniel says:

    October 17, 2017

    Two questions:

    1) Will there be a “Memory View” in 2017.3? Or planned in a future version?
    2) Which UnitTest-Framework do you recommend for plain old C?

    Thx and cheers Daniel

    • Anastasia Kazakova says:

      October 17, 2017

      Thanks for your questions:
      1) Memory view is on top of the queue, but I’m not sure about 2017.3, this might not fit, as we still have some other tasks for debugger.
      2) There are several options still. Good overview is here:

      • Daniel says:

        October 18, 2017


  5. stan says:

    November 30, 2017

    terrific article nice one for writing.

  6. Sergey Panov says:

    December 12, 2017

    My test suite is BOOST_FIXTURE_TEST_SUITE, not BOOST_AUTO_TEST_SUITE, and I am getting “Test framework quit unexpectedly” while the console output is:

    Running 15 test cases…
    *** No errors detected
    Process finished with exit code 0

    • Anastasia Kazakova says:

      December 12, 2017

      What’s your version of Boost?


Subscribe for updates