Whether to run a test case filtered out by tags when I explicitly do

Open
#1,480 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java, typescript
Domain
testing

Research direction

Start by reproducing the behavior described in the issue using a test case filtered out by tags, then explicitly select that case and compare it with the recording. No file or test entry point is named, so trace the single-case execution path from the extension UI. Done means the intended behavior for an explicitly selected case is defined and the previous status is handled consistently.

Written by the indexing model from the issue text.

Description

ai-triaged enhancement test-execution ux

If a test case is filtered out by tags from settings, it won't run when I choose to run all the cases. It's ok.
However, when I explicit click on the case itself, want to run this single case, currently it still won't run. Should we ignore tag filters when explicitly run a single case?

This case looks stranger if previous status of the case is kept there, see the second half of the recording.

https://user-images.githubusercontent.com/2351748/187153016-16185df3-eca0-4a7a-94a0-1dbefed4d53c.mp4

Dominant language
TypeScript
Stars
340
Forks
173
Avg merge
1d 2h
Merged PRs (30d)
17

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vscode-java-test

All issues in microsoft/vscode-java-test

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.