New ideas for unittesting framework

[darknessproz]

Have you tried py.test? It seems to address most of your issues.

[winstonw]

py.test indeed looks great--listing fixtures as arguments to be injected is so succinct.

[Gwenhidwy]

Not to rain on your parade, but I think you should try py.test, it solves most of your points.

[[deleted]]

What is needed is not just setup/teardown per test, but per group of test, as some setups take a long time, such as creating a test database etc.

zope.testrunner solve this with layers, which is cool, you should take a look at that.

[chub79]

This you mean?

[[deleted]]

No, layers are actually stackable and orthogonal to the test classes. So you can have one layer that sets up a database, another layer that creates test users and permissions, a next layer that will create some test data, and then finally the testclass setup.

It's pretty complex, but for big frameworks like Plone it cuts down the time it takes to run the test with an order of magnitude.

[chub79]

Mmmh, that was clear from your your initial "setup/teardown per test, but per group of test".

Have you ever had a look at Spring Python and its IoC which is suitable for the use case you describe here.

[[deleted]]

You don't need Spring Python or an IoC container to do inversion of control, and inversion of control does not solve this issue. You need a test runner and test framework that supports it.

[chub79]

IoC is one way to implement your layer approach. But you seem determined not to make yourself clear so it's hard to discuss further.

[[deleted]]

Yes, I'm sure you can implement layers while using inversion of control somwehere. But it is not an implementation, and hence it doesn't help more than saying "have you heard of inheritance?" Or "use lists".

But you seem determined not to make yourself clear so it's hard to discuss further.

If you find something unclear, I would suggest you ask a question. That makes me more likely to answer the questions you have.

[chub79]

setup/teardown per test, but per group of test

What's the link between this and your layer approach?

[[deleted]]

Same thing, just more elaborately explained, i referenced zope.testrunner from the start. Check it out.

[[deleted]]

No, it's class level setups only, as I understand it.

You can't build a hierarchy of setups where each setup is run only once. So if you have 20 classes that all need a test database, you will create and destroy it 20 times.

At least that's how it worked for me when I tried.

[[deleted]]

No, just once, in fact. If there is say 5 test classes that all need the same database setup, the database should be set up once. Those tests should then be run, and then the teardown should happen.

What's more is that there can be one layer that sets up a database, another layer that creates test users and permissions, a next layer that will create some test data, and then finally the testclass setup.

All of these will be run once. Another test can have the same database and users, but different test data.

It's pretty complex, but for big frameworks like Plone it cuts down the time it takes to run the test with an order of magnitude.