Skip to main content

🏗️ Testing in X-AutoMate

Test Cases are the core units of execution in X-AutoMate.
They represent the smallest testable components in your datastore.
Each test case can result in a Pass or Fail status based on industry-standard validation rules.

🧩 Test Suite and Test Case Relationship​

A Test Suite is a logical grouping of related test cases.

🧸 Analogy

A Test Case is like a toy, and a Test Suite is a box that contains toys.

  • A test case can belong to multiple test suites.
  • A test suite can include multiple test cases.

🧪 Test Approach​

Test Approaches define how a component is tested.
They offer an abstraction layer that helps standardize testing across similar systems or flows.

🧠 Analogy

A Test Approach is the type of toy (e.g., car, dinosaur, doll), while a Test Case is a specific toy (e.g., red sports car).

  • A test case can implement multiple test approaches.
  • A test approach can be reused across many test cases.

🧠 Rules (Behind-the-Scenes Logic)​

Rules are internal, often SQL-based templates used to identify or connect related test cases behind the scenes.

🔧 Analogy

Rules are like a suspension system in a toy car—vital but hidden.

  • Rules are not visible to end users.
  • They help structure and standardize logic across cases.

📚 Hierarchy Overview​

X-AutoMate’s test structure is organized into three levels:

  1. Test Suites – Top-level functional groups (e.g., "Purchase Flow Tests")
  2. Test Approaches – Defined methods or patterns (e.g., "Purchase Fibre Connection")
  3. Test Cases – Concrete, executable test scenarios (e.g., "Purchase 10/10 Mbps Fibre")

💡 Example Scenarios​

🖥️ Web UI Test

  • Suite: Purchase Product
    • Approach: Purchase Fibre Connection
      • Case: Purchase 10/10 Mbps Fibre Broadband

🗄️ ETL/Data Test

  • Suite: Data Quality Tests
    • Approach: Missing Values Check
      • Case: Null check in primary key columns (customer table)

🧪 Test Case Types​

X-AutoMate supports several types of test cases:

  1. 🏗️ ETL Test Cases – Validate Extract, Transform, Load processes
  2. 📊 Data Quality (DQ) Checks – Validate completeness, accuracy, and integrity
  3. 🧰 Custom Test Cases – Fully user-defined and flexible
  4. 🔄 Reconciliation Tests – Validate consistency across multiple data sources

Each type is documented separately with specific examples.

🧭 Accessing the Test Menu​

To manage your test components:

  1. Click the "Test" option from the main navigation screen
  2. From there, access:
    • 🧩 Test Suites
    • 🧪 Test Approaches
    • 📄 Test Cases

🧵 End-to-End Use Case​

By combining Test Suites, Test Approaches, and Test Cases, X-AutoMate supports cross-technology validation.

Example:
After purchasing a 10/10 Mbps fibre line via Web UI, a test ensures no NULL values exist in key fields in the backend database for that order.

📥 Bulk Changes @ Test Suites / Test Cases​

Users can:

  • 📤 Download selected suites/cases as Excel for bulk editing
  • 📥 Reupload the modified file to update the system
  • ➕ Create new Test Suites or Test Cases using the New button on the same screen

This feature is especially useful when large changes occur in table structure or test naming.

Test Case Interface