Odoo/addons/website_hr_recruitment/tests, branch 14.0

[IMP] website_hr_recruitment: Adapt tests to work with/without demo data

2019-11-05T15:18:10+00:00

[IMP] tests, *: add start_tour helper

2019-04-04T08:44:59+00:00

Before this commit, the syntax to start a tour was extremely verbose.
With this new method, it is possible to start a tour by just giving the
essential parameter: the tour name.
The full set of features from browser_js are kept by using **kwargs.

closes odoo/odoo#32316

Signed-off-by: Christophe Monniez (moc)

[REF] tests: `TestCursor` is now a proxy to a real `Cursor`

2018-02-12T09:31:59+00:00

This allows rpc requests in `HttpCase` to use the cursor `self.cr`, which is
now shared between the Python test and the rpc requests.  This simplifies code
to prepare a JS test, and code to check the result of a JS tour.

Fixes #12237

[IMP] tests: Add the possibility to tag tests

2018-01-18T12:20:37+00:00

Purpose: When running tests, all the tests for the installed/updated
files are done. This commit adds a 'tagged' decorator that can be used to
tag tests. Combined with a new 'test-tags' CLI option, it adds the ability
to filter which tests are executed. For example, @tagged('slow') will
add a tag 'slow' to the test. The CLI option 'test-tags="slow"' will
only run tests tagged 'slow'.

One can use prefixes to select cases with tags.
'+' or no prefix means that the tests tagged with this tag are selected
for execution. '-' prefix will exclude the tests tagged with this tag.
Exclusion takes precedence over inclusion.

Also, by default, all Odoo tests cases are tagged 'standard' and with
the technical name of the module.
This means that when selecting tests with the 'test-tags'
parameter, if '-standard' is not specified, all tests tags are
going to be executed.
When tagging tests, one can remove such automatic tag by prefixing the
tag name with '-'. E.g. @tagged('-standard') will remove the standard
tag from the test.

Another example, if one wants to test the 'sale' module alone,
even without adding any 'tagged' decorator thos tests can be selected
like that: --test-tags="sale"

Tests are selected or deselected using a TagsSelector. When instanciated,
 a string is passed with comma separated tests selectors like
'+slow,-standard'. When the 'check' method is called  with a test as argument,
it returns True or False if the test has to be executed or not.

[FIX] Various P3-related import changes

2017-04-28T07:06:53+00:00

* LDAP import: python-ldap is not python3-compatible, pyldap is

  Warning: only supported from debian Stretch (current testing)?
  https://packages.debian.org/search?searchon=names&keywords=pyldap

* implicitly relative imports
* imports of moved or removed stdlib modules

issue #8530

[IMP] website_hr_recruitment: convert tours to use web_tour.tour

2016-08-30T11:54:28+00:00

[IMP] various: use odoo for imports instead of openerp and update class names

2016-08-10T13:48:07+00:00

[FIX] website_crm and website_hr_recruitment tours

2015-09-04T10:59:27+00:00

* run tours as public users since these screens should be accessible to
  and used by public users
* fix access rights issues in website_crm tour (default value of team_id
  when creating a crm.lead requiring read access on crm.team, which the
  public user does not have)
* remove duplicated crm.lead field (phone declared as char(size=64) then
  as char() a few lines below, removed first instance)

[IMP] crm & hr_recruitment tours: remove unnecessary tours

2015-09-04T10:59:27+00:00

To check for result of a tour, would run a second tour performing
JSON-RPC calls to check if the first tour had correctly impacted the
database.

Tours are expensive, an empty tour takes ~6s without doing anything.

Replace second tour by regular ORM calls.

[ADD] website_form: generic form controller

2015-08-26T14:01:19+00:00

Contains a new ajax post function that comes from mdo's
original code and that I was not able to get rid of.