Python Testing with Green

unittest.TestCase methods:

• self.fail(message)

Regarding Errors & Failures

• Where an error comes from
• How an error is presented in a test report
• Where a failure comes from
• How a failure is presented in a test report
• The difference between failures and errors

Skipped Tests

• What a skipped test looks like
• Some ways to skip a test

Please see the "Skipping Tests" lecture in the Intermediate section for more in-depth information on skipping tests.

Expected Failure

• What it means to have an expected failure
• How to mark a test as an expected failure

Quick review of ALL the concepts in the beginner section.

Did you learn the fundamentals?

How to specify specific and/or multiple test targets using Green.

How to get code coverage reports using Green.

How using your test as a design tool makes your test meaningful.

How writing a readable test makes your test meaningful.

How testing for one outcome makes your test meaningful.

How testing boundaries makes your test meaningful.

How testing the results of your code makes your test meaningful.

How isolating the unit you are testing makes your test meaningful.

How identifying the reason for your test makes your test meaningful.

Suggested ways to organize your unit test files, classes, and methods.

How (and when) to use test fixtures, class fixtures, and module fixtures.

unittest.TestCase methods:

• self.assertEqual(arg1, arg2, [message])
• self.assertNotEqual(arg1, arg2, [message])

unittest.TestCase methods:

• self.assertGreater(left, right, [message])
• self.assertGreaterEqual(left, right, [message])
• self.assertLess(left, right, [message])
• self.assertLessEqual(left, right, [message])

unittest.TestCase methods:

• self.assertIs(arg1, arg2, [message])
• self.assertIsNot(arg1, arg2, [message])
• self.assertIsNone(arg1, [message])
• self.assertIsNotNone(arg1, [message])

unittest.TestCase methods:

• self.assertIn(item, collection, [message])
• self.assertNotIn(item, collection, [message])

unittest.TestCase methods 

• self.assertIsInstance(obj, class, [message])
• self.assertNotIsInstance(obj, class, [message])

unittest.TestCase methods:

• self.assertRaises(exception, callable, [arg1, arg2, ...], [kwarg1=x, kwarg2=y, ...])
• self.assertRaisesRegexp(exception, pattern, callable, [arg1, arg2, ...], [kwarg1=x, kwarg2=y, ...])

unittest.TestCase methods:

• self.assertItemsEqual(collection1, collection2, [message])

unittest.TestCase methods:

• self.assertAlmostEqual(arg1, arg2, [places=7], [message], [delta])
• self.assertNotAlmostEqual(arg1, arg2, [places=7], [message], [delta])

unittest.TestCase methods:

• self.assertRegexpMatches(text, pattern, [message])
• self.assertNotRegexpMatches(text, pattern, [message])

A more in-depth look at ways to skip tests than the lecture in the beginner section:

• @unittest.skip(message)
• @unittest.skipIf(condition, message)
• @unittest.skipUnless(condition, message)
• self.skipTest(message)
• raise unittest.SkipTest(message)

In this section:

• Mock objects for unit tests
• Green's powerful features
• Integration Testing & Continuous Integration
• Tips & Tricks

Overview of mock module:

• Portable imports
• MagicMock: Introduction to calls, attributes, methods, return values, side effects, and patching.

The MagicMock object is vital to testing, unit testing especially.  In part 1 we begin our journey covering all the most commonly-used parts of the versatile MagicMock object.

PART TWO!!!  We bring it all in and learn all the rest that we need to know about the MagicMock...and a few other mock tidbits.

Learn how to patch your code to automatically replace real object with mocks and isolate the units you are testing.

Learn to use Green's powerful output options to customize your test reports.

How to initialize & finalize external resources (like databases) so that each worker process can have its own dedicated external resource and simultaneous tests don't interfere with each other.

Green uses multiple processes to run your tests in parallel by default.  Learn exactly how that works, and what you can do to customize it.  Run your tests FAST!

Green supports multiple config files to customize Green's behavior for your projects.

Green provides tab-completion of test targets for both bash and zsh!  Setup is quick and easy.

Sometimes you want a test run to stop after the first failure.

Learn the correct way to create and clean up temporary files & directories, plus tips & information about how Green's worker processes use temporary directories and how you can identify worker processes.