Introduction

Test Scripts can be executed directly via the external REST API, but they can also be stored on the Cuica for later use and to run as part of one or more Test Suites. The following limits apply to the Test Suite Bank:

• Maximum 16384 Bytes of Bytecode per Test Script (1500+ lines source)
• Maximum 300 Test Scripts in Bank

All operations can be done using either the web interface, the Cuica CLI app, or directly in the REST API. The related REST API endpoints can be found in the Fixture section of the OpenAPI spec and corresponding generated documentation.

Bypassing the Test Script Bank

It's also possible to bypass the Test Scripts Bank and directly import and run Test Scripts which can be useful for quick testing or when automation tools are external to the Cuica.

Example Test Scripts

To provide a starting point and to demonstrate functionality, reference Test Scripts are available in the Test Script editor dialog.

Adding Test Scripts

When adding a new Test Script, a label and version (optional) are provided and are then associated with that Test Script. An empty script may also be created for later editing using the web interface. As the Test Script is edited, replaced, or a new one uploaded, it is checked for syntax errors and converted to bytecode which is later used directly by the fixture.

Tagging Test Scripts

To facilitate grouping of Test Scripts and to more easily filter during DELETE and GET operations, the Test Scripts may be tagged with up to 20 different strings.

Replacing Test Scripts

To preserve the relationship between Test Suites and an instance of a Test Script the Test Script can be replaced or modified in-place. This makes it possible to use an existing Test Suite with different Test Scripts without having to rebuild the Test Suite.

Deleting Test Scripts

Test Scripts can be removed individually, by those matching a given tag, or all at once.