Bug 578570 - [Junit] junit-platform.properties > setting junit.jupiter.testclass.order.default not honored
Summary: [Junit] junit-platform.properties > setting junit.jupiter.testclass.order.def...
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.23   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-03 14:47 EST by Arthur Borsboom CLA
Modified: 2024-01-25 02:44 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arthur Borsboom CLA 2022-02-03 14:47:17 EST
Project type: J2EE
Functionality:

- [Run As] > [Junit Test] or
- [Coverage As] > [Junit Test] on project

JUnit offers configuration by a configuration file 'junit-platform.properties' in src/test/resources

In this case there is only one setting in the JUnit configuration file.

junit.jupiter.testclass.order.default=org.junit.jupiter.api.ClassOrderer$ClassName

This setting tells JUnit to execute the JUnit tests in class package alphabetical order.

When I run 'maven test' outside Eclipse by CLI, the setting is honored.
When I run JUnit tests inside Eclipse, this setting is not honored and all tests are executed in what seems to be random order.

This is a JUnit setting introduced in JUnit v5.8.0.

https://junit.org/junit5/docs/5.8.0/user-guide/index.html#writing-tests-test-execution-order-classes

Am I doing something wrong, or is this a bug in Eclipse/JUnit?
Comment 1 Eclipse Genie CLA 2024-01-25 02:44:17 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.