Boost logo

Boost :

From: Gennadiy Rozental (gennadiy.rozental_at_[hidden])
Date: 2007-03-21 13:53:30

"Jeremy Pack" <rostovpack_at_[hidden]> wrote in message
> This could be handy. Boost.Test does integrate rather nicely with both
> Visual Studio and Xcode though (it lets you jump to the source code where
> the error occurred) - so I'd expect such a front end to do more than just
> let me jump to a spot in source code.

We may want ot add different test log/outputs to meat different IDE

> Also, if you built a Windows application, I believe most developers who
> write C++ in Windows use Visual Studio. A Visual Studio addon might be
> more
> appropriate for them.

Yes. THat What I though it should look like.

> If I were doing this, I might try something like the following:
> Build a command line application that can:
> 1 - Run the unit tests that result from compiling a set of source files
> (equivalent to a [ run ../src/$(CPP).cpp ] in a Jamfile). I may not want
> to
> run all of my unit tests, and just want an interface to run those from one
> file.

1.34.0 includes boost_test_runner tool. It could be used to run test modules
build as DLLs. Test case selection support is planned for next release.

> 2 - Automatically add test cases.

test suites, fixtures etc

> 3 - Run in a loop where it repeatedly compiles and runs any unit tests
> whose
> source files have changed (I could have this open in a command window as I
> code, and see failing unit tests soon after I save my faulty code).
> And then build a Visual Studio addon that makes it possible to use this
> command line application from inside VS. It would parse the information,
> and
> display it to the user in useful ways, and allow the user to go straight
> to
> where tests failed, or just run a single file's unit tests.

I am ont sure that command line based addon is based approach. I would
rather do separate test runner as addon.


Boost list run by bdawes at, gregod at, cpdaniel at, john at