Skip to content

Commit 7729fb8

Browse files
Xronophobehjwp
andauthored
apply O'Reilly conventions, add missing word
Co-authored-by: Harry Percival <[email protected]>
1 parent 3bae109 commit 7729fb8

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

chapter_12_organising_test_files.asciidoc

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -568,8 +568,8 @@ saves you from having to use `def..():` and an indented block:
568568
5
569569
----
570570
571-
In our case, we're using it to transform a bit of code - that would otherwise be
572-
executed immediately - into a function that we can pass as an argument,
571+
In our case, we're using it to transform a bit of code--that would otherwise be
572+
executed immediately--into a function that we can pass as an argument,
573573
and that can be executed later, and multiple times:
574574
// CSANAD: I think it's easier to read like this.
575575
@@ -632,14 +632,14 @@ through what happened:
632632
<1> In our FT, we call our `self.wait_for` helper, where we pass
633633
the `lambda`-ified version of `assertEqual`.
634634

635-
<2> We go into `self.wait_for` in `base.py`,
635+
<2> We go into `self.wait_for` in _base.py_,
636636
where we're calling (and returning) `fn()`, which refers to the passed
637637
lambda function encapsulating our test assertion.
638638

639639
<3> To explain where the exception has actually come from,
640640
the traceback takes us back into _test_list_item_validation.py_
641641
and inside the body of the `lambda` function,
642-
and tells us that the attempt to find the `.invalid-feedback` element
642+
and tells us that it was attempt to find the `.invalid-feedback` element
643643
that failed.
644644
// CSANAD: I changed two things here:
645645
// First, I think it's better to remove the specific line number which may

0 commit comments

Comments
 (0)