Skip to content

Commit 3bae109

Browse files
Xronophobehjwp
andauthored
clarify wording of running the complete test suite before commit
Co-authored-by: Harry Percival <[email protected]>
1 parent 034c370 commit 3bae109

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

chapter_12_organising_test_files.asciidoc

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -381,9 +381,10 @@ AssertionError: write me!
381381
Brilliant--no need to sit around waiting for all the FTs
382382
when we're only interested in a single one.
383383
Although we need to remember to run all of them now and again, to check for regressions.
384-
It's a good habit to run all the tests before making a `git commit`.
385-
Later in the book we'll see how to give that task over to an automated Continuous Integration loop.
386-
For now, let's commit!
384+
Later in the book we'll set up a Continuous Integration (CI) server to run all the tests automatically,
385+
for example every time we push to master.
386+
For now, a good prompt for running all the tests is "just before you do a commit",
387+
so let's get into that habit now:
387388

388389
[subs="specialcharacters,quotes"]
389390
----

0 commit comments

Comments
 (0)