General Test Execution Problems
If you experience issues where tests fail to run, generate, or execute properly, please follow the solution below:Most test execution issues can be resolved by completely deleting the generated
/testsprite_tests
directory and re-running the workflow from the beginning. If the problem persists, try reinstalling the TestSprite MCP Server.Cursor IDE
- Open Cursor IDE
- Go to the MCP Server panel/sidebar
- Find “TestSprite” in the server list
- Toggle the TestSprite MCP server OFF
- Wait 5-10 seconds
- Toggle the TestSprite MCP server ON
- Wait for the server to reconnect (green status indicator)
VS Code
- Stop VS Code completely
- Remove existing TestSprite MCP installation
- Clear VS Code workspace cache (optional)
- Reinstall latest version
- Verify installation
- Restart VS Code
- Reload VS Code window
- Press
- Type the following command:
- Press ⇧ Enter
Verification Steps
After reinstalling, verify the MCP server is working:- Test the server directly
- Check if the server responds
Advanced Troubleshooting
If reinstallation doesn’t resolve the issue:- Verify Node.js version (requires 22+)
- Update if needed
Common Error Messages
'Command not found' after reinstallation
'Command not found' after reinstallation
- Ensure Node.js 22+ is installed
- Restart your terminal/IDE
- Check PATH environment variable
Server connection failed
Server connection failed
- Verify internet connection
- Check firewall settings
- Validate API key format
Permission denied
Permission denied
- Use npx instead of global installation
- Fix npm permissions (see Installation Issues section)
When to Contact Support
If reinstallation doesn’t resolve your issue, please contact support with:- System information
- IDE and configuration details
- IDE name and version
- Operating system version
- Screenshot of the MCP Server panel
- Relevant configuration files (sanitized)