Domanda

We've got a test suite of about 2000 tests distributed over 50-60 files, that we run with nosetests. What is the best way to figure out which tests are running slowly? I could add a start/stop timer to the setUp method of every test, but this would be cumbersome to add to every file.

È stato utile?

Soluzione

The nosetests prof documentation provides details on how to profile your application. Easiest way is:

nosetests --with-profile
Autorizzato sotto: CC-BY-SA insieme a attribuzione
Non affiliato a StackOverflow
scroll top