Contributors mailing list archives

contributors@odoo-community.org

Odoo report testing

by
Anybox, Pierre Verkest
- 30/11/2016 11:15:51
Hi,

Since my last message[1] in this ML regarding Odoo report testing some works has been done:

* extract the code from anybox.testing.openerp to a gh repo: https://github.com/anybox/odoo-report-testing
* test the lib on travis against some version of odoo (OK: 7.0, 8.0, WIP: 9.0, 10.0)
* release the first version on pipy: https://pypi.python.org/pypi/odoo-report-testing/
* document the lib: https://odoo-report-testing.readthedocs.io
* write a blog post regarding the philosophy and the why of this lib: https://anybox.fr/blog/how-do-you-develop-odoo-report-are-you-testing-them

If you still get interest on this tool I'm happy to move it under OCA umbrella, I'm just wondering
how to process, we may have a IRC discussion to figure out how to do it (I'm petrus-v feel free to ping me). There are probably some technical points to discuss before moving it:

* I've chosen to use anybox.recipe.odoo to run unit tests because I didn't know how to
  run them (as they are not part of an Odoo module) using OCA MQT repo[2] so of course that can change.
* Setting up wkhtml2pdf and lessc to the expected version on Travis dockerized builder is a bit a nightmare to me, helps welcome!
* If we start to use this lib in various OCA repo to test report we have to be ready with the previous point (I haven't look yet last changes from Moises and Alexandre regarding dockerized builds I guess that may be benefit)

Regards,
[2] I had a try at this commit but my unit test wasn't running: https://github.com/anybox/odoo-report-testing/tree/16fb95266e2993dc2ae4b816fe4c4734b3e7b4df

--
Anybox
Pierre Verkest
06 51 35 50 50
Github: petrus-v - Twitter: petrusv84