[curious] stack test runs more tests than requested

[curious] stack test runs more tests than requested

[pandoc-only-Mmb7MZpHnFY]

[-- Attachment #1.1: Type: text/plain, Size: 1416 bytes --]

Greetings,

I noticed that stack test --test-arguments='-p something' evaluates more 
tests than selected by the pattern "something", probably all of them.  
Someone more familiar with the Haskell evaluation mechanics may want to 
look into that - or not.

My sources are based on version 2.2.1, and I have tinkered quite a bit with 
the docx reader, so i have a few tests that I want to run for that aspect.  
But when I insert a Debug.Trace.trace in testCompare, it beeps for every 
test there is.  The tests are also evaluated in depth, since my tracing 
calls deep in the field-parsing code also produce output.

The test run only reports on the selected tests, and I assume failures from 
the superfluous tests are ignored, so there is no functional deficiency.  
But it would be nice to have things run a little faster.

Greetings,
Felix

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/eec12cc2-cf62-4226-9701-36d75f9d56fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 1947 bytes --]

Re: [curious] stack test runs more tests than requested

[John MacFarlane]

We use the tasty test framework, so maybe it would
make sense to ask its author whether --test-arguments
actually suppresses running the tests, or just
reporting them.   It could be that adding 'trace'
changes things somehow?

I used 'time' to compare running the tests with
different patterns, and including more tests
definitely takes more time...

pandoc-only-Mmb7MZpHnFY@public.gmane.org writes:

> Greetings,
>
> I noticed that stack test --test-arguments='-p something' evaluates more 
> tests than selected by the pattern "something", probably all of them.  
> Someone more familiar with the Haskell evaluation mechanics may want to 
> look into that - or not.
>
> My sources are based on version 2.2.1, and I have tinkered quite a bit with 
> the docx reader, so i have a few tests that I want to run for that aspect.  
> But when I insert a Debug.Trace.trace in testCompare, it beeps for every 
> test there is.  The tests are also evaluated in depth, since my tracing 
> calls deep in the field-parsing code also produce output.
>
> The test run only reports on the selected tests, and I assume failures from 
> the superfluous tests are ignored, so there is no functional deficiency.  
> But it would be nice to have things run a little faster.
>
> Greetings,
> Felix
>
> -- 
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/eec12cc2-cf62-4226-9701-36d75f9d56fb%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Re: [curious] stack test runs more tests than requested

[pandoc-only-Mmb7MZpHnFY]

[-- Attachment #1.1: Type: text/plain, Size: 1640 bytes --]

Timing the penalty sure helps put things in perspective.  Seems not to be 
worth the effort.

On Tuesday, July 24, 2018 at 7:06:02 PM UTC+2, pando...-Mmb7MZpHnFY@public.gmane.org wrote:
>
> Greetings,
>
> I noticed that stack test --test-arguments='-p something' evaluates more 
> tests than selected by the pattern "something", probably all of them.  
> Someone more familiar with the Haskell evaluation mechanics may want to 
> look into that - or not.
>
> My sources are based on version 2.2.1, and I have tinkered quite a bit 
> with the docx reader, so i have a few tests that I want to run for that 
> aspect.  But when I insert a Debug.Trace.trace in testCompare, it beeps for 
> every test there is.  The tests are also evaluated in depth, since my 
> tracing calls deep in the field-parsing code also produce output.
>
> The test run only reports on the selected tests, and I assume failures 
> from the superfluous tests are ignored, so there is no functional 
> deficiency.  But it would be nice to have things run a little faster.
>
> Greetings,
> Felix
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/4ad683df-1420-44d3-8cb5-5b26d887c981%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 2288 bytes --]