microsoft / microsoft/vscode-java-test

Expose lists of tests to be usable in inputs of task.json

Open
#1,405 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ai-triaged enhancement maven test-discovery
Dominant language
TypeScript
Stars
340
Forks
173
Avg merge
1d 19h
Merged PRs (30d)
18

Description

I want to write a task like

"inputs": [
    {
      "id": "pickedTest",
      "type": "command",
      "command": "extension.yourextension.testPickerinCurrentFile",
    }
  ],

"tasks": [{
  "type": "shell",
  "command": "mvn -Dtest=${input:pickedTest} test -e",
  "label": "run test.."
}]

to be able to run any test(s) in current file or the entire workspace in my terminal instead of the debug console.

so if you exposed two commands

  • one for tests or test classes in current file
  • one for tests or test classes in entire workspace

with full classpath and/or methodname as output which can directly be fed to maven, I'd be grateful.

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.

Research direction

Start with the task.json input example and the requested current-file and workspace test commands, then review how Maven accepts classpath, class, and method-name output. Done means both commands expose test selections that can be substituted into the task and run from the terminal.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, typescript, vscode
Domain
testing, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.