What happened?
I'm submitting a ...
What is the current behavior?
Unexpected logs appear in the IntelliJ console after running tests that use the JUnit5 @BeforeAll annotation. I tried changing the Allure version from 2.29.0 to 2.24.0, but the issue persists.
This issue has already been mentioned in:
Steps to reproduce:
import org.junit.jupiter.api.BeforeAll;
import org.junit.jupiter.params.ParameterizedTest;
import org.junit.jupiter.params.provider.ValueSource;
public class UnnessaryLogsTest {
@BeforeAll
static void beforeAll() {
}
@ParameterizedTest
@ValueSource(ints = {1, 3, 5, -3, 15, Integer.MAX_VALUE})
void test(int number) {
}
}
Additionally, I have added the following property in junit-platform.properties:
junit.jupiter.extensions.autodetection.enabled=true
Please tell us about your environment:
| Type |
Dependency |
Version |
| Allure |
|
2.29.0 |
| Test framework |
JUnit 5 |
5.11.3 |
| Allure integration |
allure-junit5 |
2.29.0 |
| Generate report using |
allure-maven |
2.15.2 |
| IDE |
Intellij |
2024.3.1.1 |
| Build tool |
Maven |
3.9.9 |
| Java |
|
22 |
Other information
example:
timestamp = 2024-12-23T21:35:50.852486500, allure.parameter = arg0, value = 1
timestamp = 2024-12-23T21:35:50.852486500, allure.parameter = arg0, value = 2147483647
What Allure Integration are you using?
allure-junit5
What version of Allure Integration you are using?
2.29.0
What version of Allure Report you are using?
2.29.0
Code of Conduct
What happened?
I'm submitting a ...
What is the current behavior?
Unexpected logs appear in the IntelliJ console after running tests that use the JUnit5
@BeforeAllannotation. I tried changing the Allure version from 2.29.0 to 2.24.0, but the issue persists.This issue has already been mentioned in:
Steps to reproduce:
Additionally, I have added the following property in junit-platform.properties:
Please tell us about your environment:
Other information
What Allure Integration are you using?
allure-junit5
What version of Allure Integration you are using?
2.29.0
What version of Allure Report you are using?
2.29.0
Code of Conduct