In our Yarn workspace, Copilot rarely suggests test files across packages; I've toggled settings but need practical fixes to surface test suggestions.
Tool mentioned: GitHub Copilot
1 approved answer
Try these fixes:
- Add a root tsconfig/jsconfig that includes all packages so the language server indexes tests.
- Open the monorepo root in VS Code (not a single package) so Copilot sees all files.
- Ensure tests use standard names (.test/.spec) and aren’t excluded by files.exclude or .gitignore.
- Update the Copilot extension, sign out/in, and enable inline suggestions.
More on Copilot vs alternatives: Compare GitHub Copilot and Cursor
Create an account or sign in to join this discussion and publish replies under your own forum profile.
Copilot suggestions lag or sometimes time out in our large TypeScript monorepo despite normal network checks. Looking for VS Code settings, extension conflicts, and memory tuning steps to…
Mid-level JavaScript dev testing Copilot vs ChatGPT for bug fixes, PR summaries, and unit-test generation inside VS Code; want trade-offs on accuracy, context handling, and IDE integration.
Developer using Copilot in a large monorepo and remote dev container experiences long latency for completions and occasional timeouts. Need stepwise diagnostics (network, extension, settings) and config changes…
We're adding automated unit/integration test generation into our CI pipeline and want tools that produce maintainable tests and PRs. Comparing Copilot code suggestions vs ChatGPT-driven test generation for…
