[Boost-bugs] [Boost C++ Libraries] #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

Subject: [Boost-bugs] [Boost C++ Libraries] #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
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2012-09-22 22:05:51


#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
------------------------------------------------+---------------------------
 Reporter: Jamie Allsop <ja11sop@…> | Owner: rogeeff
     Type: Patches | Status: new
Milestone: To Be Determined | Component: test
  Version: Boost Development Trunk | Severity: Problem
 Keywords: |
------------------------------------------------+---------------------------
 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.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/7410>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:10 UTC