9.2.4 Automation Languages: Scripts, Script Language
"Scripts and script languages are sometimes used to better implement and expand the test conditions and test cases."
"For example when testing a web application, a script might be used to bypass the user interface to more adequately test the API (application programming interface) itself."
Whether a tool drives the SUT via the GUI or an API is a property of the tool interface, not the script language.
"Another example would be the case where the testing of a user interface is automated to allow all possible combinations of inputs which would be infeasible with manual testing."
Another example of what?
Why restrict this to the UI? Applicable to all testing.
Not likely to be able to test ALL POSSIBLE inputs with a tool either. An infinite set? Not likely.
Infeasible has a specific meaning with respect to paths. Impractial or uneconomic would be better.
"The capability of scripting languages varies widely. Note that scripting languages can range from normal programming languages, to very specific standard notations, e.g. signaling for protocols like TTCN-3."
TTCN-3 is a a non-proprietary notation for defining tests, which can be used for automation. See http://www.ttcn-3.org/Howisdiff.htm "TTCN-3 as such is not executable and requires a compiler/interpreter, adapter as well as codec implementations". Is TTCN-3 'extra capable' or incapable on in some range? What is meant by 'can range'???