accelQ supports 2 types of Contexts, UI and Library contexts.
Represents a UI based Context in the application with related visual elements and user actions. This is the type of Context you would be choose when building test assets for a UI based application.
Represents a Stateless Context comprising of general purpose non-UI based Actions. When you work with API or back-end testing, you can create a Library Context and add Actions.
You select the type of Context when you create a Context. Once set, you cannot change the "type".
When to use Library Context
When you are working with Non-Web UI test scenarios such as API testing or database testing, you can use Library context to define Actions. When you develop scenarios with library contexts, it is not required to start with a browser initialization step. This avoids requirement to open a browser to start testing.
Note that a library context does not allow Views, and hence you cannot work with any UI interaction type of logic in their actions. However, actions in a UI Context do allow inserting API and other non-ui related statements in the action logic.