2011-03-07 09:26:32 +00:00
|
|
|
{
|
2012-08-22 13:03:36 +00:00
|
|
|
'name': 'Web',
|
|
|
|
'category': 'Hidden',
|
2013-05-02 13:04:35 +00:00
|
|
|
'version': '1.0',
|
2012-08-22 13:03:36 +00:00
|
|
|
'description':
|
2011-11-25 11:07:15 +00:00
|
|
|
"""
|
2012-07-13 11:32:54 +00:00
|
|
|
OpenERP Web core module.
|
|
|
|
========================
|
|
|
|
|
|
|
|
This module provides the core of the OpenERP Web Client.
|
2011-11-25 11:07:15 +00:00
|
|
|
""",
|
2013-06-18 09:58:16 +00:00
|
|
|
'depends': ['base'],
|
2012-03-14 18:18:53 +00:00
|
|
|
'auto_install': True,
|
2014-01-09 15:11:40 +00:00
|
|
|
'data': [
|
|
|
|
'views/webclient_templates.xml',
|
|
|
|
],
|
2011-11-02 11:11:05 +00:00
|
|
|
'qweb' : [
|
|
|
|
"static/src/xml/*.xml",
|
|
|
|
],
|
2012-10-25 15:47:45 +00:00
|
|
|
'test': [
|
[IMP] setup & teardown of test runner
simplify code and make setup & teardown processes more reliable
add testing.Stack tools which stacks promise-returning functions
around the actual promise-returning function to execute (the test case
itself).
testing.Stack returns an object with 3 methods, ``push([setup][,
teardown])``, ``unshift([setup][, teardown])`` and ``execute(fn,
*args)``. ``push`` and ``unshift`` create a new stack with the
provided setup and teardown added respectively at the top and bottom
of the stack.
``execute`` will walk the stack from bottom to top executing ``setup``
handlers (and waiting on their result), if all setup handlers execute
without failure the ``fn`` callback gets executed (and waited on) then
*all* ``teardown`` handlers are executed from top to bottom:
| setup
| setup
| setup
| setup
| fn
| teardown
| teardown
| teardown
V teardown
If a ``setup`` handler fails (the promise is rejected), teardowns will
start executing *from the previous level* (so the ``teardown``
matching the failed ``setup`` will *not* be run), but all
``teardowns`` below that will be run regardless, even if one fails the
next one will still be executed.
The stack will either ultimately return a promise rejection using the
*first* rejection it got (a rejection may be cascading, so the
rejection of a setup may also lead to or be linked to a teardown being
rejected later), or will return the resolution from ``fn``.
If ``execute`` is passed further arguments, those arguments will in
turn be forwarded to ``fn`` as well as all ``setup`` and ``teardown``
handlers.
bzr revid: xmo@openerp.com-20121116071712-zuld957icellezum
2012-11-16 07:17:12 +00:00
|
|
|
"static/test/testing.js",
|
2013-07-26 16:07:15 +00:00
|
|
|
"static/test/framework.js",
|
2012-10-25 15:47:45 +00:00
|
|
|
"static/test/registry.js",
|
|
|
|
"static/test/form.js",
|
2013-04-16 09:23:44 +00:00
|
|
|
"static/test/data.js",
|
2012-10-25 15:47:45 +00:00
|
|
|
"static/test/list-utils.js",
|
|
|
|
"static/test/formats.js",
|
2013-08-01 16:32:21 +00:00
|
|
|
"static/test/rpc-misordered.js",
|
2012-10-25 15:47:45 +00:00
|
|
|
"static/test/evals.js",
|
|
|
|
"static/test/search.js",
|
2012-11-16 11:39:36 +00:00
|
|
|
"static/test/list.js",
|
2012-11-16 15:12:48 +00:00
|
|
|
"static/test/list-editable.js",
|
|
|
|
"static/test/mutex.js"
|
2012-10-25 15:47:45 +00:00
|
|
|
],
|
2011-03-07 09:26:32 +00:00
|
|
|
}
|