Changeset 32683

Timestamp:

2018-12-13T21:18:37+13:00 (5 years ago)

Author:

ak19

Message:

1. Rudimentary test class for running GLI with Assertj Swing. 2. Already accidentally prematurely committed major changes in revision 32680 to ext/testing/build.xml which starts using assertj-swing. I think it's now successfully launching GLI. The reason I may not be seeing GLI's GUI when testing may perhaps be since there are no actual tests yet other than to run and quit GLI. The changes to build.xml in this commit are cosmetic, but wanted a commit message explaining the new targets introduced in revision 32680, which were to compile up and build our tutorial testing classes. At present there's only one class which doesn't do much yet, as explained. But at least I got the ant target's classpath correct to get it compiled and for JUnit to start running the basic test class.

Location:

gs3-extensions/testing/trunk/src

Files:

• build.xml (modified) (2 diffs)
• src/gstests (added)
• src/gstests/tutorials (added)
• src/gstests/tutorials/RunGLITest.java (added)

gs3-extensions/testing/trunk/src/build.xml

@@ -1 +1 @@
 <?xml version="1.0"?>
 <project name="Greenstone3 Testing Extension" default="build-util-jar" basedir=".">
-  <!-- get properties from the environment -->
-  <property environment="env"/>
+  
+  <property environment="env"/> <!-- get properties from the environment -->
   <property name="compile.includeantruntime" value="false"/> <!-- to get rid of annoying 'ant' warning -->
 
@@ -101 +101 @@
 TODO: Launching GLI for GS2 is also different -->
 
+<!-- JUnit must run in GLI folder to mimic how GLI is run.
+     One reason why this is necessary is that GLI then won't display parsing issues with GLI class HelpFrame -->
 <!-- http://ant.1045680.n5.nabble.com/How-to-increase-memory-used-by-JVM-in-Ant-td1355370.html -->
 <target name="run-tutorials-tests" depends="needs-gs3-setup, needs-make-gli-jar">