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: sections/testing-perks/tests-as-documentation.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,4 +36,4 @@ Please, keep in mind that:
36
36
37
37
- UI tests are not the only ones: having more low-level tests for parts of the code that could be hard to be understood is a great way to describe the code expected behaviors.
38
38
39
-
- comments in the test could help a lot the reader, look at the ["Matching the test's code and test runner's commands" section of the "Keep abstraction low to ease debugging the tests" chapter](../../sections/generic-best-practices/test-code-with-debugging-in-mind.md#matching-the-tests-code-and-test-runners-commands)
39
+
- comments in the test could help a lot the reader, look at the ["Matching the test's code and test runner's commands" section of the "Keep abstraction low to ease debugging the tests" chapter](../generic-best-practices/test-code-with-debugging-in-mind.md#matching-the-tests-code-and-test-runners-commands).
0 commit comments