Add API error monitoring tests and error context snapshots for various browsers

- Created error context snapshots for Firefox, WebKit, and Chromium to capture UI state during API error monitoring.
- Implemented e2e tests for API error detection, including console errors, failed API requests, and proxy errors.
- Added functionality to ignore specific API patterns in monitoring assertions.
- Ensured tests validate the monitoring system's ability to detect and report errors effectively.
This commit is contained in:
catlog22
2026-01-31 00:15:59 +08:00
parent f1324a0bc8
commit a0f81f8841
66 changed files with 3112 additions and 3175 deletions

View File

@@ -242,6 +242,12 @@ ${newFocusFromUser}
### Phase 2: CLI Exploration
**⚠️ CRITICAL - CLI EXECUTION REQUIREMENT**:
- **MUST** wait for ALL CLI executions to fully complete before proceeding
- After launching CLI with `run_in_background: true`, **STOP** and wait for hook callback
- **DO NOT** proceed to Phase 3 until all CLI results are received
- Minimize output: No processing until 100% results available
**Step 2.1: Launch Parallel Explorations**
```javascript
@@ -285,6 +291,7 @@ Schema:
}
// Gemini CLI for deep analysis
// ⚠️ CRITICAL: Must wait for CLI completion before aggregating
explorationPromises.push(
Bash({
command: `ccw cli -p "
@@ -314,6 +321,8 @@ CONSTRAINTS: Focus on ${dimensions.join(', ')}
)
```
**⚠️ STOP POINT**: After launching CLI calls, stop output immediately. Wait for hook callback to receive results before continuing to Step 2.2.
**Step 2.2: Aggregate Findings**
```javascript