From 054ba4c3ba4fd501129f203a22d7431cb55e465b Mon Sep 17 00:00:00 2001 From: Corey McCandless Date: Thu, 29 Nov 2018 09:42:58 -0500 Subject: [PATCH] README: add convention for exception messages (#1600) This has been established for a while now, but was never officially added as a track convention. --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 860db23e..81bb5a06 100644 --- a/README.md +++ b/README.md @@ -23,6 +23,7 @@ A list of missing exercise can be found here: https://github.com/exercism/python - We use `unittest` (Python Standard Library) and no 3rd-party-framework. - We use the parameter order `self.assertEqual(actual, expected)` ([#440](https://github.com/exercism/python/issues/440)). - We use context managers (`with self.assertRaises(\):`) for testing for exceptions ([#477](https://github.com/exercism/python/issues/477)). +- We use an established utility method to confirm that expected exceptions contain a non-empty message. This method must be included for any test class with an exception-based test case ([#1080](https://github.com/exercism/python/issues/1080#issuecomment-442068539)). - We use `assertIs(actual, True)` and `assertIs(actual, False)` rather than `assertTrue(actual)` or `assertFalse(actual)` ([#419](https://github.com/exercism/python/pull/419)). - We use a comment string in the test file to reference the version of the exercise's `canonical-data.json` that tests were adapted from (wording can be found in: [#784](https://github.com/exercism/python/issues/784)).