What is the difference between a Context and an Action?

A Context represents a page and owns its elements. An Action is a user-level function on that page, such as searching or verifying, and uses the Context's elements.

Why share elements across Actions?

If a control changes, you update it once in the Context and every Action that uses it picks up the change.

ACCELQ Application Universe: Contexts, Views, and Elements

Introduction

Everything you automate in ACCELQ starts with a model of the application. The Application Universe is a visual map of that model, and Contexts and Elements are the parts it is made from. A clean model makes every later test easier to build and maintain.

Prerequisites

The ACCELQ introduction lesson
A web application you can use for practice

Step-by-Step Guide

Step 1: Read the Application Universe

The Universe is a visual map of your application and how your test assets relate. In the map, circles represent Contexts and the lines between them represent Actions that move from one context to another. A sidebar lists Scenarios, and selecting one highlights the path it takes through the application.

Step 2: Create a Context for each page

A Context stands for a page or screen. It manages the Views, which are screenshots of the page, and the Elements used in your test logic. Name contexts after the page's purpose, for example Login, Search Results, or Checkout.

Step 3: Capture and name Elements

Elements are the controls on the page that your tests interact with. They belong to the Context and are shared by all Actions on that page. Give them business-friendly names, such as Username or Place Order, so tests read clearly and are easy to review.

Step 4: Keep identification stable

Prefer element identification that survives UI changes, and review elements after each application release. ACCELQ describes AI-based element identification and self-healing to reduce maintenance, but you should still verify behavior on your own application rather than assume it.

Step 5: Organize as the application grows

Keep one Context per page and avoid duplicating elements across Contexts. Use consistent naming conventions across the team, and remove unused elements so the Universe stays an accurate picture of the application.

FAQs

What is the difference between a Context and an Action?: A Context represents a page and owns its elements. An Action is a user-level function on that page, such as searching or verifying, and uses the Context's elements.
Why share elements across Actions?: If a control changes, you update it once in the Context and every Action that uses it picks up the change.

Summary

Model the application as Contexts with named Elements, and use the Universe to see how pages and Scenarios connect. A tidy model is the foundation for reusable Actions and low-maintenance tests.