Commit 7457093
doc: improve .throws RegExp info
It was not clear why the error name is actually also tested for when
using a regular expression. This is now clarified.
Backport-PR-URL: #19230
PR-URL: #17585
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
Reviewed-By: Evan Lucas <evanlucas@me.com>1 parent 612ba1a commit 7457093
1 file changed
Lines changed: 4 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -738,12 +738,15 @@ assert.throws( | |||
| 738 | 738 | ||
| 739 | 739 | Validate error message using [`RegExp`][]: | |
| 740 | 740 | ||
| 741 | + Using a regular expression runs `.toString` on the error object, and will | ||
| 742 | + therefore also include the error name. | ||
| 743 | + | ||
| 741 | 744 | ```js | |
| 742 | 745 | assert.throws( | |
| 743 | 746 | () => { | |
| 744 | 747 | throw new Error('Wrong value'); | |
| 745 | 748 | }, | |
| 746 | - /value/ | ||
| 749 | + /^Error: Wrong value$/ | ||
| 747 | 750 | ); | |
| 748 | 751 | ``` | |
| 749 | 752 | ||
0 commit comments