Run any Skill in Manus with one click

Get Started

debug

Stars360

Forks123

UpdatedJuly 8, 2026 at 20:37

Debug a failing test or build error in WooCommerce iOS

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

woocommerce

woocommerce/woocommerce-ios

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	debug
description	Debug a failing test or build error in WooCommerce iOS
user-invocable	true
allowed-tools	Bash, Read, Grep, Glob
argument-hint	[test class/method or error description]

Debug a build failure or test failure in the WooCommerce iOS project.

For Build Failures

Run the build and capture errors:

bundle exec fastlane build_for_testing 2>&1 \
  | grep -E "error:|fatal|cannot find|undefined|ambiguous" | head -30

Identify the failing file and error type
Read the failing file and surrounding context
Common root causes in this codebase:
- Missing module: Check Modules/Package.swift target dependencies
- Type mismatch: A Networking model changed — check if Yosemite/Storage need updates
- Cannot find type: May need bundle exec rake generate after adding GeneratedCopiable/Fakeable
- Ambiguous reference: Duplicate type names across Networking vs Storage
- CoreData model errors: Check Storage/CoreData/ model versions
Propose or apply the fix

For Test Failures

Run the specific failing test (targeted tests require xcodebuild directly):

xcodebuild -workspace WooCommerce.xcworkspace -scheme WooCommerce \
  -destination 'platform=iOS Simulator,name=iPhone 16' \
  test \
  -only-testing:"<target>/<class>/<method>" 2>&1 | tail -50

Read the test file and understand what it expects
Read the implementation file being tested
Check the mock class setup
Common test failure patterns:
- Assertion mismatch: Verify expected vs actual, check mock stub values
- Async timeout: Check if mock callbacks are being invoked, verify continuation setup
- Nil unwrap: Check if mock return values are configured
- Wrong mock state: Verify spy properties are set correctly
- CoreData errors: Ensure InMemoryStorage is used, not persistent storage
- Missing @MainActor: Some tests need MainActor annotation
Propose or apply the fix

If the simulator destination fails, run xcrun simctl list devices available to discover available simulators, then re-run with a matching device name.

More from this repository

same repository

auto-login

woocommerce/woocommerce-ios

Launch the WooCommerce app on a simulator already authenticated into a given store (site credentials, application password, or WPCom), skipping the manual login UI. Meant to be referenced by other skills/workflows that need a logged-in session fast, but also directly runnable.

2026-07-13360

woo-ai-smoke

woocommerce/woocommerce-ios

Evaluate WooAIAssistant against a structured scenario suite with hard invariants + LLM-as-judge rubric scoring. Runs live against the demo store + gpt-5.1 via the woo-mobile-ai backend wrapper, writes a JSONL run record, compares against stored baselines, and surfaces regressions. Always delegated to a subagent so the main context only sees the markdown report.

2026-07-08360

verify

woocommerce/woocommerce-ios

Build the app, launch on simulator, and verify feature behavior via mobile-mcp interaction. Use after making changes to visually confirm they work from a user's perspective.

2026-07-08360

woocommerce/woocommerce-ios

Create a pull request following WooCommerce iOS conventions

2026-03-13360

setup-context-a8c

woocommerce/woocommerce-ios

Set up the ContextA8C MCP server for accessing Automattic internal resources (Slack, Linear, P2s, GitHub Enterprise, etc.)

2026-03-05360

simulator

woocommerce/woocommerce-ios

Discover and boot an iOS simulator. Use before any command that needs a simulator UDID.

2026-03-04360

name	debug
description	Debug a failing test or build error in WooCommerce iOS
user-invocable	true
allowed-tools	Bash, Read, Grep, Glob
argument-hint	[test class/method or error description]

Debug a build failure or test failure in the WooCommerce iOS project.

For Build Failures

Run the build and capture errors:

bundle exec fastlane build_for_testing 2>&1 \
  | grep -E "error:|fatal|cannot find|undefined|ambiguous" | head -30

Identify the failing file and error type
Read the failing file and surrounding context
Common root causes in this codebase:
- Missing module: Check Modules/Package.swift target dependencies
- Type mismatch: A Networking model changed — check if Yosemite/Storage need updates
- Cannot find type: May need bundle exec rake generate after adding GeneratedCopiable/Fakeable
- Ambiguous reference: Duplicate type names across Networking vs Storage
- CoreData model errors: Check Storage/CoreData/ model versions
Propose or apply the fix

For Test Failures

Run the specific failing test (targeted tests require xcodebuild directly):

xcodebuild -workspace WooCommerce.xcworkspace -scheme WooCommerce \
  -destination 'platform=iOS Simulator,name=iPhone 16' \
  test \
  -only-testing:"<target>/<class>/<method>" 2>&1 | tail -50

Read the test file and understand what it expects
Read the implementation file being tested
Check the mock class setup
Common test failure patterns:
- Assertion mismatch: Verify expected vs actual, check mock stub values
- Async timeout: Check if mock callbacks are being invoked, verify continuation setup
- Nil unwrap: Check if mock return values are configured
- Wrong mock state: Verify spy properties are set correctly
- CoreData errors: Ensure InMemoryStorage is used, not persistent storage
- Missing @MainActor: Some tests need MainActor annotation
Propose or apply the fix

If the simulator destination fails, run xcrun simctl list devices available to discover available simulators, then re-run with a matching device name.