describe_help() - Code Metrics - Inspection of "Embed version and copywrite" - jacebrowning/verchew - Measure and Improve Code Quality continuously with Scrutinizer

Completed

Pull Request — develop (#8)

by Jace

created 2016-10-17 21:14 UTC

describe_help() A

↳ Parent: describe_cli()

Complexity

Conditions

Size

Total Lines

Duplication

Lines	0
Ratio	0 %

Importance

Changes

Metric	Value
cc	2
dl	0
loc	7
rs	9.4285
c	0
b	0
f	0

# pylint: disable=redefined-outer-name,unused-variable,expression-not-assigned

import os
import sys

import pytest
# .scrutinizer.yml
before_commands:
    - sudo pip install abc # Python2
    - sudo pip3 install abc # Python3
import scripttest
# .scrutinizer.yml
before_commands:
    - sudo pip install abc # Python2
    - sudo pip3 install abc # Python3
from expecter import expect
# .scrutinizer.yml
before_commands:
    - sudo pip install abc # Python2
    - sudo pip3 install abc # Python3
import six


@pytest.fixture
def env(tmpdir):
    path = str(tmpdir.join('test'))
    env = scripttest.TestFileEnvironment(path)
    return env


def cli(env, *args):
    prog = os.path.join(os.path.dirname(sys.executable), 'verchew')
    cmd = env.run(prog, *args, expect_error=True)
    six.print_(cmd)
    return cmd


def describe_cli():

    def it_displays_help_information(env):
        cmd = cli(env, '--help')

        expect(cmd.returncode) == 0
        expect(cmd.stdout).contains("usage: verchew")

    def it_displays_version_information(env):
        cmd = cli(env, '--version')

        expect(cmd.returncode) == 0
        expect(cmd.stderr).contains("verchew v0.")


Pull Request — develop (#8)

describe_help() A

Complexity

Size

Duplication

Importance

1. Missing Dependencies

2. Missing init.py files

1. Missing Dependencies

2. Missing init.py files

1. Missing Dependencies

2. Missing init.py files

1			# pylint: disable=redefined-outer-name,unused-variable,expression-not-assigned
2
3			import os
4			import sys
5
6			import pytest
			0 ignored issues – show Configuration introduced 2016-10-17 16:49 UTC by Report Bug Copy Issue Report The import `pytest` could not be resolved. This can be caused by one of the following: 1. Missing Dependencies This 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 files This error could also result from missing `__init__.py` files in your module folders. Make sure that you place one file in each sub-folder. Loading history...
7			import scripttest
			0 ignored issues – show Configuration introduced 2016-10-17 16:49 UTC by Report Bug Copy Issue Report The import `scripttest` could not be resolved. This can be caused by one of the following: 1. Missing Dependencies This 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 files This error could also result from missing `__init__.py` files in your module folders. Make sure that you place one file in each sub-folder. Loading history...
8			from expecter import expect
			0 ignored issues – show Configuration introduced 2016-10-17 16:49 UTC by Report Bug Copy Issue Report The import `expecter` could not be resolved. This can be caused by one of the following: 1. Missing Dependencies This 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 files This error could also result from missing `__init__.py` files in your module folders. Make sure that you place one file in each sub-folder. Loading history...
9			import six
10
11
12			@pytest.fixture
13			def env(tmpdir):
14			path = str(tmpdir.join('test'))
15			env = scripttest.TestFileEnvironment(path)
16			return env
17
18
19			def cli(env, *args):
20			prog = os.path.join(os.path.dirname(sys.executable), 'verchew')
21			cmd = env.run(prog, *args, expect_error=True)
22			six.print_(cmd)
23			return cmd
24
25
26			def describe_cli():
27
28			def it_displays_help_information(env):
29			cmd = cli(env, '--help')
30
31			expect(cmd.returncode) == 0
32			expect(cmd.stdout).contains("usage: verchew")
33
34			def it_displays_version_information(env):
35			cmd = cli(env, '--version')
36
37			expect(cmd.returncode) == 0
38			expect(cmd.stderr).contains("verchew v0.")
39

jacebrowning / verchew

Pull Request — develop (#8)

describe_help() A

Complexity

Size

Duplication

Importance

1. Missing Dependencies

2. Missing __init__.py files

1. Missing Dependencies

2. Missing __init__.py files

1. Missing Dependencies

2. Missing __init__.py files

Duplication Side-by-Side

Filter issues like

2. Missing init.py files

2. Missing init.py files

2. Missing init.py files