Skip to content

Testing extension gets the same test included twice in case of debugging 1 test #245927

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

Open
matepek opened this issue Apr 8, 2025 · 2 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug testing Built-in testing support

Comments

@matepek
Copy link

matepek commented Apr 8, 2025

Does this issue occur when all extensions are disabled?: Yes/No

  • VS Code Version: 1.99.0 (Universal)
  • OS Version: 15.4 (24E248)

Steps to Reproduce:

  1. Maybe coming with other adapter but surely coming with matepek.vscode-catch2-test-adapter so install that.
  2. Try to debug 1 test of a cpp test executable. (I can provide mac version if you need)
  3. The adapter getting createRunProfile callback with the same test included twice.
Image

TestMate C++ currently only allows to debug one test at a time so this caused issue in the previous version. There is a workaround now but still quite suspicious. relates

Let me know if you need further info.

Bests,

@roblourens roblourens assigned connor4312 and unassigned roblourens Apr 8, 2025
@connor4312 connor4312 added bug Issue identified by VS Code Team member as probable bug testing Built-in testing support labels Apr 8, 2025
@connor4312
Copy link
Member

Haven't given your adapter a spin but to double check: do you see the single ➡️ play button beside your test, or is it stacked? If the latter that means we actually do see two tests at that location, and the default behavior of actioning on that will be to run both

@matepek
Copy link
Author

matepek commented Apr 9, 2025

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug testing Built-in testing support
Projects
None yet
Development

No branches or pull requests

3 participants