Run test teardown methods (JUnit `@AfterEach`/`@AfterAll`) when stopped manually?

Open
#1,666 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java, typescript
Domain
testing

Research direction

The issue names no file, test, or entry point. First clarify whether manual stops should run JUnit @AfterEach and @AfterAll, then trace the extension's manual-stop behavior and define how completion should be verified for cleanup involving external services.

Written by the indexing model from the issue text.

Description

ai-triaged enhancement

Does this extension run teardown methods when a user manually stops a test run? I think the answer is no, but thought I'd check if it was meant to first and I just had something misconfigured.

If not, should it? Coming from Eclipse, stopping a test did run the teardown logic (at least for JUnit @AfterEach and @AfterAll). I do find a lot of the time I want teardown methods to fire on a manual stop, especially for system integration tests that communicate with external services during cleanup.

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.