It looks like we redirect stdout somewhere when we run "ant test"?  I
don't see my sops coming out in that case .... but if I run a single
test case, I do see them...

Mike McCandless

http://blog.mikemccandless.com

---------------------------------------------------------------------

> It looks like we redirect stdout somewhere when we run "ant test"?  I
> don't see my sops coming out in that case .... but if I run a single
> test case, I do see them...

If a test passes the output is not written to the console. This is
intentional to restrict the amount of noise written to the console.
Hints:

1) Full output for every test is always written to tests-report.txt
(under build folder).

2) pass -Dtests.showSuccess=true to get the output for successful
tests or put it in any of the following:

  <property file="${user.home}/lucene.build.properties"/>
  <property file="${user.home}/build.properties"/>
  <property file="${basedir}/build.properties"/>
  <property file="${common.dir}/build.properties"/>

to get the setting enabled permanently for every run.

Note that the output is written only after the test completes (because
otherwise it'd be difficult to coordinate the output from different
jvms).

Dawid

---------------------------------------------------------------------

Thanks Dawid!  -Dtests.showSuccess=true is what I was looking for ...
I'll add it to the wiki.

Mike McCandless

http://blog.mikemccandless.com
On Sat, Jun 2, 2012 at 10:28 AM, Dawid Weiss
<[EMAIL PROTECTED]> wrote:
>> It looks like we redirect stdout somewhere when we run "ant test"?  I
>> don't see my sops coming out in that case .... but if I run a single
>> test case, I do see them...
>
> If a test passes the output is not written to the console. This is
> intentional to restrict the amount of noise written to the console.
> Hints:
>
> 1) Full output for every test is always written to tests-report.txt
> (under build folder).
>
> 2) pass -Dtests.showSuccess=true to get the output for successful
> tests or put it in any of the following:
>
>  <property file="${user.home}/lucene.build.properties"/>
>  <property file="${user.home}/build.properties"/>
>  <property file="${basedir}/build.properties"/>
>  <property file="${common.dir}/build.properties"/>
>
> to get the setting enabled permanently for every run.
>
> Note that the output is written only after the test completes (because
> otherwise it'd be difficult to coordinate the output from different
> jvms).
>
> Dawid
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

---------------------------------------------------------------------

> Thanks Dawid!  -Dtests.showSuccess=true is what I was looking for ...
> I'll add it to the wiki.

Thanks, I'm wiki-challenged. There is also command-line help readily
available if you type:

ant test-help

     [echo] # Include additional information like what is printed to
     [echo] # sysout/syserr, even if the test passes.
     [echo] # Enabled automatically when running for a single test case.
     [echo] ant -Dtests.showSuccess=true test

Dawid

---------------------------------------------------------------------

On Sat, Jun 2, 2012 at 11:37 AM, Dawid Weiss
<[EMAIL PROTECTED]> wrote:
>> Thanks Dawid!  -Dtests.showSuccess=true is what I was looking for ...
>> I'll add it to the wiki.
>
> Thanks, I'm wiki-challenged. There is also command-line help readily
> available if you type:
>
> ant test-help
>
>     [echo] # Include additional information like what is printed to
>     [echo] # sysout/syserr, even if the test passes.
>     [echo] # Enabled automatically when running for a single test case.
>     [echo] ant -Dtests.showSuccess=true test

Thanks Dawid.  ant test-help is very useful; one of these days I'll
remember to run it when I'm confused :)

Mike McCandless

http://blog.mikemccandless.com

---------------------------------------------------------------------