Community mailing list archives
Re: The Speed of UnitTestsby
2016-08-16 17:42 GMT+02:00 Nhomar Hernandez <firstname.lastname@example.org>:
Can you point us where? no there are such things as "Odoo;s speeder" you need to point to the specific action which you considere slow in order to put a proper issue there.
I hope I could, but identifying bottlenecks would require many hours of R&D. This must be done by Odoo SA itself.What I was meaning with my comment is that, if testing all modules takes 103 seconds, but preparing the environment takes 13 minutes, then the problem is not in the tests, but in the framework (that maybe includes Postgres, not sure)
2016-08-16 18:02 GMT+02:00 David Arnold <email@example.com>:
I think, a further distinction throughout the framework between unit tests and integration tests is warranted. While unit tests MUST not depend on data files, integration tests possibly can but should avoide that. Having this distinction, one could optionally get rid of the data loading part as well by a flag. I hope Odoo testing engineers happen to read this thread.
Actually creating records by reading data files or by hardcoding the record creation in the test itself should not make much difference.
OTOH, I'm not sure I want a different DB backend in my tests and in my production environment, given tests are supposed to imitate the production environment as close as possible, where data files are loaded and Postgres is used.
If you could, however, use in-memory Postgres transactions, that would get what you want: skip hard disk.
Or simply buy a fast SSD.