daily-email: add 2023-08-30
TDD and Unexpected errors
This commit is contained in:
parent
dcb1fe33a5
commit
1e3ece300a
22
src/content/daily-email/2023-08-30.md
Normal file
22
src/content/daily-email/2023-08-30.md
Normal file
|
@ -0,0 +1,22 @@
|
||||||
|
---
|
||||||
|
title: >
|
||||||
|
TDD and "Unexpected errors"
|
||||||
|
pubDate: 2023-08-30
|
||||||
|
permalink: >
|
||||||
|
archive/2023/08/30/tdd-and-unexpected-errors
|
||||||
|
tags:
|
||||||
|
- automated-testing
|
||||||
|
- test-driven-development
|
||||||
|
---
|
||||||
|
|
||||||
|
When working on projects, it's common to see messages like "The website encountered an unexpected error. Please try again later.".
|
||||||
|
|
||||||
|
Usually, this is the message shown to the user, whilst a more detailed error message is logged for Developers to diagnose and fix the underlying error.
|
||||||
|
|
||||||
|
The wording "unexpected error" has been intriguing to me, though. When do you expect an error?
|
||||||
|
|
||||||
|
The best example I can think of for an expected error is when doing test-driven development.
|
||||||
|
|
||||||
|
When doing TDD, you want to see an error to start as you start with a failing test.
|
||||||
|
|
||||||
|
Then, you write the code to remove the error and get the test passing.
|
Loading…
Reference in a new issue