From 304949b68c68559f39a7f0481fb6d9da2a34f26b Mon Sep 17 00:00:00 2001 From: Mark Pilgrim Date: Sat, 22 Aug 2009 12:37:38 -0400 Subject: [PATCH] typo --- unit-testing.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/unit-testing.html b/unit-testing.html index 1c679b5..507d1a0 100755 --- a/unit-testing.html +++ b/unit-testing.html @@ -468,13 +468,13 @@ OK
  • Oh, that’s even worse. Both of these cases should raise an exception. Instead, they give bogus results. -

    Testing for non-integers is not difficult. First, define a NonIntegerError exception. +

    Testing for non-integers is not difficult. First, define a NotIntegerError exception. 

    # roman4.py
 class OutOfRangeError(ValueError): pass
 class NotIntegerError(ValueError): pass
    -

    Next, write a test case that checks for the NonIntegerError exception. +

    Next, write a test case that checks for the NotIntegerError exception. 

    class ToRomanBadInput(unittest.TestCase):
     .