search

hrcorval / behavex

BDD test wrapper on top of Behave for parallel test executions and more!
https://github.com/hrcorval/behavex
MIT License
81 stars 19 forks source link

JUnit XML is always per feature #127

Open gridranger opened 2 months ago

gridranger commented 2 months ago

Describe the bug The README states: "By default, there will be one JUnit file per feature, unless the parallel execution is performed by scenario, in which there will be one JUnit file per scenario."

To Reproduce python -m behavex tests --parallel-processes 4 --parallel-scheme scenario

Expected behavior Having 2 JUnit XML files as I have 2 scenarios in my feature file.

Screenshots behavex

Desktop (please complete the following information):

Additional context the feature file's content:

@web @duckduckgo
Feature: Basic web search
  As a web surfer,
  I want to find information online,
  So I can learn new things and get tasks done.

  @webtest @firefox
  Scenario: More Basic DuckDuckGo Search
    Given the DuckDuckGo home page is displayed
    When the user searches for "dog"
    Then results are shown for "dog"

  Scenario: Other DuckDuckGo Search
    Given the DuckDuckGo home page is displayed
    When the user searches for "cat"
    Then results are shown for "cat"

PS: Great job on the library by the way :)

hrcorval commented 2 weeks ago

Hi @gridranger, We realize this is an issue in the documentation, as the junit files will always be generated at feature level. We will update the documentation accordingly. Thanks!!