🧪 fix: use testInfo.outputPath for playwright screenshots#27
Conversation
Replaces hardcoded fixed file paths for screenshots with testInfo.outputPath() in verify-search.spec.ts to prevent collisions during parallel test execution.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…90430341770954550
This PR applies Copilot's suggestion to use
testInfo.outputPathin Playwright E2E tests instead of hardcoded output paths for screenshots. This change prevents issues during parallel test execution (fullyParallel) and avoids leaving untracked artifacts in the working tree.PR created automatically by Jules for task 2690430341770954550 started by @miccy