Belajar QA Tester - Shift-Left & Continuous Quality

#Pendahuluan

Setelah di episode 23 kita mempelajari test automation introduction, pada episode ini kita mempelajari shift-left & continuous quality — pendekatan yang memulai quality sejak awal siklus development, bukan hanya saat testing. Shift-left adalah philosophy yang mengubah cara tim berpikir tentang kualitas.

Mengapa shift-left penting? Karena bug yang ditemukan di awal (requirement/design) jauh lebih murah untuk diperbaiki dibanding bug yang ditemukan di production. Dengan shift-left, tim bisa mengurangi cost dan meningkatkan kualitas secara signifikan.

#Shift-Left Testing

#Traditional vs Shift-Left

text

Traditional Approach:
├── Requirement → Design → Code → Test → Deploy
├── Testing di akhir siklus
├── Bug fix mahal
└── Quality responsibility di QA
 
Shift-Left Approach:
├── Quality di setiap fase
├── Testing di awal siklus
├── Bug prevention lebih baik dari bug detection
└── Quality responsibility semua orang

#Shift-Left Activities

text

Shift-Left Activities:
├── Requirement Phase:
│   ├── QA review requirement
│   ├── Identify testable requirements
│   ├── Suggest improvements
│   └── Create acceptance criteria
├── Design Phase:
│   ├── QA review design
│   ├── Identify testability issues
│   ├── Suggest design for testability
│   └── Create test strategy
├── Development Phase:
│   ├── Unit testing by developer
│   ├── Code review with QA perspective
│   ├── Continuous integration
│   └── Early testing
└── Testing Phase:
    ├── Automated regression
    ├── Exploratory testing
    └── Quality gates

#Continuous Quality

#Quality in Every Phase

text

Continuous Quality:
├── Every commit:
│   ├── Unit tests pass
│   ├── Code review approved
│   └── Linting clean
├── Every build:
│   ├── Integration tests pass
│   ├── Security scan clean
│   └── Performance baseline met
├── Every deployment:
│   ├── Smoke tests pass
│   ├── E2E tests pass
│   └── Monitoring active
└── Every day:
    ├── Quality metrics review
    ├── Bug triage
    └── Process improvement

#Quality Gates

text

Quality Gates:
├── Gate 1: Code Quality
│   ├── Linting passes
│   ├── Code review approved
│   └── No critical issues
├── Gate 2: Test Quality
│   ├── Unit test coverage > 80%
│   ├── All tests pass
│   └── No flaky tests
├── Gate 3: Security
│   ├── No high/critical vulnerabilities
│   └── OWASP scan clean
├── Gate 4: Performance
│   ├── Response time < threshold
│   └── No performance regression
└── Gate 5: Release
    ├── All gates passed
    ├── Product owner approval
    └── QA sign-off

Note

Shift-left bukan berarti QA harus melakukan semua testing. Ini berarti semua orang (developer, designer, product owner) ikut bertanggung jawab atas kualitas.

#Practical: Shift-Left Implementation

yaml

shift_left_implementation:
  requirement:
    - qa_review_user_stories
    - create_acceptance_criteria
    - identify_test_scenarios
  design:
    - review_for_testability
    - create_test_strategy
    - identify_automation_opportunities
  development:
    - unit_testing_required
    - code_review_with_qa
    - continuous_integration
  testing:
    - automated_regression
    - exploratory_testing
    - quality_gates

Tip

Mulai dengan QA review requirement dan user stories. Ini adalah shift-left activity termudah yang memberikan dampak signifikan.

#Penutup

Pada episode 24 ini, kalian telah mempelajari shift-left & continuous quality.

Inti yang harus dibawa pulang:

Shift-left: mulai quality sejak requirement, bukan hanya saat testing.
Continuous quality: quality di setiap commit, build, deployment.
Quality gates: checkpoint untuk memastikan kualitas sebelum lanjut.
Everyone responsible: quality bukan hanya tanggung jawab QA.

Di episode 25 selanjutnya, kita akan membahas QA metrics & reporting — bagaimana mengukur dan melaporkan kualitas secara efektif. Sampai jumpa di episode 25!