Belajar Quality Engineer - Test Automation Mastery

#Pendahuluan

Setelah di episode 2 kita mempelajari quality strategy & test pyramid, pada episode ini kita mempelajari test automation mastery — bagaimana membangun framework automation yang maintainable dan scalable. Automation mastery bukan sekadar menulis test, tapi membangun sistem automation yang bisa bertahan dan berkembang.

Mengapa automation mastery penting? Karena test automation yang buruk bisa menjadi burden: flaky tests, maintenance tinggi, danROI rendah. Dengan mastery, kalian bisa membangun automation yang reliable dan memberikan value jangka panjang.

#Framework Design Principles

#Design Principles

text

Automation Design Principles:
├── DRY (Don't Repeat Yourself):
│   ├── Reusable functions
│   ├── Shared utilities
│   └── Centralized locators
├── KISS (Keep It Simple):
│   ├── Simple test logic
│   ├── Clear assertions
│   └── Minimal dependencies
├── SOLID Principles:
│   ├── Single responsibility
│   ├── Open/closed
│   ├── Liskov substitution
│   ├── Interface segregation
│   └── Dependency inversion
└── Page Object Model:
    ├── Separate test logic dari page logic
    ├── Reusable page components
    └── Easy maintenance

#Framework Structure

text

Framework Structure:
├── src/
│   ├── pages/
│   │   ├── LoginPage.ts
│   │   ├── DashboardPage.ts
│   │   └── components/
│   │       ├── HeaderComponent.ts
│   │       └── FooterComponent.ts
│   ├── fixtures/
│   │   ├── auth.fixture.ts
│   │   └── test-data.fixture.ts
│   ├── utils/
│   │   ├── api-helper.ts
│   │   ├── db-helper.ts
│   │   └── report-helper.ts
│   └── types/
│       └── index.ts
├── tests/
│   ├── auth/
│   │   ├── login.spec.ts
│   │   └── registration.spec.ts
│   └── checkout/
│       ├── checkout.spec.ts
│       └── payment.spec.ts
├── playwright.config.ts
└── package.json

#Reusable Components

#Component Pattern

typescript

// components/SearchComponent.ts
export class SearchComponent {
  constructor(private page: Page) {}
 
  async search(query: string) {
    await this.page.fill('#search-input', query);
    await this.page.click('#search-button');
  }
 
  async getResults() {
    return this.page.locator('.search-result').allTextContents();
  }
 
  async getResultCount() {
    return this.page.locator('.search-result').count();
  }
}

#Fixture Pattern

typescript

// fixtures/auth.fixture.ts
import { test as base } from '@playwright/test';
 
export const test = base.extend({
  authenticatedPage: async ({ page, browserName }, use) => {
    // Setup: login
    await page.goto('/login');
    await page.fill('#email', 'test@example.com');
    await page.fill('#password', 'password123');
    await page.click('#login-button');
    await page.waitForURL('/dashboard');
 
    // Provide authenticated page
    await use(page);
 
    // Teardown: logout
    await page.click('#logout-button');
  },
});

Note

Reusable components adalah kunci maintainability. Saat UI berubah, kalian hanya perlu update component, bukan semua test cases. Investasi di awal akan menghemat waktu jangka panjang.

#Flaky Test Management

#Identifikasi Flaky Tests

text

Flaky Test Indicators:
├── Test yang kadang pass kadang fail
├── Test yang gagal tanpa code change
├── Test yang depend pada timing
├── Test yang depend pada external service
└── Test yang depend pada test order

#Fix Flaky Tests

text

Flaky Test Fixes:
├── Remove timing dependencies:
│   ├── Use auto-wait
│   ├── Explicit waits
│   └── Polling for conditions
├── Isolate tests:
│   ├── Independent test data
│   ├── No shared state
│   └── Parallel execution safe
├── Mock external dependencies:
│   ├── API mocking
│   ├── Service virtualization
│   └── Stub responses
└── Fix test data:
    ├── Unique data per test
    ├── Cleanup after test
    └── Deterministic data

#Practical: Automation Quality Metrics

yaml

automation_quality:
  metrics:
    - test_pass_rate: "target > 99%"
    - flaky_test_rate: "target < 1%"
    - execution_time: "target < 30 minutes"
    - maintenance_time: "target < 20% of development"
  practices:
    - code_review_for_tests
    - regular_refactoring
    - flaky_test_tracking
    - test_coverage_monitoring

Tip

Automation maintenance harus < 20% dari development time. Jika lebih, ada masalah dengan framework design. Refactor secara teratur dan investasi di reusable components.

#Penutup

Pada episode 3 ini, kalian telah mempelajari test automation mastery.

Inti yang harus dibawa pulang:

Design principles: DRY, KISS, SOLID, Page Object Model.
Framework structure: pages, fixtures, utils, types.
Reusable components: component pattern, fixture pattern.
Flaky test management: identifikasi dan fix.

Di episode 4 selanjutnya, kita akan membahas contract testing — bagaimana menguji kontrak antara service menggunakan consumer-driven contracts. Sampai jumpa di episode 4!