[TIP] paramterized or generative tests [was nose2: the nosening]

[Michael Foord]

On 06/08/2010 02:23, Jesse Noller wrote:
> [snip...]
> ps: If nose2/unittest2 could find it in it's shiny new innocent heart
> to say, have support for test generators; I'd die happy.
>    

Well there's another discussion :-)

It would be very simple to support parameterized tests (of some form), 
where the number of tests can be known at test load time. Supporting 
generative tests - where the tests are generated at *test run time* is 
uglier.

Would parameterized tests, where the tests are all generated at test 
load time, suffice or do you have a use case for generative tests where 
the tests have to be generated whilst the tests are running and not when 
the tests are loaded?

Michael

> _______________________________________________
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
> http://lists.idyll.org/listinfo/testing-in-python
>    


-- 
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog

READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.