1 | # pylint: disable=unused-variable,expression-not-assigned |
||
0 ignored issues
–
show
|
|||
2 | |||
3 | from unittest.mock import patch, call |
||
4 | |||
5 | import pytest |
||
6 | from expecter import expect |
||
0 ignored issues
–
show
The import
expecter could not be resolved.
This can be caused by one of the following: 1. Missing DependenciesThis error could indicate a configuration issue of Pylint. Make sure that your libraries are available by adding the necessary commands. # .scrutinizer.yml
before_commands:
- sudo pip install abc # Python2
- sudo pip3 install abc # Python3
Tip: We are currently not using virtualenv to run pylint, when installing your modules make sure to use
the command for the correct version.
2. Missing __init__.py filesThis error could also result from missing ![]() |
|||
7 | |||
8 | from gdm import cli |
||
9 | |||
10 | |||
11 | def describe_gdm(): |
||
0 ignored issues
–
show
This function should have a docstring.
The coding style of this project requires that you add a docstring to this code element. Below, you find an example for methods: class SomeClass:
def some_method(self):
"""Do x and return foo."""
If you would like to know more about docstrings, we recommend to read PEP-257: Docstring Conventions. ![]() |
|||
12 | |||
13 | @pytest.fixture |
||
14 | def config(tmpdir): |
||
0 ignored issues
–
show
This function should have a docstring.
The coding style of this project requires that you add a docstring to this code element. Below, you find an example for methods: class SomeClass:
def some_method(self):
"""Do x and return foo."""
If you would like to know more about docstrings, we recommend to read PEP-257: Docstring Conventions. ![]() |
|||
15 | tmpdir.chdir() |
||
16 | path = str(tmpdir.join("gdm.yml")) |
||
17 | open(path, 'w').close() |
||
18 | return path |
||
19 | |||
20 | def describe_edit(): |
||
0 ignored issues
–
show
This function should have a docstring.
The coding style of this project requires that you add a docstring to this code element. Below, you find an example for methods: class SomeClass:
def some_method(self):
"""Do x and return foo."""
If you would like to know more about docstrings, we recommend to read PEP-257: Docstring Conventions. ![]() |
|||
21 | |||
22 | @patch('gdm.system.launch') |
||
23 | def it_launches_the_config(launch, config): |
||
0 ignored issues
–
show
This function should have a docstring.
The coding style of this project requires that you add a docstring to this code element. Below, you find an example for methods: class SomeClass:
def some_method(self):
"""Do x and return foo."""
If you would like to know more about docstrings, we recommend to read PEP-257: Docstring Conventions. ![]() |
|||
24 | cli.main(['edit']) |
||
25 | |||
26 | expect(launch.mock_calls) == [call(config), call().__bool__()] |
||
27 | |||
28 | def it_exits_when_no_config_found(tmpdir): |
||
0 ignored issues
–
show
This function should have a docstring.
The coding style of this project requires that you add a docstring to this code element. Below, you find an example for methods: class SomeClass:
def some_method(self):
"""Do x and return foo."""
If you would like to know more about docstrings, we recommend to read PEP-257: Docstring Conventions. ![]() |
|||
29 | tmpdir.chdir() |
||
30 | |||
31 | with expect.raises(SystemExit): |
||
32 | cli.main(['edit']) |
||
33 |
The coding style of this project requires that you add a docstring to this code element. Below, you find an example for methods:
If you would like to know more about docstrings, we recommend to read PEP-257: Docstring Conventions.