scm-app: allow to set documented pyro4 as scm_app_implementation....

scm-app: allow to set documented pyro4 as scm_app_implementation. The documented ini setting allows to set pyro4 as scm_app, while the backend code crashes on import of pyro4 module. This change allows to configure the app based on the .ini docs. if we pass pyro4 as backedn, we simply skip import and use the default pyro4 scm_app

marcink - - Load All Authors

File last commit:

r1:854a839a default


                r632:064401fe

default

Download file

             naming-conventions.rst
        
                    29 lines
            
             | 689 B
            
                | text/x-rst
            
             |
                RstLexer

/ docs / contributing / testing / naming-conventions.rst

History | Annotation | Raw |Copy content |Copy permalink

Naming conventions

We found so far a few patterns emerging in our py.test fixtures. The naming conventions for those are documented on this page.

Utilities - `_util`

Used for fixtures which are used to ensure that the pre-conditions of the test are met. Usually it does not matter so much for the test how they achieve this. Most utilities will clean up automatically after themselves.

Use the suffix _util.

Page objects - `{route_name}_page`

Used as abstractions of pages.

Use the suffix _page and if possible use the route name as the prefix.

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

Naming conventions

Utilities - _util

Page objects - {route_name}_page

Utilities - `_util`

Page objects - `{route_name}_page`