allure-framework/allure-java

๐Ÿž: CompletableFuture. AllureLifecycle - Could not start step: no test case running

NewbieProger opened this issue ยท 2 comments

What happened?

If I put testStep into CompletableFuture I get errors and it doesn't execute

    @SuppressWarnings("rawtypes")
    @Test
    @DisplayName("Some test")
    void case_33() {
        SetUppreconditions();

        List<CompletableFuture> futureList = new ArrayList<>();
        for (int i = 0; i < 20; i++) {
            futureList.add(
                CompletableFuture.runAsync(() -> {
                    kafkaSteps.sendRequest(msg);
                })
            );
        }
        CompletableFuture.allOf(futureList.toArray(new CompletableFuture[0])).join();

        databaseRepostitory.assertCount(1);
    }
22:48:10.095 [ForkJoinPool.commonPool-worker-4] ERROR io.qameta.allure.AllureLifecycle - Could not start step: no test case running
22:48:10.095 [ForkJoinPool.commonPool-worker-3] ERROR io.qameta.allure.AllureLifecycle - Could not start step: no test case running
22:48:10.095 [ForkJoinPool.commonPool-worker-22] ERROR io.qameta.allure.AllureLifecycle - Could not start step: no test case running
22:48:10.095 [ForkJoinPool.commonPool-worker-24] ERROR io.qameta.allure.AllureLifecycle - Could not start step: no test case running
22:48:10.321 [ForkJoinPool.commonPool-worker-29] ERROR io.qameta.allure.AllureLifecycle - Could not update step: no step running
22:48:10.321 [ForkJoinPool.commonPool-worker-22] ERROR io.qameta.allure.AllureLifecycle - Could not update step: no step running
22:48:10.321 [ForkJoinPool.commonPool-worker-19] ERROR io.qameta.allure.AllureLifecycle - Could not update step: no step running
22:48:10.321 [ForkJoinPool.commonPool-worker-6] ERROR io.qameta.allure.AllureLifecycle - Could not update step: no step running

What Allure Integration are you using?

allure-junit5

What version of Allure Integration you are using?

2.22.22

What version of Allure Report you are using?

2.22.22

Code of Conduct

  • I agree to follow this project's Code of Conduct

Hello. We have the same issue