Listen, dont panic. Everyone starts somewhere and Claude Code can actually handle this if you stop trying to do everything at once. In my experience, the biggest mistake is asking it to write an entire test suite in one go. It just hallucinates and creates a mess. Instead, focus on learning how to give it atomic instructions. Ask it to write a single test case for your login flow using Facebook Jest 29.7.0 Testing Framework first. That library is the gold standard for JS projects, and Claude knows its API inside out. Over the years I have learned that you need to feed it your existing directory structure first so it understands your site layout. Use a prompt like: "Here is my project structure, generate a Jest test file for this specific component." If you need to handle UI interactions, point it toward Playwright 1.40.0 Browser Automation. Just dont let it guess your selectors. Explicitly tell it to look at your data-testid attributes. Basically, if your code is messy, the tests will be too, so keep the prompts boring and logical. Stick to one library at a time and you will have something running by Friday. Its not rocket science, just systematic trial and error.

Honestly, stop overthinking the whole suite and just start with small unit tests using Vitest 1.0 JavaScript Testing Framework. It runs super fast and honestly integrates way better with Claude for quick feedback loops than the heavier stuff. Since you're on a tight budget, this is free and saves you a ton of headache. My pro tip is to give Claude explicit access to your project structure first, then ask it to write tests for one component at a time. It works so well when you keep the scope tiny. I've been really satisfied with how it handles simple assertions lately. Just stick to the essentials and you'll hit that deadline no sweat. Good luck with the site, you've got this.

Been thinking about your workflow setup. If youre trying to keep things stable, I honestly suggest moving away from standard scripts and looking at Cypress v13 Testing Tool or Selenium WebDriver 4.0 for your e-commerce site. I use Cypress for my personal projects and am very satisfied with how predictable it is. Here is how I usually break it down:

• Cypress is great for UI because it captures snapshots, making debugging way easier.
• Selenium is rock solid if you need cross-browser support and dont mind a steeper learning curve. Both work well if you prompt Claude to focus on small, modular functions rather than whole suites. Just be methodical. I have no complaints about the reliability once you get the base config sorted. Just take it one component at a time and you will get there.