test_valid_pipeline() - Code Metrics - Inspection of "[WIP] Version 2.0" - sunscrapers/djoser - Measure and Improve Code Quality continuously with Scrutinizer

Passed

Pull Request — master (#259)

by Piotr

created 2018-01-15 18:27 UTC

test_valid_pipeline() B

↳ Parent: Project

Complexity

Conditions

Size

Total Lines

Duplication

Lines	21
Ratio	100 %

Importance

Changes	7
Bugs	0	Features	0

Metric	Value
cc	5
c	7
b	0
f	0
dl	21
loc	21
rs	8.439

import pytest
class SomeClass:
    def some_method(self):
        """Do x and return foo."""

from django.contrib.auth import get_user_model


from djoser import pipelines, signals
from tests.common import catch_signal, mock

User = get_user_model()



@pytest.mark.django_db(transaction=False)
def test_valid_serialize_request(test_user):
class SomeClass:
    def some_method(self):
        """Do x and return foo."""
    request = mock.MagicMock()
    request.user = test_user
    request.data = {'email': 'new@localhost'}
    result = pipelines.user_update.serialize_request(request, {})

    assert 'serializer' in result
    assert result['serializer'].validated_data == request.data


@pytest.mark.django_db(transaction=False)
def test_valid_perform(test_user):
class SomeClass:
    def some_method(self):
        """Do x and return foo."""
    request = mock.MagicMock()
    request.user = test_user
    old_email = test_user.email

    serializer = mock.MagicMock()
    serializer.validated_data = {'email': 'new@localhost'}
    context = {'serializer': serializer}
    result = pipelines.user_update.perform(request, context)

    assert 'user' in result
    assert result['user'].username == test_user.username
    assert result['user'].email == serializer.validated_data['email']
    assert result['user'].email != old_email
    assert test_user.email == serializer.validated_data['email']


def test_valid_signal(test_user):
class SomeClass:
    def some_method(self):
        """Do x and return foo."""
    request = mock.MagicMock()
    context = {'user': test_user}

    with catch_signal(signals.user_updated) as handler:
        pipelines.user_update.signal(request, context)

    handler.assert_called_once_with(
        sender=mock.ANY,
        signal=signals.user_updated,
        user=test_user,
        request=request
    )


@pytest.mark.django_db(transaction=False)
def test_valid_serialize_instance(test_user):
class SomeClass:
    def some_method(self):
        """Do x and return foo."""
    context = {'user': test_user}
    result = pipelines.user_update.serialize_instance(None, context)
    username = getattr(test_user, User.USERNAME_FIELD)

    assert 'response_data' in result
    assert result['response_data'] == {
        'id': 1,
        'email': test_user.email,
        User.USERNAME_FIELD: username,
    }


@pytest.mark.django_db(transaction=False)

def test_valid_pipeline(test_user):
class SomeClass:
    def some_method(self):
        """Do x and return foo."""
    request = mock.MagicMock()
    request.user = test_user
    request.data = {'email': 'new@localhost'}
    username = getattr(test_user, User.USERNAME_FIELD)

    pipeline = pipelines.user_update.Pipeline(request)
    with catch_signal(signals.user_updated) as handler:
        result = pipeline.run()

    handler.assert_called_once_with(
        sender=mock.ANY,
        signal=signals.user_updated,
        user=result['user'],
        request=request
    )

    assert test_user.email == request.data['email']
    assert 'response_data' in result
    assert result['response_data'] == {
        'id': 1,
        'email': test_user.email,
        User.USERNAME_FIELD: username,
    }


# TODO: test errors, test FK, test m2m



1		import pytest
		0 ignored issues – show Coding Style introduced 2018-01-15 18:28 UTC by Report Bug Copy Issue Report 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... introduced 2018-01-15 18:28 UTC by Report Bug Copy Issue Report Unable to import 'pytest' Loading history...
2
3		from django.contrib.auth import get_user_model
		0 ignored issues – show introduced 2018-01-15 18:28 UTC by Report Bug Copy Issue Report Unable to import 'django.contrib.auth' Loading history...
4
5		from djoser import pipelines, signals
6		from tests.common import catch_signal, mock
7
8		User = get_user_model()
		0 ignored issues – show Coding Style Naming introduced 2018-01-15 18:28 UTC by Report Bug Copy Issue Report The name `User` does not conform to the constant naming conventions (`(([A-Z_][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...
9
10
11		@pytest.mark.django_db(transaction=False)
12		def test_valid_serialize_request(test_user):
		0 ignored issues – show Coding Style introduced 2018-01-15 18:28 UTC by Report Bug Copy Issue Report 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. Loading history...
13		request = mock.MagicMock()
14		request.user = test_user
15		request.data = {'email': 'new@localhost'}
16		result = pipelines.user_update.serialize_request(request, {})
17
18		assert 'serializer' in result
19		assert result['serializer'].validated_data == request.data
20
21
22		@pytest.mark.django_db(transaction=False)
23		def test_valid_perform(test_user):
		0 ignored issues – show Coding Style introduced 2018-01-15 18:28 UTC by Report Bug Copy Issue Report 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. Loading history...
24		request = mock.MagicMock()
25		request.user = test_user
26		old_email = test_user.email
27
28		serializer = mock.MagicMock()
29		serializer.validated_data = {'email': 'new@localhost'}
30		context = {'serializer': serializer}
31		result = pipelines.user_update.perform(request, context)
32
33		assert 'user' in result
34		assert result['user'].username == test_user.username
35		assert result['user'].email == serializer.validated_data['email']
36		assert result['user'].email != old_email
37		assert test_user.email == serializer.validated_data['email']
38
39
40		def test_valid_signal(test_user):
		0 ignored issues – show Coding Style introduced 2018-01-15 18:28 UTC by Report Bug Copy Issue Report 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. Loading history...
41		request = mock.MagicMock()
42		context = {'user': test_user}
43
44		with catch_signal(signals.user_updated) as handler:
45		pipelines.user_update.signal(request, context)
46
47		handler.assert_called_once_with(
48		sender=mock.ANY,
49		signal=signals.user_updated,
50		user=test_user,
51		request=request
52		)
53
54
55		@pytest.mark.django_db(transaction=False)
56		def test_valid_serialize_instance(test_user):
		0 ignored issues – show Coding Style introduced 2018-01-15 18:28 UTC by Report Bug Copy Issue Report 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. Loading history...
57		context = {'user': test_user}
58		result = pipelines.user_update.serialize_instance(None, context)
59		username = getattr(test_user, User.USERNAME_FIELD)
60
61		assert 'response_data' in result
62		assert result['response_data'] == {
63		'id': 1,
64		'email': test_user.email,
65		User.USERNAME_FIELD: username,
66		}
67
68
69	View Code Duplication	@pytest.mark.django_db(transaction=False)
		0 ignored issues – show Duplication introduced 2018-01-15 18:28 UTC by Report Bug Copy Issue Report This code seems to be duplicated in your project. Loading history...
70		def test_valid_pipeline(test_user):
		0 ignored issues – show Coding Style introduced 2018-01-15 18:28 UTC by Report Bug Copy Issue Report 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. Loading history...
71		request = mock.MagicMock()
72		request.user = test_user
73		request.data = {'email': 'new@localhost'}
74		username = getattr(test_user, User.USERNAME_FIELD)
75
76		pipeline = pipelines.user_update.Pipeline(request)
77		with catch_signal(signals.user_updated) as handler:
78		result = pipeline.run()
79
80		handler.assert_called_once_with(
81		sender=mock.ANY,
82		signal=signals.user_updated,
83		user=result['user'],
84		request=request
85		)
86
87		assert test_user.email == request.data['email']
88		assert 'response_data' in result
89		assert result['response_data'] == {
90		'id': 1,
91		'email': test_user.email,
92		User.USERNAME_FIELD: username,
93		}
94
95
96		# TODO: test errors, test FK, test m2m
		0 ignored issues – show Coding Style introduced 2018-01-15 18:28 UTC by Report Bug Copy Issue Report `TODO` and `FIXME` comments should generally be avoided. Loading history...
97

sunscrapers / djoser

Pull Request — master (#259)

test_valid_pipeline() B

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like