Hi,
I'm processing a series of log files and looking at each one for certain
strings of interest. Rather than keep the regex strings in the ant file
itself, it would be preferable to keep them as a group of properties stored
in a file.
Is this possible? Has anyone tried keeping their regex valu
Hi,
I have some tests that send output to plain text files. Its easy to spot
errors in the files by simply doing something like:
What I cannot figure out, is how to log something that would identify
exactly what the er
>
> apparently not
> i saw "junitreport" and assumed your junitreport task was spawning n number
> ANT junit task(s)
>
> would be interested to know the solution graham provides
Me too. :)
-T
>
>
> Martin Gainty
> __
> Verzicht und Vertraulichkeitanme
Hi Martin,
Thanks for the quick reply!
Since the tap2junit utility is used to convert a non-junit test to
junit-like output, I do not have a junit definition. Do I need one even if
I'm not using junit?
-T
On Sun, Jul 26, 2009 at 5:51 PM, Martin Gainty wrote:
>
> somewhere in the build.xml yo
Hi Graham,
I'm using your excellent tap2junit tool to try and convert some test
output. I'm using ant (version 1.7.1) and running 'junitreport' on the
converted output.
I'm hoping you can understand why junitreport says this:
[junitreport] the file
/opt/cruisecontrol/projects/itinerator/results/
Hi,
Is there some kind of debug command I can turn on to figure why this is
happening??
[junitreport] the file
/opt/cruisecontrol/projects/itinerator/results/ListTest.1254.xml is not a
valid testsuite XML document
-T
to filter out all the lines that contain
> the regular expression that shows zero errors, tests, and time taken.
>
> Once I've done that, I use the fail to fail the build, but I only fail
> on the condition that the combined test results file is not empty. If
> all the tests are val
Hi,
This is about ant used with cruisecontrol, but I thought someone here may
know the answer. Nobody seems to know on the cc mailer.
I have a few tests that will be shown as "Tests: 0, Failures: 0, Errors: 0,
Duration: 0.0" in the dashboard's test suites report. Generally, this is a
poorly cod
