Test Automation Architecture logo

Test Automation Architecture

Community
Omar-Obando
test-automation-architecture

Use when designing test automation frameworks, implementing page object patterns, creating test reporting systems, and managing parallel test execution. Includes test strategy, test data management, and test infrastructure setup. Based on CTFL-TA and ISTQB Advanced Level certifications.

Overview

PublisherOmar-Obando
Repositoryqwen-orchestrator
Skill nametest-automation-architecture
Stars
53
Forks
13
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Omar-Obando on GitHub. Read the source before you install it.

Installation

Install the Test Automation Architecture AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Omar-Obando/qwen-orchestrator/tree/main/skills/test-automation-architecture
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Omar-Obando/qwen-orchestrator.git /tmp/qwen-orchestrator
mkdir -p .claude/skills
cp -r /tmp/qwen-orchestrator/skills/test-automation-architecture .claude/skills/test-automation-architecture
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Test Automation Architecture in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Test Automation Architecture on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Test Automation Architecture is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Test Automation Architecture Skill — QA Engineer

Overview

This skill provides comprehensive guidance for designing and implementing test automation frameworks. It covers page object patterns, test reporting, parallel execution, test data management, and test infrastructure following CTFL-TA and ISTQB Advanced Level certifications.

When to Use

Use this skill when:

  • Designing test automation frameworks
  • Implementing page object patterns
  • Creating test reporting and dashboards
  • Managing parallel test execution
  • Setting up test data management
  • Designing test infrastructure
  • Implementing test framework best practices
  • Creating test libraries and utilities
  • Setting up CI/CD integration
  • Designing test environment management
  • Implementing test result analysis
  • Creating test metrics and KPIs
  • Designing test coverage reporting
  • Implementing test flakiness reduction
  • Setting up test monitoring
  • Designing test data privacy
  • Implementing test version control
  • Creating test documentation
  • Designing test failure analysis
  • Implementing test performance optimization
  • Setting up test orchestration
  • Designing test scalability
  • Creating test maintainability strategies
  • Implementing test quality gates

Do NOT use this skill when:

  • Writing application business logic (use domain-driven skill)
  • Designing database schemas (use database-design skill)
  • Writing API endpoint specifications (use api-design skill)
  • Performing security audits (use security-auditor skill)
  • Writing SQL queries (use sql-best-practices skill)
  • Designing multi-page website layouts (use design-system skill)
  • Analyzing deployment configurations (use deployment skill)
  • Writing documentation (use documentation-best-practices skill)

Test Framework Architecture

Layered Architecture

┌─────────────────────────────────────────────────────────────┐
│              Test Framework Architecture                    │
├─────────────────────────────────────────────────────────────┤
│  ┌──────────────────────────────────────────────────────┐   │
│  │              Test Layer (Tests)                      │   │
│  │  - Feature tests                                       │   │
│  │  - Integration tests                                   │   │
│  │  - Unit tests                                          │   │
│  └──────────────────────────────────────────────────────┘   │
│  ┌──────────────────────────────────────────────────────┐   │
│  │           Support Layer (Utilities)                  │   │
│  │  - Test data builders                                  │   │
│  │  - API clients                                         │   │
│  │  - Database helpers                                    │   │
│  └──────────────────────────────────────────────────────┘   │
│  ┌──────────────────────────────────────────────────────┐   │
│  │           Framework Layer (Base Classes)             │   │
│  │  - Page objects                                        │   │
│  │  - Test base classes                                   │   │
│  │  - Assertions                                          │   │
│  └──────────────────────────────────────────────────────┘   │
│  ┌──────────────────────────────────────────────────────┐   │
│  │           Tool Layer (Test Runner)                   │   │
│  │  - Test runner (Jest, Mocha, Pytest)                  │   │
│  │  - Reporting (Allure, HTML report)                    │   │
│  │  - CI/CD integration                                   │   │
│  └──────────────────────────────────────────────────────┘   │
└─────────────────────────────────────────────────────────────┘

Page Object Pattern

typescript
// ✅ Good: Page Object Pattern
class LoginPage {
  constructor(private page: Page) {}

  async navigate() {
    await this.page.goto('/login');
  }

  async fillEmail(email: string) {
    await this.page.fill('#email', email);
  }

  async fillPassword(password: string) {
    await this.page.fill('#password', password);
  }

  async submit() {
    await this.page.click('#login-btn');
  }

  async isLoggedIn(): Promise<boolean> {
    return await this.page.isVisible('#dashboard');
  }
}

// Test using Page Object
test('user can login', async () => {
  const loginPage = new LoginPage(page);
  await loginPage.navigate();
  await loginPage.fillEmail('user@example.com');
  await loginPage.fillPassword('password123');
  await loginPage.submit();
  expect(await loginPage.isLoggedIn()).toBe(true);
});

Test Data Management

Test Data Builder Pattern

typescript
// ✅ Good: Test Data Builder
class UserBuilder {
  private user: Partial<User> = {
    email: faker.internet.email(),
    name: faker.name.findName(),
    role: 'user',
  };

  withEmail(email: string) {
    this.user.email = email;
    return this;
  }

  withRole(role: UserRole) {
    this.user.role = role;
    return this;
  }

