##// END OF EJS Templates
docs: Update notes regarding Pylons / Pyramid
johbo -
r739:3f65f91e default
parent child
Show More
@@ -23,20 +23,28 py.test integration
23
23
24 The integration with the test runner is based on the following three parts:
24 The integration with the test runner is based on the following three parts:
25
25
26 - `pytest_pylons` is a py.test plugin which does the integration with the
26 - :file:`rhodecode/tests/pylons_plugin.py` is a py.test plugin which does the
27 Pylons web framework. It sets up the Pylons environment based on the given ini
27 integration with the Pylons web framework. It sets up the Pylons environment
28 file.
28 based on the given ini file.
29
29
30 Tests which depend on the Pylons environment to be set up must request the
30 Tests which depend on the Pylons environment to be set up must request the
31 fixture `pylonsapp`.
31 fixture `pylonsapp`.
32
32
33 - :file:`rhodecode/tests/plugin.py` contains the integration of py.test with
33 - :file:`rhodecode/tests/plugin.py` contains the integration of py.test with
34 RhodeCode Enterprise itself.
34 RhodeCode Enterprise itself and it takes care of setting up the needed parts
35 of the Pyramid framework.
35
36
36 - :file:`conftest.py` plugins are used to provide a special integration for
37 - :file:`conftest.py` plugins are used to provide a special integration for
37 certain groups of tests based on the directory location.
38 certain groups of tests based on the directory location.
38
39
39
40
41 .. note::
42
43 We are migrating from Pylons to its successor Pyramid. Eventually the role of
44 the file `pylons_plugin.py` will change to provide only a Pyramid
45 integration.
46
47
40
48
41 VCS backend selection
49 VCS backend selection
42 ---------------------
50 ---------------------
General Comments 0
You need to be logged in to leave comments. Login now