# QA Automation Engineer > Skill hỗ trợ agent thực hiện các tác vụ QA automation testing bao gồm generate test cases, automation scripts, API tests, locators, phân tích flaky tests, và tạo test data. Use when this capability is needed. - Skill: `tomevault-io/qa-automation-engineer` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/qa-automation-engineer` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/qa-automation-engineer/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/qa-automation-engineer --- # QA Automation Engineer ## Description This skill enables the agent to assist with software testing and automation tasks. The agent can: - Generate manual test cases from requirements - Generate test automation scripts from test cases or UI flows - Generate API tests from Swagger/OpenAPI specifications - Explore applications and discover test scenarios - Generate automation frameworks - Generate test data - Analyze flaky tests - Generate stable locators - Generate requirements from website analysis This skill is designed for modern QA workflows and automation development. --- # When to Use Use this skill when the user asks about: - Test automation - Manual testing - Automation frameworks - API testing - UI testing - Test data generation - Flaky test debugging - Locator generation - Requirements analysis from website - Jira integration (fetch requirements, push test results) - Xray test management Typical prompts include: - Generate test cases from requirement - Generate Selenium automation from test case - Generate automation from UI steps - Generate API tests from Swagger - Generate regression suite → _(redirect sang `generate_application_test_plan` hoặc `generate_manual_testcases_rbt`)_ - Generate test data - Analyze flaky test - Generate locator for element - Generate requirements from website --- # Workflow Routing When the user request matches a specific task, select the appropriate workflow file from `.agent/workflows/`. ### Generate test cases from requirements > **Delegate:** Tác vụ này thuộc skill **`rbt_manual_testing`** — không phải `qa_automation_engineer`. Use workflow: `generate_testcases_from_requirements` (QUICK mode) hoặc `generate_manual_testcases_rbt` (FULL RBT mode). Triggers when user asks: - generate test cases → **delegate to `rbt_manual_testing` (QUICK mode)** - write manual test cases → **delegate to `rbt_manual_testing` (QUICK mode)** - test scenarios from requirement → **delegate to `rbt_manual_testing` (QUICK mode)** - sinh test cases đầy đủ / quy trình 6 bước → **delegate to `rbt_manual_testing` (FULL RBT mode)** --- ### Generate automation from manual test case Use workflow: `generate_automation_from_testcases` Triggers when user asks: - convert test case to automation - generate Selenium automation - generate Playwright automation from test case --- ### Generate automation from UI steps Use workflow: `generate_automation_from_ui_flow` Triggers when user asks: - automate this UI flow - generate automation from steps - run UI steps and generate Selenium script --- ### Generate API tests Use workflow: `generate_api_tests_from_swagger` Triggers when user provides: - Swagger URL - OpenAPI specification --- ### Generate test data Use workflow: `generate_test_data` Triggers when user asks: - generate test data - generate boundary test data --- ### Analyze cross-module feature & generate combinatorial matrix Use workflow: `generate_cross_module_test_plan` > Workflow dành cho **tính năng phức tạp đi qua nhiều modules nối tiếp**. Sinh Data Flow Map + Ma trận kết hợp đa chiều (Pairwise / Business-critical / Full Cartesian). Triggers when user asks: - phân tích tính năng cross-module - test nhiều module liên kết - sinh ma trận kết hợp / combinatorial matrix - test tính năng có nhiều điều kiện kết hợp - analyze multi-module feature - pairwise testing - decision table đa chiều / nhiều chiều --- ### Generate combinatorial test data (multi-module pipeline) Use workflow: `generate_combinatorial_test_data` > Sinh test data cho ma trận kết hợp. Hỗ trợ 2 modes: **GENERATE** (sinh offline) và **PIPELINE** (chạy thật trên browser qua N modules). Triggers when user asks: - sinh data cho ma trận kết hợp - tạo test data cho combinatorial matrix - chạy pipeline tạo data qua nhiều module - generate combinatorial test data - setup data cho cross-module test --- ### Generate regression suite > **Không có workflow riêng.** Dùng `generate_application_test_plan` (Mode PLAN) hoặc `generate_manual_testcases_rbt` (FULL RBT) tùy theo input. Triggers when user asks: - create regression test suite - generate regression scenarios --- ### Generate automation framework > **Delegate:** Tác vụ này sử dụng skill **`framework_architect`** để thiết kế framework. Use workflow: `generate_automation_framework` Triggers when user asks: - create automation framework - design Selenium framework - design Playwright framework - design Appium framework - scaffold automation project - thiết kế framework mới --- ### Explore application and generate test plan Use workflow: `generate_application_test_plan` > Workflow này có **2 modes**: PLAN (mặc định — chỉ test plan) và FULL (test plan + automation skeleton). > Khi user yêu cầu "full automation suite" hoặc "bootstrap automation" → tự động chọn Mode FULL. Triggers when user asks: - explore application - discover test scenarios - generate test plan - generate full automation suite - bootstrap automation for project --- ### Analyze flaky tests Use workflow: `analyze_flaky_tests` Triggers when user asks: - why is this test flaky - analyze unstable automation --- ### Generate stable locators Use workflow: `generate_locator` Triggers when user asks: - generate locator for this element - find stable selector - create automation locator --- ### Generate requirements from website Use workflow: `generate_requirements_from_website` Triggers when user asks: - generate requirements from website - analyze website module and create requirements - extract user stories from web page --- ### Analyze requirement document > **Delegate:** Tác vụ này sử dụng skill **`requirements_analyzer`** để phân tích requirement documents. Use workflow: `analyze_requirement_document` > Workflow chỉ **phân tích** requirement — KHÔNG sinh test cases. Output là tài liệu phân tích chi tiết gồm: AC breakdown, dependencies, ambiguities, risks. Triggers when user asks: - phân tích requirement document - review yêu cầu / analyze this ticket - phân tích Jira ticket / requirement - tìm điểm mơ hồ trong requirement - analyze requirement / review requirement document --- ### Fetch requirements from Jira Use workflow: `fetch_jira_requirements` Triggers when user asks: - fetch jira requirements - lấy requirement từ jira - get jira ticket - import user stories from jira --- ### Import test results to Xray Use workflow: `import_test_results_xray` Triggers when user asks: - push test results to xray - đẩy kết quả test lên xray - import test execution to jira - upload playwright results to xray --- # Automation Framework Default automation stack: - **Language:** Java - **UI automation:** Selenium WebDriver or Playwright - **Test framework:** TestNG - **API automation:** REST Assured - **Mobile automation:** Appium - **Design pattern:** Page Object Model (POM) --- # Locator Strategy ## Selenium Locator Priority 1. `id` 2. `data-testid` 3. `name` 4. `css selector` 5. `xpath` (last resort) Avoid fragile locators such as auto-generated class names or positional xpaths. ## Playwright Locator Priority 1. `getByRole()` 2. `getByLabel()` 3. `getByPlaceholder()` 4. `getByText()` 5. `getByTestId()` 6. `css selector` 7. `xpath` (last resort) Avoid fragile selectors such as dynamic class names. > **Note:** For detailed locator rules, refer to `.agent/rules/locator_strategy.md`. --- # Rules References The agent MUST also follow the detailed rules defined in `.agent/rules/`: - [automation_rules.md](.agent/rules/automation_rules.md) — General automation best practices - [locator_strategy.md](.agent/rules/locator_strategy.md) — Detailed locator selection rules - [playwright_rules.md](.agent/rules/playwright_rules.md) — Playwright-specific rules - [selenium_rules.md](.agent/rules/selenium_rules.md) — Selenium-specific rules - [appium_rules.md](.agent/rules/appium_rules.md) — Appium mobile automation rules --- # References The agent may consult additional documentation in the `references/` folder: - `PROJECT_CONTEXT.md` — Project domain, tech stack, key modules - `TEST_STRATEGY.md` — Testing objectives, scope, execution plan - `PROMPT_TEMPLATES.md` — Reusable prompt templates for common QA tasks External references (thay thế cho các file đã gộp): - `plans/automation/project_architecture/README.md` — Repository structure & project architecture (thay thế REPOSITORY_MAP.md) - `GEMINI.md` > "Cleanup & Delivery" — Quality checklist / Definition of Done (thay thế SELF_CHECK.md) --- # Output Depending on the request, the agent may return: - Manual test cases (structured format) - Automation scripts (Java/TypeScript) - API tests (REST Assured) - Locator recommendations - Test data (structured, randomized, traceable) - Automation framework design - Requirements documents Automation outputs should include: - Page Object classes - Test classes - Assertions validating expected behavior - Clean, readable, maintainable code (no debug logs, no commented code) --- > Source: [anhtester/antigravity-testing-kit](https://github.com/anhtester/antigravity-testing-kit) — distributed by [TomeVault](https://tomevault.io).