Attribute placed on a coded automation step in the code behind of a test.

Processes the execution of test (.aii) and test list (.aiilist).

The data context responsible for iteration the test. The ExecutionContext has a collection of DataContext for each test in the row (e.g. test as step, both tests data-bound.

Represents a data iteration result for data driven testing.

Debugging Options when debugging.

Command to execute a test

Provides the execution context of a specific test. (Test, step, settings, manager, data ..etc) You can use this class to get at information at any point in the execution flow of a testcase.

Contains all values returns from execution

Represents the mechanism to filter objects.

A filtered collection other objects can implement

All FindExpression updates

Manage communication inside the ArtOfTest.Runner.exe with the RunnerController.

Base for all runner commands

Command to report results

Simple summary of an execution of a .aii test.

Wraps .aii test execution so it can be called from third party apps.

Represents a collection of test results for a specific run.

Represents the collection of run results exposing filtering methods.

Represents the result of a test as step run.

Represents the collection of actual tests object along with custom logic to retrieve tests (filtering).

Class representing a test result.

Class contains all updates that occured to the test during execution.

All update info objects should inherit from this.

All Verification updates

Visual Debugger that handles UI display during execution and the Stop/Go/Auto-Pause aspect of execution. This object is exposed to users so they can call it from the code behind. Execution engine communicates directly with this object.

Implements an extension to the execution engine.

Possible options to auto pause execution

The different debugger modes

Serves as comparison types enum for filtering string type Test properties. Note: Shall we add a new item here a separate case needs to be implemented in the Match method.

Possible commands

The command line runner exit code. - '0' for processed run and tests success - '1' for processed run but some failed tests - more than 1 for other errors.