You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Chris Hostetter <ho...@fucit.org> on 2015/11/15 22:21:04 UTC
Re: test suite counter skipping numbers?
: > Tests summary: 100 suites (2 ignored), xx tests, xx ignored (xx assumptions).
:
: Will do it in the next version. Thanks for letting me know.
Dawid: that reminds me, if you are tweaking the logging, it would also be
helpful if the "Completed [X/Y] ..." line after each test also indicated
if there had been any failures so far, so you can see at a glance in your
terminal if any thing has failed up to this point (w/o needing to scroll
back, or wait for the ant command to complete.
for example...
>> [junit4] Completed [1/545] on J1 in 17.77s, 3 tests, 1 skipped
..just started, everything is all good..
>> [junit4] Completed [25/545 (1!)] on J3 in 7.35s, 5 tests, 5 skipped
..a suite just had failure, every "Completed" line after that will include
"(1!)" until another quite has a failure...
>> [junit4] Completed [26/545 (1!)] on J0 in 1.34s, 42 tests, 1 skipped
>> [junit4] Completed [27/545 (1!)] on J1 in 3.45s, 31 tests, 4 skipped
... if you glance at your terminal now, you know to scroll up because
something failed earlier...
If another test fails later the output changes a bit...
>> [junit4] Completed [145/545 (2!)] on J1 in 13.73s, 42 tests, 1 skipped
...etc...
-Hoss
http://www.lucidworks.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: test suite counter skipping numbers?
Posted by Dawid Weiss <da...@gmail.com>.
Done, Hoss.
https://issues.apache.org/jira/browse/LUCENE-6924
D.
On Mon, Nov 16, 2015 at 9:13 AM, Dawid Weiss <da...@gmail.com> wrote:
> Yeah... it'd be perfect to make it somehow configurable so that tweaks
> like this can be done without changing the code. I'll see what I can
> do.
>
> https://github.com/randomizedtesting/randomizedtesting/issues/220
>
> By the way -- if any of you guys is using argument factory methods
> I've added a nicer way to provide their names without the need to wrap
> the argument in a custom class, etc.
>
> https://github.com/randomizedtesting/randomizedtesting/releases/tag/release%2F2.3.0
>
> Dawid
>
> On Sun, Nov 15, 2015 at 10:21 PM, Chris Hostetter
> <ho...@fucit.org> wrote:
>>
>> : > Tests summary: 100 suites (2 ignored), xx tests, xx ignored (xx assumptions).
>> :
>> : Will do it in the next version. Thanks for letting me know.
>>
>> Dawid: that reminds me, if you are tweaking the logging, it would also be
>> helpful if the "Completed [X/Y] ..." line after each test also indicated
>> if there had been any failures so far, so you can see at a glance in your
>> terminal if any thing has failed up to this point (w/o needing to scroll
>> back, or wait for the ant command to complete.
>>
>> for example...
>>
>>>> [junit4] Completed [1/545] on J1 in 17.77s, 3 tests, 1 skipped
>>
>> ..just started, everything is all good..
>>
>>>> [junit4] Completed [25/545 (1!)] on J3 in 7.35s, 5 tests, 5 skipped
>>
>> ..a suite just had failure, every "Completed" line after that will include
>> "(1!)" until another quite has a failure...
>>
>>>> [junit4] Completed [26/545 (1!)] on J0 in 1.34s, 42 tests, 1 skipped
>>>> [junit4] Completed [27/545 (1!)] on J1 in 3.45s, 31 tests, 4 skipped
>>
>> ... if you glance at your terminal now, you know to scroll up because
>> something failed earlier...
>>
>> If another test fails later the output changes a bit...
>>
>>>> [junit4] Completed [145/545 (2!)] on J1 in 13.73s, 42 tests, 1 skipped
>>
>> ...etc...
>>
>>
>>
>> -Hoss
>> http://www.lucidworks.com/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: test suite counter skipping numbers?
Posted by Dawid Weiss <da...@gmail.com>.
Yeah... it'd be perfect to make it somehow configurable so that tweaks
like this can be done without changing the code. I'll see what I can
do.
https://github.com/randomizedtesting/randomizedtesting/issues/220
By the way -- if any of you guys is using argument factory methods
I've added a nicer way to provide their names without the need to wrap
the argument in a custom class, etc.
https://github.com/randomizedtesting/randomizedtesting/releases/tag/release%2F2.3.0
Dawid
On Sun, Nov 15, 2015 at 10:21 PM, Chris Hostetter
<ho...@fucit.org> wrote:
>
> : > Tests summary: 100 suites (2 ignored), xx tests, xx ignored (xx assumptions).
> :
> : Will do it in the next version. Thanks for letting me know.
>
> Dawid: that reminds me, if you are tweaking the logging, it would also be
> helpful if the "Completed [X/Y] ..." line after each test also indicated
> if there had been any failures so far, so you can see at a glance in your
> terminal if any thing has failed up to this point (w/o needing to scroll
> back, or wait for the ant command to complete.
>
> for example...
>
>>> [junit4] Completed [1/545] on J1 in 17.77s, 3 tests, 1 skipped
>
> ..just started, everything is all good..
>
>>> [junit4] Completed [25/545 (1!)] on J3 in 7.35s, 5 tests, 5 skipped
>
> ..a suite just had failure, every "Completed" line after that will include
> "(1!)" until another quite has a failure...
>
>>> [junit4] Completed [26/545 (1!)] on J0 in 1.34s, 42 tests, 1 skipped
>>> [junit4] Completed [27/545 (1!)] on J1 in 3.45s, 31 tests, 4 skipped
>
> ... if you glance at your terminal now, you know to scroll up because
> something failed earlier...
>
> If another test fails later the output changes a bit...
>
>>> [junit4] Completed [145/545 (2!)] on J1 in 13.73s, 42 tests, 1 skipped
>
> ...etc...
>
>
>
> -Hoss
> http://www.lucidworks.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org