Mehmet Akif Baysal

Use when a product decision or feature needs a written record - what to capture in a task document (PRD, decision record) and where to attach it, since TaskTrooper has no epic

中文简介正在准备中。当前显示原文说明。

Wire the automation test project into the repository's own pipeline so every task must pass the suite before it can leave QA

中文简介正在准备中。当前显示原文说明。

Use when the task changes anything a user sees in a web app - booting it, driving flows with the browser tools, the four-width check, console/network/keyboard checks and the visual checklist

中文简介正在准备中。当前显示原文说明。

Use when a criterion mentions speed or limits, or the change touches a list, query, endpoint or page that could get slower - timing loops, the N-vs-10N data check and Lighthouse on a production build

中文简介正在准备中。当前显示原文说明。

Use after the targeted cases pass - choosing the adjacent behaviour this change can break from the PR's files and the component's links, and the per-repository smoke set

中文简介正在准备中。当前显示原文说明。

Use at the start of every QA round - recording the case matrix with record_test_cases (categories, criterion links, rejected cases) before touching the app, then executing all of it

中文简介正在准备中。当前显示原文说明。

Use when a case needs data, a user/role, or a third-party dependency - seeding through the product first, test credentials, namespacing on shared environments, and stubbing an external HTTP service by hand

中文简介正在准备中。当前显示原文说明。

Use before booting anything - choosing local (start_task_preview or a workspace boot), the task's preview or stage, confirming the build is the PR head, and what to do when nothing can run

中文简介正在准备中。当前显示原文说明。

Use when the task has a background job, queue consumer, scheduler or webhook - firing the real trigger, polling for the side effect, and the retry, idempotency and poison-message cases

中文简介正在准备中。当前显示原文说明。

Use when a screen must work without network or a mutation must survive a lost connection - local storage choice, the outbox pattern with idempotency keys, background replay, and how to test it with a fake clock and fake network.

中文简介正在准备中。当前显示原文说明。

Use when a feature needs camera, location, photos, notifications, contacts, microphone, Bluetooth, or local network - the per-platform request flow, every denial state, and how to actually test the denied path when the shared test device auto-grants permissions.

中文简介正在准备中。当前显示原文说明。

Use when moving tasks or reporting status - the kanban column semantics, which columns are human/architect/QA gates, and where the PM actually acts

中文简介正在准备中。当前显示原文说明。

Use when organizing the workspace - create/rename initiative projects and link repositories to them directly, since these are factual actions needing no analiz or approval

中文简介正在准备中。当前显示原文说明。

Use when capturing what a feature must do - write testable user-story requirements that state WHAT and WHY, never HOW, with assumptions made explicit

中文简介正在准备中。当前显示原文说明。

Use when a stakeholder sends a request - route it to backlog tasks, an analiz task, or a focused question, decide ask-vs-assume with a Definition of Ready, and ask only what a wrong guess would actually cost

中文简介正在准备中。当前显示原文说明。

Use when the task touches a backend API, database or worker - booting it from the task branch, driving real requests and verifying side effects (DB rows, outbound calls, logs) as evidence

中文简介正在准备中。当前显示原文说明。

Maintain a dedicated automation test project per repository - separate from the product's unit tests - with API, worker, and UI suites written scenario-first

中文简介正在准备中。当前显示原文说明。

Use when the task touches a mobile app - the device flow with the mobile_* tools, confirming the installed build is the task's, and what to report when no device is attached

中文简介正在准备中。当前显示原文说明。

Use when a test needs a database - spin up a dedicated, disposable test database (Testcontainers) seeded with known data, never a shared or production database

中文简介正在准备中。当前显示原文说明。

Use before and after calling rollback_release - what a rollback restores per delivery mode, when a schema change makes a code rollback unsafe, how to work and report manual_steps, and what to do when rollback_release refuses

中文简介正在准备中。当前显示原文说明。

Use while deriving cases - Given/When/Then and the techniques (partitions, boundaries, decision tables, state transitions) that find the cases the criteria do not state

中文简介正在准备中。当前显示原文说明。

Use when the task came back to QA after need_revision - what to re-run, what may carry over, and how to keep old passes from approving new code

中文简介正在准备中。当前显示原文说明。

Use when a batch (desktop or mobile) release reaches awaiting_verdict or was rolled back - read-only checks that the published artifact really exists and is served, and the exact yank step for a bad tag

中文简介正在准备中。当前显示原文说明。

Use when building or changing any interactive mobile UI - VoiceOver/TalkBack labels, grouping, headings, focus order, Dynamic Type/font scale, reduce motion, contrast, and the automated check for each stack.

中文简介正在准备中。当前显示原文说明。