From 4fb940313f0e51199056603fd5708988584e1863 Mon Sep 17 00:00:00 2001 From: wainstead Date: Sat, 22 Dec 2001 17:12:51 +0000 Subject: [PATCH] Reordered the two page tutorial so it makes more sense in the context of a README. git-svn-id: svn://svn.code.sf.net/p/phpwiki/code/trunk@880 96ab9672-09ca-45d6-a79d-3d69d39ca109 --- tests/README | 50 ++++++++++++++++++++++++++------------------------ 1 file changed, 26 insertions(+), 24 deletions(-) diff --git a/tests/README b/tests/README index 475360907..e9685555c 100644 --- a/tests/README +++ b/tests/README @@ -1,4 +1,4 @@ -$Id: README,v 1.1 2001-12-22 16:52:15 wainstead Exp $ +$Id: README,v 1.2 2001-12-22 17:12:51 wainstead Exp $ (This is just a set of entries from my work log when I was at Capital Thinking. It was then copy/pasted into their Wiki (they used PyWiki) as a little tutorial on how to use it. All of the basic information is @@ -24,6 +24,30 @@ How to make a test suite: * run ant +-------------- +Short Tutorial + +The GuiTester is a small simple system to test the GUI of the BlueWire system. + +As a programmer you have to do these steps: + + 1. Write a little input script. Let's call it MyTest.inputs. + 2. Create a Java source file with your input script, with a Perl script called maketest.pl. Run this command: '''maketest.pl MyTest.inputs'''. This will create a file called MyTest.java. + 3. Compile your file: '''javac MyTest.java''' + 4. Run your test: '''java MyTest''' + +That's the short form for writing your own single test. You can accumulate tests in a single directory, and via the magical tools "make" and Ant, run a whole set of tests. + + 1. Write one or more input scripts. + 1. run '''makemakebuild.pl'''. This script gets the names of all .input files in the current directory and generates a Makefile and a build.xml file. + 1. Run ant with no arguments, i.e. just type "ant" and hit return. + +That's all. All the Java files will be generated for you, compiled, and ran against BlueWire. + + +----------------- +A Longer Tutorial + An input script, which follows the naming convention ClassName.inputs, consists of a set of little statement blocks. Here is a sample which handles logging in to the system: @@ -101,7 +125,7 @@ with a hash sign (#) at the start of a line: # I am a comment. ------ +oo----- '''Types of statement blocks''' There are only four kinds of statement blocks in GuiTester: @@ -175,25 +199,3 @@ always use double quotes for the arguments, separated by a comma: - - -The GuiTester is a small simple system to test the GUI of the BlueWire system. - -As a programmer you have to do these steps: - - 1. Write a little input script. Let's call it MyTest.inputs. - 2. Create a Java source file with your input script, with a Perl script called maketest.pl. Run this command: '''maketest.pl MyTest.inputs'''. This will create a file called MyTest.java. - 3. Compile your file: '''javac MyTest.java''' - 4. Run your test: '''java MyTest''' - -That's the short form for writing your own single test. You can accumulate tests in a single directory, and via the magical tools "make" and Ant, run a whole set of tests. - - 1. Write one or more input scripts. - 1. run '''makemakebuild.pl'''. This script gets the names of all .input files in the current directory and generates a Makefile and a build.xml file. - 1. Run ant with no arguments, i.e. just type "ant" and hit return. - -That's all. All the Java files will be generated for you, compiled, and ran against BlueWire. - -Here's a more in-depth tutorial: GuiTesterTutorialOne - -CategoryGuiTester \ No newline at end of file -- 2.45.0