NOTE: This feature has been disabled as of Jameleon-3.3-M5.
This section explains how to use the provided GUI to generate action point code. Currently, only jiffie tags are generated. However, all that is required to generate other web plug-in java code is to provide a template.
This feature can save a lot of time and can help make your scripts more readable. If you haven't already, please read the Introduction Section in the main Jameleon documentation on how to start the GUI.
To start the action point generator, first start the GUI. Then click on the button with gears on it:
Once you click on the above marked button, enter the displayed URL and press enter, you should be presented with the following screen:
The table below the URL is used for defining variable names, descriptions and other information that will be included in the custom tag. Please be sure to fill the empty fields out to make it easy for others that may end up using the tag(s). The field name is the actual name of the form field. This should be left alone. The variable name entry represents the attribute names that will be available for the tag. If the variable name is not provided, then the field name will be used.
This feature can be used to generate all action points of the application, one after another. Once IE is opened, you can browser to where you like and the GUI will keep track of how many forms are on each page. To get to the point of where IE is below, I started IE on freshmeat.net's homepage, then clicked on the login link. I then selected the third form and the GUI highlighted the form that I selected.
There are a few known issues with the action point generator:
Once the desired form is selected and the information in the table is filled out, press the "Generate Action Point" button. The following window should appear:
The following table attempts to explain what the fields mean:
|package||The field is used to organize your tags. It is a dot-separted path. The suggest package use would be for the first directory to be the name of the application. The second directory should then the be the functional area. So for our example freshmeat.net example a possible package name would be fm.logon. I shortened freshmeat to fm. The only reason to create a separate package for each functional area is it helps organize them so later when you have several custom tags, it won't be hard to find them. If you are going to use the provided validation tags.|
|Source Directory||If you downloaded the jameleon-test-suite package, then this field should be filled out for you. There is a setting for this in the GUI configuration file. This represents the base directory where the file will be saved to. In the above example, it would be saved to src/java/fm/logon.|
|Class Name||This field is the name of the actual class name minus the .java ending. It is recommended that all tags end with Tag. For our above example, we used FMLogonTag.|
|Tag Name||This is the name of the tag that will be used in the test script. Remeber that all tag names must be unique. It is recommended that the tag be prefixed with the name of the application. I chose fm-logon.|
Please be sure to not include any Java keywords in your package name. For example, public is a Java keyword. If your package name has public in it, then the will likely not compile.
Now to finally generate the code, press the Generate Code button. The file will be saved to the source directory entered in above.