Skip to content

Refactor Needed for "Run Separately" Method (JUnit 5) #24

@luoos

Description

@luoos

To gain full control of test execution order, the current implementation is to run test "separately". There are at least two drawbacks of this method:

  1. @BeforAll/@AfterAll method will execute multiple times. This violates the intention of it, i.e., that method should only run once for all tests in the same test class. And it could lead to some unexpected results.
  2. It brings some performance overhead. But this issue is minor.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions