Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Copilot shouldn't prompt to set up test suite when one already exists #2748

Open
zubin opened this issue Nov 20, 2024 · 2 comments
Open

Copilot shouldn't prompt to set up test suite when one already exists #2748

zubin opened this issue Nov 20, 2024 · 2 comments
Assignees

Comments

@zubin
Copy link

zubin commented Nov 20, 2024

Type: Bug

When I asked to perform a task and write tests, Copilot said that tests weren't set up and wanted to set up RSpec. It's an established code base with extensive tests. RSpec is already well and truly set up!

Extension version: 0.22.4
VS Code version: Code 1.95.3 (Universal) (f1a4fb101478ce6ec82fe9627c43efbf9e98c813, 2024-11-13T14:50:04.152Z)
OS version: Darwin arm64 24.1.0
Modes:

System Info
Item Value
CPUs Apple M3 Pro (11 x 2400)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) 2, 2, 2
Memory (System) 36.00GB (0.78GB free)
Process Argv --crash-reporter-id a6886e66-a4e4-4ccc-9140-36e99573713d
Screen Reader no
VM 0%
A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
vscaac:30438847
c4g48928:30535728
azure-dev_surveyonecf:30548226
962ge761:30959799
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
724cj586:31013169
dvdeprecation:31068756
dwnewjupyter:31046869
2f103344:31071589
nativerepl1:31139838
pythonrstrctxt:31112756
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530

@github-actions github-actions bot added the triage-needed Issues needing to be assigned to the prospective feature owner label Nov 20, 2024
@lramos15 lramos15 assigned connor4312 and unassigned lramos15 Nov 21, 2024
@lramos15 lramos15 removed the triage-needed Issues needing to be assigned to the prospective feature owner label Nov 21, 2024
@connor4312
Copy link
Member

The initial detection is based on whether you have a testing extension installed yet. If you action through it, it should recommend an extension to install. Otherwise, if you ignore, it should go away.

@connor4312 connor4312 added info-needed Issue requires more information from poster under-discussion Issue is under discussion for relevance, priority, approach labels Dec 11, 2024
@zubin
Copy link
Author

zubin commented Dec 15, 2024

The initial detection is based on whether you have a testing extension installed yet. If you action through it, it should recommend an extension to install. Otherwise, if you ignore, it should go away.

Gotcha. Maybe the messaging should indicate that it's referring to installing an extension, rather than setting up RSpec.

@connor4312 connor4312 added polish /tests and removed info-needed Issue requires more information from poster under-discussion Issue is under discussion for relevance, priority, approach labels Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants