accelQ creates and manages test assets in a well structured, modular fashion with an objective to create a sustainable test automation suite. Various entities serve as building blocks and interact with each other providing a level of abstraction necessary to create a maintainable test asset.
Following diagram identifies important entities in accelQ and how they are related to each other. This article provides a brief definition of important components in this diagram. Further details can be found in sections throughout this guide.
Context is like a page in the application-under-test. Every distinct page in the application becomes a Context in accelQ.
Context refers to a 'state' of the application-under-test (AUT), where a set of user actions are possible. In a typical web application, you can consider each distinct page of the application to be a Context. Examples include Home Page, Purchase Page etc.
Context manages the Views (like screenshots of your application) and Elements relevant for your test logic.
Action is a meaningful functionality that a user can perform in one given page (context). Action includes logic to interact with browser or perform validations.
Examples: Search for Flights, Navigate to Home Page, Verify Purchase Order etc.
Action belongs to a Context and makes use of element from the Context's repository.
Scenario represents a use case or a test script on your application. It includes multiple steps going across different pages of your application. Each step in the Scenario is an Action from one of the pages in the application.
Scenario represents a use case on the test application (AUT), which can be “run” as a test.
A Scenario may yield multiple test cases, with each test case representing one set of data inputs required to perform the steps in the Scenario.
Test Case is an iteration of a Scenario that comprises the data to be used for that iteration. Each Scenario may have multiple test cases with different combinations of test data. When you run a Scenario which has multiple test cases, this same Scenario is repeatedly executed, once per each test case. It is similar to the typical data driven testing concept in testing.
Test Suite is a collection of Scenarios grouped together for execution. A suite can be created either based on metadata filters (custom fields), User Stories or as a static set of Scenarios. You typically manage the execution requirement in a Sprint or a Release through a Suite.