GitLab

!306 (comment 63737)

The tests were written in qunit and were run through a unittest test case.
The tests were running in firefox and their results were reported through a
custom controller.
This changeset migrates these js tests to jest.


The TestCase subclass allowing to run js tests in firefox is still present in
devtools. We should probably deprecate it and check if other cubes are using it.

related: #339

related: #339

Version 4 of sphinx adds an incompatibility with the `iclassmethod` decorator
of logilab.common. This decorator is so strange that I am not sure that this
bug will ever get fixed.

For now, pin sphinx to version 1.8.5. This is the version used by readthedocs
by default and it still works with our codebase.
If https://github.com/sphinx-doc/sphinx/issues/9756 doesn't get fixed we should
start searching for a workaround.

For posterity, here is the error message we currently get when using sphinx 4:

```
File "<ENV>/lib/python3.7/site-packages/sphinx/util/inspect.py", line 853, in getdoc
    return getdoc(meth.__func__)
    AttributeError: 'iclassmethod' object has no attribute '__func__'
```

Closes #428.

pyramid.compat is deprecated and will be removed in Pyramid 2.0. The functionality is no longer necessary, as Pyramid 2.0 drops support for Python 2.

And we don't use python 2 anymore.

the rdflib-jsonld lib was not compatible with the new setuptools (v.58.0.1 and superior)
since there is no "use_2to3" function anymore

BREAKING CHANGE: The RDFLib v6 does not support python 3.6 anymore. With this dependency, CubicWeb neither.

This will allow to parallelize these tests and thus gain time.

related: #339

related: #434

- Python 3 version of Debian 10 (current stable) is 3.7.
  https://packages.debian.org/buster/python3
- Python 3 version of Ubuntu 20.04 (current LTS) is 3.8.
  https://packages.ubuntu.com/focal/python3

De facto, we don't test anymore on Python 3.6 and we won't change
this. In consequence, let's officially drop support for 3.6, that
might already be broken and that we would probably not want to fix
if it was the case.

--HG--
branch : 3.33

--HG--
branch : 3.33

--HG--
branch : 3.33

--HG--
branch : 3.32

--HG--
branch : 3.32

--HG--
branch : 3.32

--HG--
branch : 3.33

--HG--
branch : 3.32

--HG--
branch : 3.31

--HG--
branch : 3.30

--HG--
branch : 3.29

--HG--
branch : 3.29

--HG--
branch : 3.29

This feature was mistakenly droped during merge of 3.28.3 into 3.29.2.

Closes #404.

--HG--
branch : 3.29

--HG--
branch : 3.29