-
Best Tools for First-Time Odoo Development
Thibaut Richard, Developer - OdooHoàn tất
-
How to Create l10n Payroll Structures
Yannick Tivisse, Developer - OdooHoàn tất
-
How to Deal with Custom Code for an Upgrade
Patricia Daloze, Developer - OdooHoàn tất
-
The New Tax Engine and How to Use It in Localizations
Olivier Colson, Developer - OdooHoàn tất
-
How to Develop Your Own In-App Purchase Service
Damien Bouvy , Developer - OdooHoàn tất
-
Load Testing: How to Stress Your Odoo with Locust
Michael Vannerom, Developer - OdooHoàn tất
-
Impact of the New ORM on Your ModulesRaphael Collet, Developer - OdooHoàn tất
-
Ask Me Anything for DevelopersAntony Lesuisse, Chief Technical Officer & Olivier Dony, Platform & Security - OdooHoàn tất
-
Odoo.sh for Project Managers & Developers
Benjamin Akboka Apengu, Developer - OdooHoàn tất
-
Odoo External API
Adrien Bonatesta, Developer - OdooHoàn tất
Stanislas is a client solution developer, and has been developing on Odoo for the last 4 years, specifically on customer projects. He has been the technical lead on Odoo's biggest customer project for the last 2 years with a team of 5 developers. Before working at Odoo, he taught for 7 years at the university level.
This talk will introduce a tool we've developed for big custom projects to record functional flows and create automated integration tests by using the standard unit tests making the most of your run bot.
This tool allows us to record a business flow made through the UI, generating the equivalent server side code in the database. Using that code allows us to quickly create integration tests with few modifications for the checks that need to be made. The tool tries to be smart to find the best fit for the records used in the flow by automatically generating external identifiers or finding a link to a previously existing record.
Due to the nature of the tool, the tests are generated after developing the features so it's a great tool to avoid regressions with future developments. Having your functional team or your customer recording the flow and recording what tests need to be done limits the work on the developer's side while making your code more robust. A few thousand lines of codes of testing can be done in a few hours.