Quickstart Guide

Overview

When using Test Assistant, it is advisable to utilize Starter Packs for streamlined configurations and efficient implementations. However, should you opt for creating all modules from the ground up, see General configuration.

Prerequisites

Kubernetes and Helm requirements

• Kubernetes version 1.28 or higher
  • ingress-nginx
  • cert-manager
  • PostgreSQL database with TA DB Pack
  • Ocular Framework (if ocular will be used as auth)
• Helm version 3.0 or higher

System requirements

The following are the minimum requirements for machines running Test Assistant:

Prerequisite packages

Test Assistant offers two prerequisite packages — Bundles and Configuration Migration Assistant (CMA). These packages serve as the foundation for Test Assistant to operate. Before installation, you are required to deploy only one of the two packages to ensure the functionality of Test Assistant. For more information, see Prerequisite packages.

Selenium IDE plugin

Selenium IDE plugin is a third-party browser plugin that needs to be installed in your browsers. This plugin is the primary tool used for scenarios involving UI recordings.

To install a Selenium IDE plugin, see Getting Started in the Selenium IDE documentation.

Starter Packs

Starter packs are sets of pre-defined scenarios that you can employ for your testing projects. These scenarios cover a wide range of diverse testing situations, enabling you to begin your testing project effortlessly and efficiently. This ensures comprehensive coverage of crucial testing scenarios right from the start.

Test Assistant offers the following starter packs for the following industries:

• Banking — To see the list of pre-defined scenarios for the banking industry, see Banking starter pack.
• Healthcare
• Utilities

Use a starter pack

To use a starter pack, follow these steps:

1. Install Test Assistant.
2. Ensure that all the Prerequisites are met.
3. Ensure that all the Required Test Assistant actions have been completed.
4. Modify your test data. For more information, see Data sets.
5. Optional: If you are using a custom API, ensure that you have modified the Payload Details in the Services module. For more information, see Services.
6. Navigate to Test Runs & Results > Test Run. To run a test suite, see Execute a test in Test Run.
7. View your test results in Runs & Results > Run Results. For more information, see Run Results.

Required Test Assistant actions

Batch configurations

You have to set up your batch configurations for batch executions. For more information, see Batch Configurations in Configurations.

Environment configuration and authentication details

Before running the test, ensure that the testing environment is properly set up and configured. This includes specifying the necessary credentials and database details for accessing the configured environment. For more information, see Create an environment in Environment.

General configuration

If you decide to customize all modules, follow these steps:

1. Verify that all the Prerequisites are met.
2. Install Test Assistant.
3. Create an external system.
4. Create an environment for the created external system in the previous step.
5. Create a project for the created external system in Step 3.
6. Create a feature for the created project in the previous step.
7. Create a service for the created external system in Step 3.
8. Create a validation service for the created external system in Step 3.
9. Create a step for the created service in Step 7. Link all applicable validation services.
10. Create a scenario. Link all applicable steps and validation services.
11. Create a dataset for the created scenario in the previous step.
12. Execute a test.
13. View the run results.