In odoo/documentation-user#945, the developer documentation is merged with the user documentation in a single repository and build config. This commit then removes source files for the developer documentation from the odoo/odoo repository. DOC PR: https://github.com/odoo/documentation-user/pull/945 task-2351938 task-2352371 task-2205684 task-2352544 Co-authored-by: Victor Feyens <vfe@odoo.com> Co-authored-by: Antoine Vandevenne <anv@odoo.com>
closes odoo/odoo#60601 Signed-off-by: Antoine Vandevenne (anv) <AntoineVDV@users.noreply.github.com>
* Cmdline interface: how to trigger database population * Testing: how to implement database population on a given model. * autodocumentation of the population methods + improve population methods docstrings. closes odoo/odoo#50596 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
Before this commit, the test assets were called with a `t-call-assets` and contained themselves some other `t-call-assets` to the back-end assets. According to the current specification, having nested `t-call-assets` will result in a compilation of the lower levels regardless of the current debugging mode. Now, the test bundles (desktop & mobile) have been arranged so that their `t-call-assets` are all called on the same level. closes odoo/odoo#49306 Related: odoo/enterprise#9797 Signed-off-by: Aaron Bohy (aab) <aab@odoo.com>
* Since https://github.com/odoo/odoo/commit/8d5da6e4be05428f3243f92c0464d3c1f6a43873#diff-e07cbcffb9fb7b2eafd1ace3c4b1626a, post_install and at_install test tags have been removed. * minor warnings in javascript reference. closes odoo/odoo#39817 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
When loading a page on an existing starting database, registry is not fully loaded causing potential error when trying to access model existing in database (views, menitem, ...) since model added in last loaded module does not exist in registry. Thus, executing browser js test may lead to errors when executed during an update on a database with other modules installed. HTTPCase should be executed post_install to ensure that registry is fully loaded to avoid this problem. Since HTTPCase are slower than other test, it is also a good idea to execute them at the end, in order to prioritize fast fail. With this commit, a warning is isued if such a test class is tagged to run at install time. While at it, remove deprecated at_install and post_install helpers and remove the deprecated phantom_js alias. closes odoo/odoo#39462 Signed-off-by: Christophe Monniez (moc) <moc@odoo.com>
closes odoo/odoo#37372 Signed-off-by: Christophe Simonis <chs@odoo.com>
Actually, when a browser_js test is running, screencasts and screenshots
are saved only if a "--logfile" parameter is specified.
This is problematic with the runbot because '--logfile' arg is not
provided when running tests. Also, in most situations, developpers
prefer to have logs on stdout.
With this commit, two CLI args are added to specify screencasts and
screenshots directories. If no screenshots dir is provided, it defaults
to "{tmp_dir}/odoo_tests/{db_name}/screenshots".
It means that screenshots are always enabled during browser_js tests.
If screencasts arg is given, it enables screencasts and save them in
"DIR/{db_name}/screencasts". If the screencasts parameter is "1", DIR
will be the same as for screenshots.
The ffmpeg tools is used to encode frames into a video. If the ffmpeg
tool is not found on the system, the frames are kept as pngs files
instead.
closes odoo/odoo#34640
Signed-off-by: Xavier Dollé (xdo) <xdo@odoo.com>
This commit adds a warning for common causes of mistakes, while running the JS test suite. It is possible to lose a lot of time trying to make the tests pass if one does not notice that the browser window is not zoomed at 100%. Maybe this warning will help someone in the future... closes odoo/odoo#29021