Commit 6f81b27
doc: fix typo in writing-test.md
Corrects the misspelling of "optimial" to "optimal".
PR-URL: #59123
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
Reviewed-By: Darshan Sen <raisinten@gmail.com>
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Ulises Gascón <ulisesgascongonzalez@gmail.com>1 parent 88e434e commit 6f81b27
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -24,7 +24,7 @@ See [directory structure overview][] for outline of existing test and locations. | |||
| 24 | 24 | ||
| 25 | 25 | ## How to write a good test | |
| 26 | 26 | ||
| 27 | - A good test should be written in a style that is optimial for debugging | ||
| 27 | + A good test should be written in a style that is optimal for debugging | ||
| 28 | 28 | when it fails. | |
| 29 | 29 | ||
| 30 | 30 | In principle, when adding a new test, it should be placed in a new file. | |
0 commit comments