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

Update test results in CMake Test Explorer #2522

Open
BMBurstein opened this issue Apr 25, 2022 · 6 comments
Open

Update test results in CMake Test Explorer #2522

BMBurstein opened this issue Apr 25, 2022 · 6 comments
Labels
enhancement an enhancement to the product that is either not present or an improvement to an existing feature Feature: ctest help wanted we currently are not planning work on this and would like help from the open source community
Projects
Milestone

Comments

@BMBurstein
Copy link

Issue Type: Feature Request

I use the CMake Tools status bar to run all tests with one click, and I use the CMake Test Explorer extension to run and see results from individual tests. It woud be great if running the tests via one of the methods would update the test results in the other as well.

I don't know exactly how this works, but I think the CMake Test Explorer uses some kind of standard VSCode api to manage and display tests, so I am guessing this extension would need to use the same api for updating the test results.

Extension version: 1.10.5
VS Code version: Code 1.66.2 (dfd34e8260c270da74b5c2d86d61aee4b6d56977, 2022-04-11T07:46:01.075Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No
Remote OS version: Linux x64 5.4.0-109-generic

@bobbrow
Copy link
Member

bobbrow commented Apr 26, 2022

We have an issue tracking doing a test explorer #1682, but it hasn't made it on the roadmap yet. Does the Test Explorer extension have a way to run tests in a single click or command? If it does have a way to run tests easily, I would recommend hiding our status bar button using the following setting:

"cmake.statusbar.advanced": {
  "ctest": {
    "visibility": "hidden"
  }
}

@bobbrow bobbrow closed this as completed Apr 26, 2022
@bobbrow bobbrow added duplicate a duplicate of an already present issue Feature: ctest enhancement an enhancement to the product that is either not present or an improvement to an existing feature labels Apr 26, 2022
@bobbrow
Copy link
Member

bobbrow commented Apr 26, 2022

It looks like there is a Test Explorer: Run all tests command that you could bind to a keyboard shortcut. Or you could use the play button in the Test Explorer panel.

@BMBurstein
Copy link
Author

@bobbrow That doesn't rebuild or refresh the list of tests automatically. Using the button in the status bar also rebuilds and always runs all tests, including any new ones.

@bobbrow
Copy link
Member

bobbrow commented Apr 27, 2022

I see. We'll have to look into whether it makes sense for us to run their command on your behalf if we detect the extension is present. I'll reopen this issue to cover that angle. Just to set expectations though, we may not get to this immediately but will track upvotes (👍). We'd also accept a PR if someone wants to take a look as well.

@bobbrow bobbrow reopened this Apr 27, 2022
@bobbrow bobbrow added the help wanted we currently are not planning work on this and would like help from the open source community label Apr 27, 2022
@BMBurstein
Copy link
Author

Thank you. I understand that this is a low priority, but maybe if it is on the list someone will look into it. Maybe the two extensions can even be merged in some way if it makes sense.
I am sorry that I am asking for this and not offering to do it myself, but I am a C++ programmer and know nothing of JS or Typescript or whatever else is needed for this.

@bobbrow bobbrow removed the duplicate a duplicate of an already present issue label Feb 6, 2023
@cvanbeek13
Copy link
Contributor

I'm also hoping to see this feature implemented. I tried using a custom keybinding to rebuild and refresh the tests. Then it would run Test: Run all tests. However, another issue is that Test: Run all tests runs everything sequentially, so it takes forever as the test suite grows.

With the cmake.ctest command, I can run tests in parallel, it's just frustrating that it doesn't update the Test Explorer with the results.

@gcampbell-msft gcampbell-msft added this to Triage in 1.16 via automation Aug 16, 2023
@gcampbell-msft gcampbell-msft added this to the 1.16 milestone Aug 16, 2023
@benmcmorran benmcmorran modified the milestones: 1.16, 1.17 Oct 4, 2023
@gcampbell-msft gcampbell-msft added this to Triage in 1.17 via automation Nov 20, 2023
@gcampbell-msft gcampbell-msft removed this from Triage in 1.16 Nov 20, 2023
@gcampbell-msft gcampbell-msft modified the milestones: 1.17, On Deck Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement an enhancement to the product that is either not present or an improvement to an existing feature Feature: ctest help wanted we currently are not planning work on this and would like help from the open source community
Projects
Status: Pending Prioritization
1.17
Triage
Development

No branches or pull requests

5 participants