Differences between Testframe and Scriptframe
What are the key differences between the Scriptframe introduced in V3.5 and the earlier Testframe?
The Scriptframe was introduced in response to customer demand for a more flexible testing solution and addresses the following key points:
- Test Composition (Cross-Service Testing): The Scriptframe allows invocations on services to be combined to form more complex testing scenarios i.e. it allows the response from previous invocations to be used to drive subsequent ones. In comparison, the Testframe supported only a single request/response invocation model.
- Data Assertions: The Testframe will validate a response against a WSDL/Schema definition and can perform a diff against a reference response but customers requested a more fine-grained model for checking response data. The use of assertions, in combination with JavaScript allows very sophisticated data checks or policies to be enforced.
- Running tests against different target endpoints: A typical testing requirement is the ability to take a set of tests, which have been scripted against a development endpoint, and 're-target' them on a UAT or production environment. Whereas the Testframe relied on static WSDL endpoint data, the Scriptframe can avail of customizable properties to instantly and dynamically change test endpoints. These properties can also be used to share common test data across scripts.
- Customizable Reports: The Testframe allowed a basic set of test data to be exported as CSV. The Scriptframe supports creation of CSV and HTML using cusomizable stylesheets. In addition the ability to write log properties from within a script allows key test result data to be added to a report.
If you require information or support regarding particular schema constructs then please let us know.