Results for “drive”

Guides test-first development with vertical slices, writing one behavior test at a time and refactoring only when green.

Guides test-driven development for Laravel apps using PHPUnit and Pest, covering factories, database testing, fakes, and coverage targets.

Guides implementing features and fixing bugs by writing failing tests first, then minimal code, with verification at each step.

Runs a test-driven rendering loop for Copier templates, writing E2E assertions first and iterating until every flavor renders cleanly before committing.

Guides test-driven development for Spring Boot services using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo to achieve 80%+ coverage.

Define owned inductive invariants and enforce them at parse, construct, API, DB, lock, or transaction boundaries, with counterexample-driven verification.

Guides the red-green-refactor cycle for implementing features with test-driven development, including test quality guidelines, framework setup, and commit patterns.

Guides test-driven development for Django applications using pytest, factory_boy, and Django REST Framework, covering models, views, serializers, and API testing.

Executes implementation plans by dispatching a fresh subagent per task and running two-stage reviews for spec compliance and code quality.

Runs a hypothesis-driven debugging workflow that reproduces failures, forms discriminating tests, proves root cause via toggle, and delivers a fix, regression test, and postmortem.

Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests for new features, bug fixes, and refactoring.

Guides test-driven development for Spring Boot services with JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo, covering unit, web, integration, and persistence tests.

Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests when writing features, fixing bugs, or refactoring code.

Execute implementation plans by dispatching a fresh subagent per task, with task review after each and a whole-branch review at the end.

Prove a feature works by delegating verification to an independent sub-agent that drives the real app, then open a pull request with the proof.

Refactors production code with test coverage using a TDD workflow that applies approved refactorings one at a time, gates each on passing tests, and commits or reverts accordingly.

Runs adversarial UI tests in a real browser, covering functional, accessibility, responsive, and UX checks, with diff-driven, exploratory, and parallel workflows.

Walks a running app across routes, states, and interactions to find real bugs, then root-causes, fixes, adds regression tests, and verifies each fix before committing.

Searches for existing content pages containing a specific block in AEM Edge Delivery Services, reporting URLs with occurrences and variants to help identify test content during development.

Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with generics, interfaces, and robust error handling.

Enforces strict outside-in red-green-refactor TDD with one-failure-per-turn discipline, predicting failures before every run, hardcoding minimum changes, and using triangulation and property-based testing. Triggers on explicit TDD requests and tasks phrased as 'implement', 'add', 'write a function', 'build a feature'.