You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the vscode-meson should categorise test cases into test suite(s), if exists.
Steps:
I am using vscode-meson v1.24.0 with a C/C++ project (gtk)
Select VSCode's "Testing" feature from the Activity Bar
Observe a long list of test cases. The gtk project categorises the Meson test cases into Meson test suite(s). I think vscode‑meson should categorise too.
The text was updated successfully, but these errors were encountered:
cskeogh
added a commit
to cskeogh/vscode-meson
that referenced
this issue
Jun 30, 2024
Meson test cases may belong to test suite(s). If so, in VSCode's
"Testing" feature from the Activity Bar, add the test suite(s) as a
parent item and add the test cases as children.
The user has the choice to run all tests belonging to a test suite.
Will pass the test suite to the meson test command --suite. The option
--suite is needed to run test cases that the meson config purposely
excludes (for example, test suite "flaky").
Fixesmesonbuild#245
Quote the "test case" in the meson command, so can run test cases with a
space in the name. The quotes are needed because `cp.ExecFileOptions`
sets `shell=true`.
Fixesmesonbuild#256
Thank you for the great extension!
I think the vscode-meson should categorise test cases into test suite(s), if exists.
Steps:
The text was updated successfully, but these errors were encountered: