Chapter 10. Error Handling
What error drives our eyes and ears amiss?
William Shakespeare (through the tongue of Antipholus of Syracuse), The Comedy of Errors
Mistakes are a part of life. One of the reasons for adopting test-driven development is to ensure that we can go as fast as we safely can, minimizing bugs in code.
The next item on our feature list is to improve error handling:
5 USD × 2 = 10 USD |
10 EUR × 2 = 20 EUR |
4002 KRW / 4 = 1000.5 KRW |
5 USD + 10 USD = 15 USD |
Separate test code from production code |
Remove redundant tests |
5 USD + 10 EUR = 17 USD |
1 USD + 1100 KRW = 2200 KRW# |
Determine exchange rate based on the currencies involved (from → to) |
Improve error handling when exchange rates are unspecified |
Allow exchange rates to be modified |
Error Wish List
The way our code currently handles missing exchange rates is buggy. Let’s address this shortcoming. Table 10-1 shows our wish list for handling errors due to missing exchange rates.
| Item | Description |
|---|---|
1 |
The |
2 |
The error message should be “greedy”—that is, it should indicate all the missing exchange rates that prevent a |
3 |
To prevent the error from being ignored by the caller, no valid |
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access