GitLab

This was another thing matching the newer way of doing things in Watir,
but we use an older version

sometimes the test will fail because the DOM hasn't fuly loaded, so we
need to wait for the table line we want to be present

Since we use an old version of watir for our tests, we need to use the
old way of doing things :)

for the call to Watir::Wait.until simply pass the timeout value instead
    of passing a named parameter

$1 is only the first parameter thus launch_functional_tests usage was not
clear. Instead we use $*.

Follows a4d71986

(not currently working)

preserve the edited patient in order to apply the filter on its info.

reorganise the server functional test files to match the browser
functional tests

Patients are sorted in reverse order of creation, so we should expect
the last patient created when clicking on the first row.

using array-style accessors doesn't work unless dealing with an array or
collection. The :index attribute is what we want here.

using the accessors was yielding the content of the first table row.
Using table.tbody.rows yields a collection of rows which is exactly what
we want.

concatenating strings and integers without converting ? Might as well
use modifiers.

button wasn't found due to some unwanted whitespace.

use an array of strings when selecting elements over multiple classes.

When the form gets reloaded in the page, the initial login_form variable
will no longer evaluate to present since. So we need to reassign the
variable with the Watir selectors in order to check if it is present.

basic set of functional tests to ensure the views are sending to correct
data to the controllers

set the admin password before changing file ownership. Ensures web2py is
able to update the admin password.

fix fcgiwrap, imgt_proxy, cgi address in conf.js, add in cgi files. add
vidjil-algo

Since in gitlab-ci we are launching the unit tests on the host, and the
database initialisation needs to be launched on the docker container, we
want to separate the two.

ensure the db is reset in order to test the database initialisation
mechanism.

We don't want reset_db to be accessible in a controller. Moving it to a
module ensures it can only be executed inside a script or controller.
Also add a script so we can reset the database before launching
functional tests.

This was not working for mysql databases due to the usage of foreign
keys, so we now disable to foreign keys if using mysql before truncating
tables.

fix known bug in correct version of base.py and replace with the one installed from
packages.

starting it in the background doesn't seem to be working. The detached
mode must exist for this purpose

due to our runner meccano having the i686 architecture, for which there
is no official image for MySQL, and alternatives were causing issues.

since we're running docker-compose in the background, we need to wait
for our containers to have started before attempting to run our tests