From e9a360d5a2c59a6ef55cd0614034ec9b7df19985 Mon Sep 17 00:00:00 2001 From: Gintas Grigelionis Date: Mon, 12 Mar 2018 19:57:10 +0100 Subject: [PATCH] More adjustments --- manual/tutorial-HelloWorldWithAnt.html | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/manual/tutorial-HelloWorldWithAnt.html b/manual/tutorial-HelloWorldWithAnt.html index 5b02d6a67..5d1f306ae 100644 --- a/manual/tutorial-HelloWorldWithAnt.html +++ b/manual/tutorial-HelloWorldWithAnt.html @@ -361,7 +361,8 @@ start the application from that directory and these files will included into the

Testing the class

In this step we will introduce the usage of the JUnit [3] test framework in combination with Ant. Because Ant has a -built-in JUnit 4.12 you could start directly using it. Write a test class in src\HelloWorldTest.java:

+built-in JUnit 4.12 you could start directly using it. Write a test class +in src\oata\HelloWorldTest.java:

 package oata;
@@ -383,9 +384,9 @@ public class HelloWorldTest {
 
 }
-

Because we don't have real business logic to test, this test class is very small: just show how to start. For further -information see the JUnit documentation [3] and the manual of junit task. Now we add a -junit instruction to our buildfile:

+

Because we don't have real business logic to test, this test class is very small: just showing how to start. For +further information see the JUnit documentation [3] and the manual of junit task. Now we +add a junitcode> instruction to our buildfile:

     ...
@@ -434,7 +435,7 @@ junit:
 BUILD SUCCESSFUL
 ...
-

We can also produce a report. Something that you (and others) could read after closing the shell .... There are two +

We can also produce a report. Something that you (and others) could read after closing the shell ... There are two steps: 1. let <junit> log the information and 2. convert these log files to something readable (browsable).