# Troubleshooting Common troubleshooting issues and best practices for Buddy Unit Tests. ### **Tests are not being reported to Buddy. What should I do?** If tests are not being reported to Buddy, make sure the `BUDDY_UT_TOKEN` environment variable is set correctly. You can find the token in the suite settings in Buddy. ### **Reporters or the CLI are not working. What is the cause?** If the reporters or CLI are not working, check your Node.js version - Buddy Unit Tests reporters and the CLI require Node.js 20 or higher: ```bash node --version # Check current version ``` ### **JUnit XML files are not being uploaded. How can I fix this?** If JUnit XML files are not being uploaded, verify the file paths and glob patterns in your CLI command or API calls. Use absolute paths whenever possible. ### **Test sessions remain open indefinitely. What should I do?** If test sessions remain open indefinitely: - Check the timeout settings in your suite configuration - For Cypress, make sure you run `closeSession()` after the tests finish - Verify that your test runner properly exits after completion ### **Error patterns or placeholders are showing empty values. How do I fix this?** If error patterns or placeholders show empty values, make sure your JUnit XML files contain all the required fields. Check that the XML structure matches the format expected by Buddy. ### **GitHub commit checks are not appearing. What should I do?** If GitHub commit checks are not appearing: - Verify that the GitHub integration toggle is enabled in the Suite Settings - Make sure the suite name matches the expected check context pattern: `/buddy/tests/` - Check that your GitHub token has the required permissions ### **Playwright: “Executable doesn’t exist” - What should I do?** If you encounter the `browserType.launch: Executable doesn't exist` error, it means that the Playwright browsers are not installed. Run: ```bash npx playwright install ``` --- Original source: https://buddy.works/docs/tests/unit-tests/troubleshooting