id,summary,reporter,owner,description,type,status,milestone,component,version,severity,resolution,keywords,cc 7410,Test Units (Cases and Suites) in Boost.Test do not capture __FILE__ and __LINE__ at declaration point making it impossible to provide source file linking using external test management tools,Jamie Allsop ,Gennadiy Rozental,"We currently use [http://bitten.edgewall.org/ Bitten] as our continuous integration tool. We also use Boost.Test for all our unit tests. As Bitten integrates with [http://trac.edgewall.org/ Trac], which also provides the ability to browse our source repository, we want to be able to augment our test reports with links from test cases back to the source they appear in. In order to provide this capability we need to patch boost test so that __FILE__ and __LINE__ are captured in the test case and test suite macros. The patch attached to this ticket adds this capability. Once this information is available it becomes easy to extract this information from the test output. We use human readable output but this works equally well with the XML output. This can then be used by any number of continuous integration tools to provide much better test reports. In our case we turn each test case and test suite name into a link directly to the file and line in our source tree where the test unit was defined. This makes linking reports to actual source much more intuitive. This is a relatively simple patch and I have another follow on patch that further enhances the reporting capability of Boost.Test with a view to easier integration to third party tools. I'll comment back with the ticket number when it is created. We currently use a similar patch to the attached with our development code with boost 1.48. The attached patch is against trunk.",Patches,closed,Boost 1.59.0,test,Boost Development Trunk,Problem,fixed,,