You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: readme-zh-TW.md
+9-9Lines changed: 9 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -1578,32 +1578,32 @@ it("Test addNewOrder, don't use such test names", () => {
1578
1578
1579
1579
<br/><br/>
1580
1580
1581
-
## ⚪ ️4.4 Preventing test code issues with Test linters
1581
+
## ⚪ ️4.4 使用 Test linter 來避免測試程式的問題
1582
1582
1583
-
:white_check_mark:**Do:**A set of ESLint plugins were built specifically for inspecting the tests code patterns and discover issues. For example, [eslint-plugin-mocha](https://www.npmjs.com/package/eslint-plugin-mocha)will warn when a test is written at the global level (not a son of a describe() statement) or when tests are [skipped](https://mochajs.org/#inclusive-tests)which might lead to a false belief that all tests are passing. Similarly, [eslint-plugin-jest](https://github.com/jest-community/eslint-plugin-jest)can, for example, warn when a test has no assertions at all (not checking anything)
❌ **Otherwise:**Seeing 90% code coverage and 100% green tests will make your face wear a big smile only until you realize that many tests aren’t asserting for anything and many test suites were just skipped. Hopefully, you didn’t deploy anything based on this false observation
0 commit comments