|
Boost Testing : |
From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-11-16 03:25:10
On Wednesday 15 November 2006 23:34, Juergen Hunold wrote:
Hi Jürgen!
> On Monday 18 September 2006 09:21, Vladimir Prus wrote:
> > Hi,
> > the libs/test/test/Jamfile has the following code:
> >
> > test-suite "prg_exec_monitor_test"
> >
> > : [ test-btl-lib run-fail : prg_exec_fail1 ]
>
> Which is currently failing at my WinXP machine because it needs static
> link library ;-)
>
> > When I look at regression test results:
> >
> > http://tinyurl.com/joyut
> >
> > I don't see any mention of those four tests. Anybody knows what's
> > wrong?
>
> I think I've trace this down to
> tools/regression/xsl_reports/xsl/v2/common.xsl
> ( or the same filename one directory up, I don't know which xsl script
> are used at the moment...)
>
> At line 148 there is a XSLT function "meta:is_test_log_a_test_case"
> which is obviously used to test whether a test_log is a valid test
> case.
> Unfortunately, the current version only checks for
> -compile
> -compile_fail
> -run
> -run_pyd
>
> The three remaining test categories are missing:
> - link (used by asio test in HEAD, after a short grep...)
> - link_fail (unused)
> - run_fail (used by Boost.Test tests.)
Ah, so this should be a simple change!
> So at least four tests are falling off the radar right now...
>
> The attached patch should solve the problem.
> Warning: untested, as I've just copy & edited the text and have to
> figure out how to create the test summary page myself.
>
> It would be nice if someone from metacomm could comment on this...
Alexey, can you briefly comment if this patch looks reasonable, or there's
something deeper going on?
Thanks,
Volodya
>