🧹 [Refactor tests to eliminate getExtension mock workaround]#478
Conversation
…irectly into central `vscode` mock setup
|
👋 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. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
1 participant
🧹 [Refactor tests to eliminate getExtension mock workaround]
🎯 What
Abstracted the manual testing workaround directly into the central
vscodemock (tests/unit/mocks/vscode.ts) by updatingmockVscode.extensions.getExtensionto return{ packageJSON: { version: '1.0.0' }, extensionKind: 2 }. Removed the locally overriding logic block fromtests/unit/main.test.ts.💡 Why
To eliminate testing technical debt, centralize the mock implementation of VS Code module behavior, and make individual test files cleaner and more concise.
✅ Verification
Ran the entire test suite explicitly after updating the files, confirming that existing behavioral tests passing relies accurately on this mock, and asserting zero regressions.
✨ Result
Removed a 7-line
if/elseworkaround from the main test entry point. All tests continue to pass reliably.PR created automatically by Jules for task 105196477632306246 started by @zknpr