Passed
Push — master ( 691bd8...662939 )
by Marco
01:32
created

test_logging_file()   B

Complexity

Conditions 4

Size

Total Lines 26

Duplication

Lines 26
Ratio 100 %

Importance

Changes 1
Bugs 0 Features 0
Metric Value
cc 4
c 1
b 0
f 0
dl 26
loc 26
rs 8.5806
1
import os
0 ignored issues
show
Coding Style introduced by
This module 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.

Loading history...
2
import sys
3
4
5
def _gw_logging_cfg(log_file):
6
    return {
7
        'version': 1,
8
        'disable_existing_loggers': False,
9
        'formatters': {
10
            'standard': {
11
                'format': "%(asctime)s - %(levelname)-5s - %(message)s"
12
            },
13
            'debug': {
14
                'format': "%(asctime)s - %(levelname)-5s - %(name)-40s - %(message)-80s - %(module)s:%("
0 ignored issues
show
Coding Style introduced by
This line is too long as per the coding-style (104/100).

This check looks for lines that are too long. You can specify the maximum line length.

Loading history...
15
                          "funcName)s(%(lineno)s)"
16
            },
17
        },
18
        'handlers': {
19
            'console_stdout': {
20
                'formatter': 'standard',
21
                'class': 'logging.StreamHandler',
22
                'stream': sys.stdout,
23
                'level': 'INFO'
24
            },
25
            'file': {
26
                "class": "logging.handlers.RotatingFileHandler",
27
                "formatter": "debug",
28
                "filename": log_file,
29
                "maxBytes": 1024000,
30
                "backupCount": 3,
31
                'level': 'INFO'
32
            },
33
        },
34
        'loggers': {
35
            '': {
36
                'handlers': ['console_stdout'],
37
                'level': 'INFO',
38
                'propagate': False
39
            },
40
            'groundwork': {
41
                'handlers': ['console_stdout', 'file'],
42
                'level': 'INFO',
43
                'propagate': False
44
            },
45
        }
46
    }
47
48
49 View Code Duplication
def test_logging_file(basicApp, tmpdir):
0 ignored issues
show
Coding Style Naming introduced by
The name basicApp does not conform to the argument naming conventions ((([a-z][a-z0-9_]{2,30})|(_[a-z0-9_]*))$).

This check looks for invalid names for a range of different identifiers.

You can set regular expressions to which the identifiers must conform if the defaults do not match your requirements.

If your project includes a Pylint configuration file, the settings contained in that file take precedence.

To find out more about Pylint, please refer to their site.

Loading history...
Duplication introduced by
This code seems to be duplicated in your project.
Loading history...
50
    """
51
    The test case sets up a Groundwork application with logging to file with log level ``INFO``.
52
    The application is then called to log a debug and an info message.
53
54
    The generated logfile is then parsed and asserted, that only the info message can be found,
55
    the debug message cannot.
56
    """
57
    log_file = os.path.join(str(tmpdir), "test.log")
58
    app = basicApp
59
    # set up logging in the config, with log level INFO
60
    app.config.set('GROUNDWORK_LOGGING', _gw_logging_cfg(log_file))
61
    app._configure_logging(app.config.get("GROUNDWORK_LOGGING"))
0 ignored issues
show
Coding Style Best Practice introduced by
It seems like _configure_logging was declared protected and should not be accessed from this context.

Prefixing a member variable _ is usually regarded as the equivalent of declaring it with protected visibility that exists in other languages. Consequentially, such a member should only be accessed from the same class or a child class:

class MyParent:
    def __init__(self):
        self._x = 1;
        self.y = 2;

class MyChild(MyParent):
    def some_method(self):
        return self._x    # Ok, since accessed from a child class

class AnotherClass:
    def some_method(self, instance_of_my_child):
        return instance_of_my_child._x   # Would be flagged as AnotherClass is not
                                         # a child class of MyParent
Loading history...
62
63
    debug_message = "This is a test debug message."
64
    info_message = "This is a test info message."
65
    app.log.debug(debug_message)
66
    app.log.info(info_message)
67
68
    # verify the contents of the log file
69
    with open(log_file) as lf:
0 ignored issues
show
Coding Style Naming introduced by
The name lf does not conform to the variable naming conventions ((([a-z][a-z0-9_]{2,30})|(_[a-z0-9_]*))$).

This check looks for invalid names for a range of different identifiers.

You can set regular expressions to which the identifiers must conform if the defaults do not match your requirements.

If your project includes a Pylint configuration file, the settings contained in that file take precedence.

To find out more about Pylint, please refer to their site.

Loading history...
70
        log = lf.read()
71
    # at log level INFO, the DEBUG message should not be there
72
    assert log.find(debug_message) == -1
73
    # the INFO message should be there
74
    assert log.find(info_message) > 0
75
76
77 View Code Duplication
def test_logging_console(basicApp, tmpdir, capsys):
0 ignored issues
show
Coding Style Naming introduced by
The name basicApp does not conform to the argument naming conventions ((([a-z][a-z0-9_]{2,30})|(_[a-z0-9_]*))$).

This check looks for invalid names for a range of different identifiers.

You can set regular expressions to which the identifiers must conform if the defaults do not match your requirements.

If your project includes a Pylint configuration file, the settings contained in that file take precedence.

To find out more about Pylint, please refer to their site.

Loading history...
Duplication introduced by
This code seems to be duplicated in your project.
Loading history...
78
    """
79
    The test case sets up a Groundwork application with logging to stdout with log level ``INFO``.
80
    The application is then called to log a debug and an info message.
81
82
    The captured stdout is then parsed and asserted, that only the info message can be found,
83
    the debug message cannot.
84
    """
85
    log_file = os.path.join(str(tmpdir), "test.log")
86
    app = basicApp
87
    # set up logging in the config, with log level INFO
88
    app.config.set('GROUNDWORK_LOGGING', _gw_logging_cfg(log_file))
89
    app._configure_logging(app.config.get("GROUNDWORK_LOGGING"))
0 ignored issues
show
Coding Style Best Practice introduced by
It seems like _configure_logging was declared protected and should not be accessed from this context.

Prefixing a member variable _ is usually regarded as the equivalent of declaring it with protected visibility that exists in other languages. Consequentially, such a member should only be accessed from the same class or a child class:

class MyParent:
    def __init__(self):
        self._x = 1;
        self.y = 2;

class MyChild(MyParent):
    def some_method(self):
        return self._x    # Ok, since accessed from a child class

class AnotherClass:
    def some_method(self, instance_of_my_child):
        return instance_of_my_child._x   # Would be flagged as AnotherClass is not
                                         # a child class of MyParent
Loading history...
90
91
    debug_message = "This is a test debug message."
92
    info_message = "This is a test info message."
93
    app.log.debug(debug_message)
94
    app.log.info(info_message)
95
96
    out, err = capsys.readouterr()
0 ignored issues
show
Unused Code introduced by
The variable err seems to be unused.
Loading history...
97
    # at log level INFO, the DEBUG message should not be there
98
    assert out.find(debug_message) == -1
99
    # the INFO message should be there
100
    assert out.find(info_message) > 0
101