Developer info and FAQ Frequently Asked Questions

What is the syntax for the TextScriptRunner Mini-Language?

What are some example scripts and outputs using the TextScriptRunner Mini-Language?

Why can't my script click on [whatever]?

Make sure you have spelled it correctly. If there are spaces in the name, make sure you enclose the argument in quotes.
Some items are case sensitive

I get an Error about 'Incorrect Argument Count' (e.g. Enter FieldName val1 val2 val3 only enters val1)

For arguments containing a space character, enclose the argument in quotes (e.g. Enter 'val1 val2 val3')

How do I report a bug?

Email support and include a copy of your script and screenshot of what happens when you run it. Let us know what you thought *should* happen when it runs

How do I request a new feature / enhancement / behavior change / mod?

Email support and include brief description of your request with a copy of a script that demonstrates the functionality you're interested in

How do I join the TextScriptRunner Team?

We aren't currently looking for new Team members, but if that changes we will be sure to post an update on the Home page

How to get the most out of textScriptRunner

Make your app testable:

Put a name and id on every element (where applicable). While you can try finding it by the text or crafting some XPATH, it's a lot easier to to add an id and/or name
JavaScript is flakey. Some implementations, and testing JS in general due to events and timing. Using getValue instead of getTextValue helps, especially for any calcs.

Why Users should write tests

Most developers don't like writing tests
Writing tests for your own app is likely to miss a lot
You'd get a lot more done/implemented if you spent more time coding and less time testing
Writing scripts for testing is a LOT faster than writing code for tests