Oracle’s OpenScript is a scripting platform for creating automated test scripts to be used with the Oracle Application Test Suite (OATS).
OpenScript provides an Eclipse-based environment for both developers and non-developers, and provides many facilities to ease the development of automated test scripts. The test scripts are constructed using the Java language and importantly they’re extendible, and can make use of any Java API.
OpenScript provides many features to enable the user to construct test scripts with ease. As with most testing tools OpenScript provides a standard set of capability such as automatic/manual screen shots, correlation libraries, proxy settings, data banking and so forth. Some of the main features of OpenScript are covered below..
OpenScript allows the user to record all interaction with a web application, using the native browser (both IE and Firefox), and will generate the Java code automatically. Once the recording is completed, users can playback the script, which will invoke the native browser and playback all user interactions. While recording, users can insert different kinds of tests, from text matching tests, to object attribute tests, and then continue with normal interaction. All steps within the user journey are shown in the tree view (see Figure 1).
Once the scripts have been recorded, users can switch to the Java view to examine the actual Java code, add comments, and add functionality that may not be available in record mode, for example checking something in the application environment, or adding classes to support more esoteric environments, such as telnet. This, and other features, like debugging, are helpfully contained within the Eclipse integrated development environment.
Once the test scripts have been developed, they can be managed by the Oracle Test Manager (OTM), and if the scripts are for load testing, they can be accessed directly by the Oracle Load Test tool (OTL).
OpenScript provides a Java API. There are utility classes for performing usual testing tasks without getting bogged down into (sometimes) complicated Java code. For example, reading/writing to files, reading .csv files an so on. But OpenScript also allows developers to write/employ classes specific to their environment. And the user has access to all standard Java APIs.
The OpenScript preferences section allows the user to configure how the script will execute, as well as what do in a variety of conditions. For instance, whether a script should fail, or whether it should just warn a user that a particular step has not executed as expected.
OpenScript supports the notion of modules. Modules currently supported are Web, Oracle Forms Applications, Oracle ADF applications, Web Services, Siebel Applications, (and soon Flex) and because OpenScript use Java as its platform, can support anything that has a Java API associated with it. Other features such as running the scripts from the command line are also supported.