The Stack Overflow podcast is back! Listen to an interview with our new CEO.
2 continuous testing.
source | link

I have used both Google Test and Boost Test. Both are xUnit frameworks, work on Unix and Windows, and are mature. I ended up using Google Test due to Google Mock since I wanted a mocking framework as well. Either should work well under buildbot.

Personally, I want the unit test framework to be minimal and fast. I want many tests and thus want them to run in a reasonable time frame. I personally like to use the main framework for a language instead of a mega tool but that is personal. If you wanted, you could look at continuous iteration testing: every time you save a file, it auto-runs the test cases that file depends on.

You could always write an Interface class to your unit test thus allowing a quick and effective change of frameworks.

I have used both Google Test and Boost Test. Both are xUnit frameworks, work on Unix and Windows, and are mature. I ended up using Google Test due to Google Mock since I wanted a mocking framework as well. Either should work well under buildbot.

Personally, I want the unit test framework to be minimal and fast. I want many tests and thus want them to run in a reasonable time frame. I personally like to use the main framework for a language instead of a mega tool but that is personal.

You could always write an Interface class to your unit test thus allowing a quick and effective change of frameworks.

I have used both Google Test and Boost Test. Both are xUnit frameworks, work on Unix and Windows, and are mature. I ended up using Google Test due to Google Mock since I wanted a mocking framework as well. Either should work well under buildbot.

Personally, I want the unit test framework to be minimal and fast. I want many tests and thus want them to run in a reasonable time frame. I personally like to use the main framework for a language instead of a mega tool but that is personal. If you wanted, you could look at continuous iteration testing: every time you save a file, it auto-runs the test cases that file depends on.

You could always write an Interface class to your unit test thus allowing a quick and effective change of frameworks.

1
source | link

I have used both Google Test and Boost Test. Both are xUnit frameworks, work on Unix and Windows, and are mature. I ended up using Google Test due to Google Mock since I wanted a mocking framework as well. Either should work well under buildbot.

Personally, I want the unit test framework to be minimal and fast. I want many tests and thus want them to run in a reasonable time frame. I personally like to use the main framework for a language instead of a mega tool but that is personal.

You could always write an Interface class to your unit test thus allowing a quick and effective change of frameworks.