Create test scripts using e-Tester without using visual scripts

Question

I'm new researching on e-Test suite.
I have the following question. Is there any possibility to create test scripts to run automatic tests without using the visual scripts created by e-Tester?
Today, we are using Selenium to make Web based tests and this tool is included in a custom framework developed in Java. So, we don't use record and play. Directly we create code using objects, methods and attributes provided by Selenium api.

Answer 1

You can create a dummy java agent script that can that call your module. The java agent script can then be automated to run in e-Load.
1) e-tester menu ->options->New Scripts (global) -> Advanced -> Java Agent: Check on "Create Java Agent Script.." and the other 2 check boxes.
2) menu -> File -> New Script
3) Do Nothing. No navigations, ect...
4) menu -> File -> Save Script i.e. "empty"
5) Download and install Eclipse IDE (other IDEs should work but you need to create your own project)
6) Eclipse -> Menu -> File -> Import -> General -> Existing Project into workspace: Select the root directory that contains the etester generated Java Agent script prefixed with the underscore "_" i.e c:\ETS\etest\Default!\_empty
7) Once imported I suggest you call your module from within scriptCallback.class EndScript(RunState, ScriptResult);
7b) When you get better at this you can return errors by changing the ScriptResult() object and view stats from the RunState() object.
8) You will have to modify the Eclipse Project to be dependent on your jars if you want to debug in eclipse. Secondly there are 2 batch files. These two batch files create the *.JWG file which is just a renamed .JAR file.
9) You MUST modify the batch files to create the new Empty.JWG including your *.JAR files.
10) I recommend compiling in eclispe and only running the makefileNocompile.bat (after you add the *.jar inclusion). Ignore the makefile.bat unless you also change the javac.exe execution line to include all the correct classpaths.
11) Once you are happy with running in Eclipse you should be able to execute in eload. I recommend you test the procedures steps 5 through 10 before adding your own module and code.