Skip to main content

🧪 Test Approaches

The next level in the test case hierarchy is the Test Approach, representing an abstraction layer over the System Under Test (SUT).

A Test Approach is a reusable template that captures a common testing pattern or action performed within the system.

💡 Example

In a Web UI CRM system for broadband services:

  • Test Suite: Purchase Product
  • Test Approaches: Purchase Fibre Connection, Purchase ADSL Connection

In an ETL data pipeline context:

  • Test Suite: Data Quality Tests
  • Test Approaches: Out of Range Check, Missing Values Check

This abstraction makes test case creation faster, standardized, and scalable.

🔍 Managing Test Approaches​

On the Approaches screen, you can:

  • 🔎 Search by ID or name
  • 📂 View which Test Suite each approach belongs to
  • ▶️ Run a test approach
  • ✏️ Edit, 🚫 Deactivate, or 🗑️ Delete approaches
  • ➕ Use the (+) icon to expand and view related test cases

🆕 Creating a New Test Approach​

To add a new test approach:

  1. Click the ➕ New button.
  2. Fill in required details.
  3. You can also create test cases within the same screen.

🧠 Why Use Test Approaches?​

Analogy

Think of a Test Suite as a playlist.
Each Test Approach is a music genre (e.g., Rock, Jazz), and each Test Case is a specific song in that genre.

This model allows for:

  • Modular design
  • Reusable patterns
  • Cleaner test maintenance