QA·SDET 스킬 갭 체크리스트

✕Test design techniquesexpected: Working

Boundary values, equivalence partitions, decision tables and state transitions applied to real requirements.

✕Exploratory testingexpected: Working

Chartered sessions with notes, heuristics (SFDPOT, tours) and findings others can act on.

✕Defect reporting and triageexpected: Working

Minimal reproduction steps, evidence, severity vs priority, and root-cause conversations with developers.

✕Risk-based test planningexpected: Aware

Choosing what not to test, estimating effort and writing a test plan stakeholders read.

✕SQL for test data and verificationexpected: Working

Joins, aggregates and safe updates to set up data and verify persistence.

✕One language in depth (Java, TypeScript or Python)expected: Working

Types, collections, error handling, async code and reading stack traces without help.

✕Clean code and design patternsexpected: Working

Composition over inheritance, page objects/screenplay, builders and factories for test data, small functions.

✕Git and code reviewexpected: Working

Branches, rebasing, resolving conflicts and giving useful review comments on test code.

✕Unit and component testingexpected: Working

Writing and reviewing unit tests with mocks and fakes, and knowing where they beat end-to-end tests.

✕Playwright, Selenium or Cypressexpected: Working

Stable locators, auto-waiting vs explicit waits, fixtures/hooks, screenshots and traces.

✕Framework designexpected: Aware

Layering, configuration per environment, test data management, reporting and parallel safety.

✕Flaky test diagnosisexpected: Working

Using traces, retries data and timing analysis to fix root causes instead of adding sleeps.

✕Mobile automation (Appium, Espresso, XCUITest)expected: Aware

Device/emulator setup, capabilities and gestures; knows the trade-offs of each tool.

✕HTTP, REST and auth fundamentalsexpected: Working

Methods, status codes, headers, idempotency, OAuth 2.0 and JWT basics.

✕API automation (REST Assured, Playwright request, pytest + requests)expected: Working

Request builders, schema assertions, chained calls and data cleanup.

✕Contract testing and mockingexpected: Aware

Consumer-driven contracts (Pact) and service virtualization (WireMock) to test in isolation.

✕CI pipelines (GitHub Actions, Jenkins, GitLab CI)expected: Working

Running suites on pull requests, sharding, caching, artifacts and failure notifications.

✕Docker and test environmentsexpected: Aware

Dockerfiles and Compose for dependencies, ephemeral environments and seeded databases.

✕Logs, metrics and observabilityexpected: Aware

Finding failures in logs and dashboards; using trace IDs to connect a test to backend behaviour.

✕Performance testing (k6, JMeter, Gatling)expected: Aware

Workload models, percentiles, thresholds and interpreting results with the team.

✕Security testing basicsexpected: Aware

OWASP Top 10 awareness, input validation probes, auth/authorization checks and safe use of scanners.

✕Accessibility testingexpected: Aware

WCAG 2.2 basics, keyboard and screen-reader checks, and automated axe scans in CI.

✕Test strategy and the test pyramidexpected: Aware

Deciding what belongs at unit, API, contract and UI level for a system, and defending it with data.

✕Quality metricsexpected: Aware

Escaped defects, change failure rate, suite duration and flakiness rate; avoiding vanity metrics.

✕Mentoring and stakeholder communicationexpected: Aware

Coaching juniors, release sign-off conversations and explaining risk to non-testers.

✕Agile delivery and shift-left practicesexpected: Working

Three-amigos sessions, acceptance criteria review, definition of done and testing in the sprint.

✕AI-assisted testing toolsexpected: Aware

Using code assistants for test code and data with review, and knowing their failure modes.

○Testing AI/LLM featuresexpected: None

Evaluation sets, non-deterministic outputs, guardrails and regression of model-backed features.