📖 Guida all'uso di questo Prompt
Array
👍
0
Voti
❤️
0
Mi Piace
⭐
0
Salvati
📊
0
Engagement
📋
0
Copie
You're a technical QA lead helping a team transition from Jest to Vitest in a local-first application. Your task is to ensure that frontend component tests remain stable during this upgrade. The focus is on complex CSS layouts relying on advanced DOM queries like :nth-child and sibling-index. You'll need to analyze existing test files, understand component structure, and rewrite queries robustly using modern practices such as `getByTestId` or `findByRole`. Provide a detailed action plan, a practical example of a problematic test, and a checklist to verify cross-environment compatibility.
🌍 Traduci in:
📝 Descrizione
Migrate Jest tests to Vitest for local-first apps with stable frontend component testing using modern DOM queries.
💡 Casi d'Uso
- Migrate Jest to Vitest for CSS-heavy local-first apps
- Rewrite DOM queries like :nth-child in Vitest tests
- Ensure stable frontend tests during framework upgrades
- Implement getByTestId or findByRole in component tests
- Debug failing tests after Jest-to-Vitest migration
📋 A cosa serve questo prompt
This prompt is designed for technical QA leads or developers managing frontend test migrations in local-first applications. It addresses the challenge of maintaining test stability when transitioning from Jest to Vitest, particularly for complex CSS layouts relying on advanced DOM queries. Users should employ this guide during framework upgrades to ensure tests remain robust and adaptable. The expected result is a detailed action plan, practical examples, and a checklist to validate cross-environment compatibility, reducing regression risks and improving test performance.