  build(): User {
    return this.user as User;
  }

  async create(): Promise<User> {
    const user = this.build();
    return await userRepository.create(user);
  }
}

// Usage
const user = await new UserBuilder().withRole('admin').create();

Test Data Isolation

typescript
// ✅ Good: Test data isolation
beforeEach(async () => {
  await database.truncate();
});

afterEach(async () => {
  await database.truncate();
});

// ❌ Bad: Shared test data
test('user creates order', async () => {
  // Uses same data as other tests
  const user = await User.find(1);
});

Parallel Test Execution

Parallelization Strategy

┌─────────────────────────────────────────────────────────────┐
│              Parallel Execution Strategy                    │
├─────────────────────────────────────────────────────────────┤
│  1. Test Suite Splitting                                    │
│     - Split by feature, module, or test type               │
│     - Balance execution time across workers                 │
│                                                              │
│  2. Resource Isolation                                      │
│     - Separate databases per worker                         │
│     - Isolated test data                                    │
│     - Unique test identifiers                               │
│                                                              │
│  3. Test Ordering                                           │
│     - Randomize test order                                  │
│     - Run slow tests first                                  │
│     - Group related tests                                   │
│                                                              │
│  4. Retry Logic                                             │
│     - Retry flaky tests                                     │
│     - Track flakiness metrics                               │
└─────────────────────────────────────────────────────────────┘

Parallel Configuration

yaml
# Example: Jest parallel configuration
testEnvironment: node
testRunner: jest-circus/runner
maxWorkers: 4
workerIdleMemoryLimit: 512MB
forceExit: false

Test Reporting

Reporting Dashboard

┌─────────────────────────────────────────────────────────────┐
│              Test Reporting Dashboard                       │
├─────────────────────────────────────────────────────────────┤
│  ┌─────────────┐  ┌─────────────┐  ┌─────────────┐         │
│  │  Total      │  │  Passed     │  │  Failed     │         │
│  │  Tests: 150 │  │  Tests: 145 │  │  Tests: 5   │         │
│  └─────────────┘  └─────────────┘  └─────────────┘         │
│  ┌─────────────┐  ┌─────────────┐  ┌─────────────┐         │
│  │  Duration   │  │  Pass Rate  │  │  Flaky      │         │
│  │  45s        │  │  96.7%      │  │  Tests: 2   │         │
│  └─────────────┘  └─────────────┘  └─────────────┘         │
│                                                              │
│  Test Results by Module:                                     │
│  ┌─────────────┬─────────┬─────────┬─────────┐              │
│  │ Module      │ Total   │ Passed  │ Failed  │              │
│  ├─────────────┼─────────┼─────────┼─────────┤              │
│  │ Auth        │ 25      │ 25      │ 0       │              │
│  │ Orders      │ 30      │ 28      │ 2       │              │
│  │ Products    │ 40      │ 40      │ 0       │              │
│  │ Users       │ 35      │ 32      │ 3       │              │
│  └─────────────┴─────────┴─────────┴─────────┘              │
└─────────────────────────────────────────────────────────────┘

Test Metrics

┌─────────────────────────────────────────────────────────────┐
│              Test Metrics                                   │
├─────────────────────────────────────────────────────────────┤
│  Coverage Metrics:                                          │
│  - Line coverage: 85%                                       │
│  - Branch coverage: 78%                                     │
│  - Function coverage: 90%                                   │
│  - Statement coverage: 82%                                  │
│                                                              │
│  Quality Metrics:                                           │
│  - Test pass rate: 96.7%                                    │
│  - Test flakiness: 1.3%                                     │
│  - Mean time to recovery: 5 minutes                         │
│  - Test execution time: 45 seconds                          │
│                                                              │
│  ROI Metrics:                                               │
│  - Bugs caught before prod: 45                              │
│  - Time saved: 20 hours/week                                │
│  - Release frequency: 3x faster                             │
└─────────────────────────────────────────────────────────────┘

Real-World Impact

Before this skill:

  • Ad-hoc test automation
  • Flaky tests
  • Poor test coverage
  • No reporting
  • Manual test execution

After this skill:

  • Well-designed test framework
  • Reliable, fast tests
  • Comprehensive coverage
  • Detailed reporting
  • Automated parallel execution

Cross-References

  • testing-strategy - For test strategy and planning
  • tdd-workflow - For test-driven development
  • devops-pipeline - For CI/CD integration

References

Frequently asked questions

What does the Test Automation Architecture AI skill do?

Use when designing test automation frameworks, implementing page object patterns, creating test reporting systems, and managing parallel test execution. Includes test strategy, test data management, and test infrastructure setup. Based on CTFL-TA and ISTQB Advanced Level certifications.

Why use Test Automation Architecture on TypingMind?

Because you install it once and use it with any model. Test Automation Architecture is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Test Automation Architecture in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Omar-Obando/qwen-orchestrator/tree/main/skills/test-automation-architecture. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Test Automation Architecture?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Test Automation Architecture?

As many as you like. As long as a model supports skills, you can use Test Automation Architecture with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Test Automation Architecture AI skill free?

Yes. It is published on GitHub by Omar-Obando under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