fix maven dependencies

pom.xml

@@ -28,9 +28,15 @@
         <dependency>
             <groupId>org.junit.jupiter</groupId>
             <artifactId>junit-jupiter-api</artifactId>
-            <version>5.11.2</version>
+            <version>5.11.3</version>
             <scope>compile</scope>
         </dependency>
+        <dependency>
+            <groupId>org.junit.jupiter</groupId>
+            <artifactId>junit-jupiter</artifactId>
+            <version>5.11.3</version>
+            <scope>test</scope>
+        </dependency>
     </dependencies>
 
     <build>
@@ -43,6 +49,14 @@
                     <release>8</release>
                 </configuration>
             </plugin>
+            <plugin>
+                <artifactId>maven-surefire-plugin</artifactId>
+                <version>3.3.1</version>
+            </plugin>
+            <plugin>
+                <artifactId>maven-failsafe-plugin</artifactId>
+                <version>3.3.1</version>
+            </plugin>
         </plugins>
     </build>
 

readme.md

@@ -5,7 +5,7 @@ What is it for?
 ---------------------
 There is a common anti-pattern in (unit) testing where we write a test that makes a large print-out of the test result -
 like a `.toString`, and `assertEquals` that to a print-out we have stored on disk. These tests are *great* because we
-can any little change to the test result!
+can see any little change to the test result!
 These tests are *terrible* because every little change to the test result will break the test, even if it was totally
 irrelevant to the test case.