James Cooke jamescooke

## test_assert_q_equal.py
# encoding: utf-8

import pytest
from django.db.models import Q


def assert_q_equal(left, right):
    """
    Simply test two Q objects for equality. Does is not match commutative.

## test_assert_q_equal.py
# encoding: utf-8

from __future__ import unicode_literals

from django.db.models import Q
from django.test import TestCase

from .helpers import QTestMixin


## NOTES.rst

      
              5 files
            
          
              0 forks
            
          
                0 comments
              
            
              0 stars
            
          
                jamescooke
                / NOTES.rst
            
            
              Last active
              September 27, 2015 11:29
            
              
                PyConUK sprint on improving output from unittest when `assertEqual` finds non-matching values.
              
          
    Unittest documentation improvements

http://www.pyconuk.org/sprints/unit-test-documentation-improvements/
We explored where the "Expected: 1, actual: 2" messages (used to) come from in
unittest. We found that this code has already been improved back in 2011. Why
were we still getting old output for so long?
Below are links to our findings, plus you can see the test cases we built and
	# encoding: utf-8

	import pytest
	from django.db.models import Q


	def assert_q_equal(left, right):
	"""
	Simply test two Q objects for equality. Does is not match commutative.
	# encoding: utf-8

	from __future__ import unicode_literals

	from django.db.models import Q
	from django.test import TestCase

	from .helpers import QTestMixin