bug-workflow

Root cause analysis for unclear software bugs involves tracing call chains, analyzing logs, inspecting database states, and executing temporary end-to-end tests to capture evidence. This approach systematically investigates complex system interactions to pinpoint the underlying issue.

Playwright can be used to execute temporary end-to-end browser tests during bug investigation. This gathers debugging evidence by simulating user interactions, which is essential for identifying root causes in complex multi-service environments.

Investigating bugs in a complex multi-service environment requires analyzing distributed logs, checking database states, and tracing call chains across services. Using browser debugging tools to gather evidence ensures accurate root cause identification.

This debugging workflow focuses strictly on root cause identification rather than code modification. It analyzes logs and database states, then generates detailed tasks for a tdd-agent to implement the actual fixes.

Generating actionable tasks for a tdd-agent requires completing a thorough bug investigation first. Once the root cause is identified through log analysis and temporary tests, detailed implementation tasks are automatically generated for the agent.

A dedicated bug investigation workflow is necessary when tdd-agent cannot reproduce a reported bug. It performs deep dives into logs, database states, and uses temporary browser tests to capture evidence that direct debugging might miss.