Skip to content

Support for behave which is running on parallel mode - now allure-results directory is creating empty. #321

Description

@testingplusme

I'm submitting a ...

  • bug report
  • [] feature request
  • support request => Please do not submit support request here, see note at the top of this template.

What is the current behavior?

When I'm using behave from this branch behave/behave#710 (where is possible to use behave in the parallel mode) directory allure-results is creating empty.

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

I used this command
behave --processes 3 --parallel-element feature -f allure_behave.formatter:AllureFormatter -o allure_test_results ./features

and after run this folder is creating but empty when I'm using behave without --processes 3 --parallel-element feature that allure-results directory is creating correctly.

What is the expected behavior?

That Allure works in other forks when there is parallel support so it will be very helpful to have this possibility also for behave.

What is the motivation / use case for changing the behavior?

Parallel run of tests is one of the most important thing in my opinion because always we want to decrease execution time.

Please tell us about your environment:

  • Allure version: 2.8.0
  • Test framework: behave 1.2.7.dev0
  • Allure adaptor: allure-behave@2.5.4

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions