GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Support for behave which is running on parallel mode - now allure-results directory is creating empty. · Issue #321 · allure-framework/allure-python

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

New issue
Copy link
New issue
Copy link
Closed
Closed
Support for behave which is running on parallel mode - now allure-results directory is creating empty.#321
#84 (+9)
Copy link
Labels
theme:behavetype:enhancementwork:in progress

Description

@testingplusme
testingplusme
opened on Dec 18, 2018
Issue body actions

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: [email protected]
Reacted by Adam and GowriShankariSurendran

Activity

Next
  1. yuriandreyev commented on Jan 24, 2019

    @yuriandreyev
    yuriandreyev
    on Jan 24, 2019
    More actions

    We use this Behave-Allure adapter https://pypi.org/project/allure2-behave/ https://github.com/DaulGitHub/allure-behave
    Allure report is successfully generated even if behave tests were run in parallel mode.

    Reacted by Daulet
  2. testingplusme commented on Jan 24, 2019

    @testingplusme
    testingplusme
    on Jan 24, 2019
    Author
    More actions

    @yuriandreyev thank you. Is it also possible to have access to allure.attach() method? Or maybe you have any wrapper method for it?

  3. sseliverstov
    added
    work:selected for dev
    theme:behave
    type:enhancement
    on Jan 24, 2019
  4. sseliverstov
    closed this as completedin #342on Jan 24, 2019
  5. sseliverstov
    added a commit that references this issue on Jan 24, 2019

    workaround for PR with parallel support (fixes #321 via #342)

    This issue will close once commit 5e9128b is merged into the 'master' branch.
    5e9128b
  6. DauletMavlonazarov commented on Jan 28, 2019

    @DauletMavlonazarov
    DauletMavlonazarov
    on Jan 28, 2019
    More actions

    @yuriandreyev thank you. Is it also possible to have access to allure.attach() method? Or maybe you have any wrapper method for it?

    @testingplusme code example how to use attachments https://github.com/DaulGitHub/allure-behave/blob/master/example/features/environment.py

  7. sseliverstov commented on Jan 28, 2019

    @sseliverstov
    sseliverstov
    on Jan 28, 2019
    Contributor
    More actions

    @testingplusme hi, can you check this issue with v2.5.5? Tnx!

    Reacted by Michał
  8. testingplusme commented on Jan 28, 2019

    @testingplusme
    testingplusme
    on Jan 28, 2019
    Author
    More actions

    @DaulGitHub thanks for your reply.
    @sseliverstov Thank you. I tried it. Unfortunately, still it's creating empty folder :( Ofc, I used the new version of allure-behave and allure-python-commons and behave from branch behave/behave#616 .

  9. sseliverstov
    reopened this on Jan 28, 2019
  10. sseliverstov commented on Jan 28, 2019

    @sseliverstov
    sseliverstov
    on Jan 28, 2019
    Contributor
    More actions

    @testingplusme python version?

  11. testingplusme commented on Jan 28, 2019

    @testingplusme
    testingplusme
    on Jan 28, 2019
    Author
    More actions

    @sseliverstov 3.7

  12. testingplusme commented on Feb 5, 2019

    @testingplusme
    testingplusme
    on Feb 5, 2019
    Author
    More actions

    @sseliverstov Did you look at ? ^ ^

  13. Ljancek commented on Feb 5, 2019

    @Ljancek
    Ljancek
    on Feb 5, 2019
    More actions

    I have some issue with

    • python: 2.7.15,
    • allure-behave: 2.5.5,
    • allure-python-commons: 2.5.5
    • behave: 1.2.7.dev0 from behave/behave#616
  14. 18 remaining items

  15. skhomuti
    added a commit that references this issue on Nov 18, 2020

    workaround for PR with parallel support (fixes allure-framework#321 via

    This issue will close once commit 0c1ee01 is merged into the 'master' branch.
    0c1ee01
  16. Khouloud-moalla commented on May 24, 2022

    @Khouloud-moalla
    Khouloud-moalla
    on May 24, 2022
    More actions

    We use this Behave-Allure adapter https://pypi.org/project/allure2-behave/ https://github.com/DaulGitHub/allure-behave Allure report is successfully generated even if behave tests were run in parallel mode.

    I did not find a result ! Can you help me more !

  17. DauletMavlonazarov commented on May 25, 2022

    @DauletMavlonazarov
    DauletMavlonazarov
    on May 25, 2022
    More actions

    We use this Behave-Allure adapter https://pypi.org/project/allure2-behave/ https://github.com/DaulGitHub/allure-behave Allure report is successfully generated even if behave tests were run in parallel mode.

    I did not find a result ! Can you help me more !

    Please run tests as in the example https://github.com/DaulGitHub/allure-behave/tree/master/example
    As a result, the folder allure-report should appear. https://github.com/DaulGitHub/allure-behave/blob/master/example/features/environment.py#L10

    If folder not appeared please write me.

  18. Khouloud-moalla commented on May 26, 2022

    @Khouloud-moalla
    Khouloud-moalla
    on May 26, 2022
    More actions

    Daul I want this
    Generate reports with allure behave: My Test will be executed on several browsers in parallel so when I generated the report i will have two reports but whithout the name of browser in file.json . What I want doing to know which report belongs to which browser !! heelp me please

  19. DauletMavlonazarov commented on May 26, 2022

    @DauletMavlonazarov
    DauletMavlonazarov
    on May 26, 2022
    More actions

    Daul I want this Generate reports with allure behave: My Test will be executed on several browsers in parallel so when I generated the report i will have two reports but whithout the name of browser in file.json . What I want doing to know which report belongs to which browser !! heelp me please

    You should change output report directory name https://github.com/DaulGitHub/allure-behave/blob/master/example/features/environment.py#L10 for every test run.
    for example: report_dir_name = "allure-report-firefox"
    report_dir_name = "allure-report-chrome" etc

    I hope it will help you.

  20. Khouloud-moalla commented on May 26, 2022

    @Khouloud-moalla
    Khouloud-moalla
    on May 26, 2022
    More actions

    I want that the name of browser to be written automaticcaly in report.json file generated right after every test and for every test the browser is not always the same !!

  21. DauletMavlonazarov commented on May 26, 2022

    @DauletMavlonazarov
    DauletMavlonazarov
    on May 26, 2022
    More actions

    Just change variable report_dir_name for every test run. I do not see problem.
    May be I didn`t fully understand the task.

  22. Khouloud-moalla commented on May 26, 2022

    @Khouloud-moalla
    Khouloud-moalla
    on May 26, 2022
    More actions

    ok i will try to explain more: i'm generating my reports with this command
    sh('SET CONFIG_FILE=config/%s.json & SET TASK_ID=%s & behave -f allure_behave.formatter:AllureFormatter -o reports features/project.feature ' % (config, task_id, feature3))
    it executes tests in 2 different browsers in paralell and for every browser it generates a .json report file .
    My problem is i want to know each .json file belongs to which browser and i want to add the name of the browser in the .json file

  23. DauletMavlonazarov commented on May 27, 2022

    @DauletMavlonazarov
    DauletMavlonazarov
    on May 27, 2022
    More actions

    ok i will try to explain more: i'm generating my reports with this command sh('SET CONFIG_FILE=config/%s.json & SET TASK_ID=%s & behave -f allure_behave.formatter:AllureFormatter -o reports features/project.feature ' % (config, task_id, feature3)) it executes tests in 2 different browsers in paralell and for every browser it generates a .json report file . My problem is i want to know each .json file belongs to which browser and i want to add the name of the browser in the .json file

    Ok, I understand problem.

    1. We are talking about two different repository. You mean this repository https://github.com/allure-framework/allure-python, but I mean this repository https://github.com/DaulGitHub/allure-behave. It is two different repositories and different different methods for generating a report
    2. you misled me with a quote in this question Support for behave which is running on parallel mode - now allure-results directory is creating empty. #321 (comment)
      Do you see, it is my alternative repository https://github.com/DaulGitHub/allure-behave
    3. Now to solve your question you have to ask a question or create issue in this repository https://github.com/allure-framework/allure-python

    Regards Daulet!)

  24. Khouloud-moalla commented on May 27, 2022

    @Khouloud-moalla
    Khouloud-moalla
    on May 27, 2022
    More actions

    2. you misled me with a quote in this question

    I'made my issue in the repository which say to me but without any response :( 3 days without any help and any response

  25. DauletMavlonazarov commented on May 27, 2022

    @DauletMavlonazarov
    DauletMavlonazarov
    on May 27, 2022
    More actions

    3 days without any help and any response

    It is sad!

    1. you can ask the question in the Allure framework community https://qameta.io/allure-report/ Push on a button "community".
    2. Also you can use my repository https://github.com/DaulGitHub/allure-behave , but I do not use it long time.

    I wish you good luck!

    Reacted by khouloud moalla
  26. Khouloud-moalla commented on May 27, 2022

    @Khouloud-moalla
    Khouloud-moalla
    on May 27, 2022
    More actions

    3 days without any help and any response

    It is sad!

    1. you can ask the question in the Allure framework community https://qameta.io/allure-report/ Push on a button "community".
    2. Also you can use my repository https://github.com/DaulGitHub/allure-behave , but I do not use it long time.

    I wish you good luck!

    In any case thank you

  27. beckerGil
    added a commit that references this issue on Apr 10, 2023

    workaround for PR with parallel support (fixes allure-framework#321 via

    This issue will close once commit f9ee1e3 is merged into the 'master' branch.
    f9ee1e3
  28. IvanBuruyane
    added 2 commits that reference this issue on Mar 19, 2024

    workaround for PR with parallel support (fixes allure-framework#321 via

    This issue will close once commit 9c2c42a is merged into the 'master' branch.
    9c2c42a

    add hook implementation (fixes allure-framework#321 fixes allure-fram…

    This issue will close once commit f1533b3 is merged into the 'master' branch.
    f1533b3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    theme:behavetype:enhancementwork:in progress

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402520 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.