~openerp-community/openobject-server/fix-1130010-toxml-escape-quot

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
.. _openerp-command:

The ``oe`` script
=================

The ``oe`` script provides a set of command-line tools around the OpenERP
framework. It is meant to replace the older ``openerp-server`` script (which
is still available).

Using ``oe``
------------

In contrast to the previous ``openerp-server`` script, ``oe`` defines a few
commands, each with its own set of flags and options. You can get some
information for any of them with

::

  > oe <command> --help

For instance::

  > oe run-tests --help

Some ``oe`` options can be provided via environment variables. For instance::

  > export OPENERP_DATABASE=trunk
  > export OPENERP_HOST=127.0.0.1
  > export OPENERP_PORT=8069

Depending on your needs, you can group all of the above in one single script;
for instance here is a, say, ``test-trunk-view-validation.sh`` file::

  COMMAND_REPO=/home/thu/repos/command/trunk/
  SERVER_REPO=/home/thu/repos/server/trunk

  export PYTHONPATH=$SERVER_REPO:$COMMAND_REPO
  export PATH=$SERVER_REPO:$COMMAND_REPO:$PATH
  export OPENERP_DATABASE=trunk
  export OPENERP_HOST=127.0.0.1
  export OPENERP_PORT=8069

  # The -d ignored is actually needed by `oe` even though `test_view_validation`
  # itself does not need it.
  oe run-tests -d ignored -m openerp.test_view_validation

Available commands
-------------------

See the :doc:`commands` page.

Adding new commands
-------------------

See the :doc:`adding-command` page.

Bash completion
---------------

A preliminary ``oe-bash-completion`` file is provided. After sourcing it,

::

  > . oe-bash-completion

completion (using the TAB character) in Bash should work.