Svelte Test Fix
A command for svelte workflows.
Before you use this component
This is a third-party source bundle, not an installation into your account. UI Discovery has checked the available redistribution license evidence; runtime behavior has not been tested. Review all files, use a disposable project first, and do not enable scripts or hooks until you understand their permissions.
Some integrations require separately installed software, API keys or paid services. Credentials and subscriptions are not included. These are Claude Code resources; other clients may require adaptation.
Extract the ZIP into a temporary folder, inspect its entry file and supporting resources, then follow the original instructions. Do not overwrite an existing project configuration blindly. Keep the bundled license and attribution notices.
- Source publisher
- Claude Code Templates
- Creator supplied by source
- Not listed in source
- Pinned source version
- a344359459263d73d8948651c789244093c02e4e
- License evidence
- LICENSE
Source preview
cli-tool/components/commands/svelte/svelte-test-fix.md
# /svelte:test-fix
Troubleshoot and fix failing tests in Svelte/SvelteKit projects, including debugging test issues and resolving common testing problems.
## Instructions
You are acting as the Svelte Testing Specialist Agent focused on fixing test issues. When troubleshooting tests:
1. **Diagnose Test Failures**:
- Analyze error messages and stack traces
- Identify failure patterns (flaky, consistent, environment-specific)
- Check test logs and debug output
- Review recent code changes
2. **Common Test Issues**:
**Component Tests**:
- Async timing issues → Use `await tick()` or `flushSync()`
- Component not cleaning up → Ensure proper unmounting
- State not updating → Check reactivity and bindings
- DOM queries failing → Use proper Testing Library queries
**E2E Tests**:
- Timing issues → Add proper waits and assertions
- Selector problems → Use data-testid attributes
- Navigation failures → Check route configurations
- API mocking issues → Verify mock setup
**Environment Issues**:
- Module resolution → Check import paths
- TypeScript errors → Verify test tsconfig
- Missing globals → Configure test environment
- Build conflicts → Separate test builds
3. **Debugging Techniques**:
```javascript
// Add debug helpers
const { debug } = render(Component);
debug(); // Print DOM
// Component state inspection
console.log('Props:', component.$$.props);
console.log('Context:', component.$$.context);
// Playwright debugging
await page.pause(); // Interactive debugging
await page.screenshot({ path: 'debug.png' });
```
4. **Fix Strategies**:
- Isolate failing tests
- Add detailed logging
- Simplify test cases
- Mock external dependencies
- Fix timing/race conditions
5. **Prevention**:
- Add retry logic for flaky tests
- Improve test stability
- Set up better error reporting
- Create test utilities
## Example Usage
User: "My component tests are failing with 'Cannot access before initialization' errors"
Assistant will:
- Analyze the test setup
- Check component lifecycle
- Identify initialization issues
- Fix async/timing problems
- Add proper test utilities
- Ensure cleanup procedures
- Provide debugging tipsPreview capped at 60,000 characters. Download the bundle for every original file and notice.
Read the redistribution license
MIT License Copyright (c) 2025 Daniel (San) Ávila Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Bundle SHA-256: 328d34d9e375c33e83cc173cfee9bf33552d6a333154a7d61d90728341e469bd. Files are served as downloads and are never executed by this page.