|
|
@ -68,7 +68,7 @@ Tests |
|
|
|
This module comes with a simple test in static/test/context_tunnel.js. |
|
|
|
To run it, open the page /web/tests?mod=web_context_tunnel in your browser |
|
|
|
as explained here https://doc.openerp.com/trunk/web/testing |
|
|
|
It should also by picked by the Python testing when testing with PhantomJS. |
|
|
|
It should also be picked by the Python testing when testing with PhantomJS. |
|
|
|
|
|
|
|
As for testing modules using web_context_tunnel with YAML, yes it's possible. |
|
|
|
In fact you need to manually mimic the new web-client behavior by manually |
|
|
@ -78,16 +78,17 @@ a !python statement like context.update({'my_extra_field': my_extra_field}). |
|
|
|
|
|
|
|
You can see an example of module conversion to use web_context_tunnel here |
|
|
|
for instance: |
|
|
|
https://github.com/openerpbrasil/l10n_br_core/compare/develop...feature%2Fsale-web-context-tunnel |
|
|
|
https://github.com/openerpbrasil/l10n_br_core/commit/33065366726a83dbc69b9f0031c81d82362fbfae |
|
|
|
""", |
|
|
|
'version': '2.0', |
|
|
|
'depends': ['web'], |
|
|
|
'js': ['static/src/js/context_tunnel.js'], |
|
|
|
'data': [ |
|
|
|
'views/web_context_tunnel.xml', |
|
|
|
], |
|
|
|
'test': [ |
|
|
|
'static/test/context_tunnel.js', |
|
|
|
], |
|
|
|
'css': [], |
|
|
|
'auto_install': False, |
|
|
|
'installable': False, |
|
|
|
'web_preload': False, |
|
|
|
} |