Hi,
2016-11-23 20:43 GMT+02:00 Emmanuel Bourg <[email protected]>:
>
> Hi,
>
> I'd like to suggest a minor improvement to better control the verbosity
> of the tests. Currently the output of the tests is displayed on the
> console, and it's rather difficult to see which tests failed until the
> whole suite ran.
>
> The build could use an extra parameter, for example "test.verbose" to
> allow the developers to control the verbosity. The output would then
> look similar to what we get by default with Maven projects. If the
> parameter isn't specified the tests remain verbose.
Thanks for the report and the patch.
This has been fixed in
- 9.0.x for 9.0.0.M14 onwards
- 8.5.x for 8.5.9 onwards
- 8.0.x for 8.0.40 onwards and
- 7.0.x for 7.0.74 onwards
Regards,
Violeta
> --- a/build.properties.default
> +++ b/build.properties.default
> @@ -41,6 +41,8 @@ execute.test.apr=true
> test.haltonfailure=false
> # Activate AccessLog during testing
> test.accesslog=false
> +# Display the tests output on the console
> +test.verbose=true
>
> # Note the Cobertura code coverage tool is GPLv2 licensed
> test.cobertura=false
> diff --git a/build.xml b/build.xml
> index bc21643..721adfc 100644
> --- a/build.xml
> +++ b/build.xml
> @@ -1398,7 +1398,7 @@
>
> <sequential>
> <mkdir dir="${test.reports}" />
> - <junit printsummary="yes" fork="yes" dir="." showoutput="yes"
> + <junit printsummary="yes" fork="yes" dir="."
showoutput="${test.verbose}"
> errorproperty="test.result.error"
> failureproperty="test.result.failure"
> haltonfailure="${test.haltonfailure}" >
>
>
>
> Emmanuel Bourg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
