[Allure-JUnit5] Unexpected logs in terminal

[romsper]

I added those dependencies to my project and they started to write unexpected logs to my terminal.

I'm submitting a ...

Bug to @eroshenkoam from Allure chat in Telegram

What is the current behavior?

I see these rows in my logs: timestamp = 2020-09-17T14:18:40.851, name = closeBrowser, allure.fixture = tear_down, event = start, uuid = 9998a546-eabe-4abc-9170-cc57e0c455fa and they duplicate many times

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

Just add those dependencies

Please tell us about your environment:

<allure-junit5.version>2.13.5</allure-junit5.version>
<dependency>
            <groupId>io.qameta.allure</groupId>
            <artifactId>allure-junit5</artifactId>
            <version>${allure-junit5.version}</version>
        </dependency>
        <dependency>
            <groupId>io.qameta.allure</groupId>
            <artifactId>allure-okhttp3</artifactId>
            <version>${allure-junit5.version}</version>
        </dependency>

Other information

INFO: Detected dialect: W3C
timestamp = 2020-09-17T14:18:14.786, allure.fixture = prepare, event = stop, uuid = 318aad45-8e0b-48ac-9bbe-fb097b5e5e1ctimestamp = 2020-09-17T14:18:14.787, name = prepareData, allure.fixture = prepare, event = start, uuid = ba3d4700-e7b5-4260-8285-028b0445cd99log4j:WARN No appenders could be found for logger (freemarker.cache).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
timestamp = 2020-09-17T14:18:18.233, allure.fixture = prepare, event = stop, uuid = ba3d4700-e7b5-4260-8285-028b0445cd99timestamp = 2020-09-17T14:18:40.521, name = deletePreparedData, allure.fixture = tear_down, event = start, uuid = b6c87365-c719-4a79-824d-23479802d0a4timestamp = 2020-09-17T14:18:40.741, allure.fixture = tear_down, event = stop, uuid = b6c87365-c719-4a79-824d-23479802d0a4timestamp = 2020-09-17T14:18:40.741, name = clearBrowser, allure.fixture = tear_down, event = start, uuid = 3615a6e2-44c1-413c-8c3e-e5bc931ad5fatimestamp = 2020-09-17T14:18:40.811, allure.fixture = tear_down, event = stop, uuid = 3615a6e2-44c1-413c-8c3e-e5bc931ad5faFinish: Create channel post
timestamp = 2020-09-17T14:18:40.851, name = closeBrowser, allure.fixture = tear_down, event = start, uuid = 9998a546-eabe-4abc-9170-cc57e0c455fatimestamp = 2020-09-17T14:18:40.916, allure.fixture = tear_down, event = stop, uuid = 9998a546-eabe-4abc-9170-cc57e0c455fa```

Process finished with exit code 0`

[baev]

How do you run your tests? Using IDE?

[romsper]

@baev only in IDEA -> Maven doesn't show this row.

[baev]

yeah, check out is there an option in IDEA to disable logging of report entries. For details please check out issue I linked above

[scormaq]

hi @baev , any hints how to achieve disabling junit5 output in IDEA for now? I didn't find any useful info in the thread above... I'm using:

• junit 5.7.0
• allure 2.13.7
• IDEA 2020.3 CE

[baev]

As for now, report events are no longer logged by IDEA

[LucaLis]

Hi @baev ! Can you please provide info about versions of jUnit and Allure used to confirm that it's not an issue anymore?

[baev]

I use IDEA & JUnit 5 all the time (as Java is my primary language), and I last saw these messages a while ago. Let me double-check; maybe it's because we never use setup methods.

[baev]

Double-checked:

Allure 2.25.0 JUnit 5.10.1 IntelliJ IDEA 2023.3.5 (Ultimate Edition) Build #IU-233.14808.21, built on March 12, 2024

No messages. Tested using Allure Start (Java -> JUnit 5 -> Keep defaults -> add a @Before method)

[LucaLis]

@baev Thanks! I have a problem with change of IDEA version in my environment but now at least I know a setup that should work correctly.