Understanding the Hierarchical Relationship Between Projects, Goals, Journeys, and Checkpoints

Article Overview:

This article will cover how you can achieve the following:

Guide on the hierarchical relationship between projects, goals, journeys, and checkpoints in the context of managing testing frameworks.

Description:

The purpose of this article is to:

• Establish a clear hierarchy of projects, goals, journeys, and checkpoints.
• Clarify the interconnections and relative importance of each component.

Solution:

Virtuoso provides a structured hierarchy to organise tests.

Below is an illustration showing the hierarchical relationship between:

• Projects
• Goals
• Journeys
• Checkpoints (and Library Checkpoints)

This helps in understanding how these components are interconnected.

Hierarchical Structure

Organization:

• Organization is a tenant space that a customer has to create and manage the testing portfolio for an account.
• It represents the highest level within Virtuoso, containing multiple projects.

Project:

• Project is a container for all test sets (goals) and tests (journeys).
• Each project has its dedicated dashboard and access control.
• Projects can be organized by domain or independent application under test.
• E.g. One project for Frontend application testing and another project for backend API testing

Goal:

• Goals act as a test set, representing the overall objectives of testing, such as specific modules of an application.
• Each goal contains multiple tests (journeys).
• Goals include a descriptive name, starting URL, and optional testing configurations (e.g., screen resolution).
• E.g. A goal for creating tests associated with the Finance module of the application.

Journey:

• Journeys represent the end-to-end test cases and user flows of the application.
• Each journey consists of multiple checkpoints.
• E.g. End to end user process to purchase a product from an eCommerce website.

Checkpoint:

• Checkpoints are the containers for test steps.
• A set of test steps performing certain actions can be grouped into checkpoints, e.g., Logging in to an application, Performing checkout, etc.
• E.g. A set of  test steps to perform the checkout process.

Library Checkpoint:

• Library Checkpoints are the reusable components (common sequences and reuse test steps) within the Project.
• A checkpoint that can be reused across multiple journeys throughout the project should be converted into a Library checkpoint.
• E.g. A set of test steps to perform Login.

Step:

• Executable actions within a journey.
• E.g. Click on “Login” and assert “Input” equals “Text to be verified”.