behavex 4.2.0__tar.gz → 4.2.2__tar.gz

{behavex-4.2.0/behavex.egg-info → behavex-4.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: behavex
-Version: 4.2.0
+Version: 4.2.2
 Summary: Agile testing framework on top of Behave (BDD).
 Home-page: https://github.com/hrcorval/behavex
 Author: Hernan Rey
@@ -56,6 +56,14 @@ Dynamic: requires-python
 
 # BehaveX Documentation
 
+## 📢 Important News
+
+**🎉 NEW: Allure Reports Integration!** *(Available since BehaveX 4.2.1)*
+
+BehaveX now provides seamless integration with Allure, the popular test reporting framework! Generate beautiful, comprehensive test reports with detailed evidence.
+
+[Learn more about Allure integration](#allure-reports-integration) 👈
+
 ## Table of Contents
 - [Introduction](#introduction)
 - [Features](#features)
@@ -66,8 +74,11 @@ Dynamic: requires-python
 - [Specific Arguments from BehaveX](#specific-arguments-from-behavex)
 - [Parallel Test Executions](#parallel-test-executions)
 - [Test Execution Reports](#test-execution-reports)
-- [Attaching Images and Evidence](#attaching-images-and-evidence)
-- [Test Logs and Metrics](#test-logs-and-metrics)
+- [Attaching Images to the HTML Report](#attaching-images-to-the-html-report)
+- [Attaching Additional Execution Evidence to the HTML Report](#attaching-additional-execution-evidence-to-the-html-report)
+- [Test Logs per Scenario](#test-logs-per-scenario)
+- [Metrics and Insights](#metrics-and-insights)
+- [Dry Runs](#dry-runs)
 - [Muting Test Scenarios](#muting-test-scenarios)
 - [Handling Failing Scenarios](#handling-failing-scenarios)
 - [Displaying Progress Bar in Console](#displaying-progress-bar-in-console)
@@ -76,20 +87,20 @@ Dynamic: requires-python
 
 ## Introduction
 
-**BehaveX** is a BDD testing solution designed to enhance your Behave-based testing workflow by providing additional features and performance improvements. It's particularly beneficial in the following scenarios:
+**BehaveX** is a BDD testing solution built on top of the Python Behave library, orchestrating parallel test sessions to enhance your testing workflow with additional features and performance improvements. It's particularly beneficial in the following scenarios:
 
 - **Accelerating test execution**: Significantly reduce test run times through parallel execution by feature or scenario.
 - **Enhancing test reporting**: Generate comprehensive and visually appealing HTML and JSON reports for in-depth analysis and integration with other tools.
 - **Improving test visibility**: Provide detailed evidence, such as screenshots and logs, essential for understanding test failures and successes.
 - **Optimizing test automation**: Utilize features like test retries, test muting, and performance metrics for efficient test maintenance and analysis.
-- **Managing complex test suites**: Handle large test suites with advanced features for organization, execution, and reporting.
+- **Managing complex test suites**: Handle large test suites with advanced features for organization, execution, and comprehensive reporting through multiple formats and custom formatters.
 
 ## Features
 
 BehaveX provides the following features:
 
 - **Parallel Test Executions**: Execute tests using multiple processes, either by feature or by scenario.
-- **Enhanced Reporting**: Generate friendly HTML and JSON reports that can be exported and integrated with third-party tools.
+- **Enhanced Reporting**: Generate comprehensive reports in multiple formats (HTML, JSON, JUnit) and utilize custom formatters like Allure for advanced reporting capabilities that can be exported and integrated with third-party tools.
 - **Evidence Collection**: Include images/screenshots and additional evidence in the HTML report.
 - **Test Logs**: Automatically compile logs generated during test execution into individual log reports for each scenario.
 - **Test Muting**: Add the `@MUTE` tag to test scenarios to execute them without including them in JUnit reports.
@@ -199,6 +210,9 @@ Execute BehaveX in the same way as Behave from the command line, using the `beha
 - **parallel-processes** (--parallel-processes): Specifies the number of parallel Behave processes.
 - **parallel-scheme** (--parallel-scheme): Performs parallel test execution by [scenario|feature].
 - **show-progress-bar** (--show-progress-bar): Displays a progress bar in the console during parallel test execution.
+- **formatter** (--formatter): Specifies a custom formatter for test reports (e.g., Allure formatter).
+- **formatter-outdir** (--formatter-outdir): Specifies the output directory for formatter results (default: output/allure-results for Allure).
+- **no-formatter-attach-logs** (--no-formatter-attach-logs): Disables automatic attachment of scenario log files to formatter reports.
 
 ## Parallel Test Executions
 
@@ -354,6 +368,8 @@ If you are printing logs in the console, you can configure the progress bar to d
 
 BehaveX provides integration with Allure, a flexible, lightweight multi-language test reporting tool. The Allure formatter creates detailed and visually appealing reports that include comprehensive test information, evidence, and categorization of test results.
 
+**Note**: Since BehaveX is designed to run tests in parallel, the Allure formatter processes the consolidated `report.json` file after all parallel test executions are completed. This ensures that all test results from different parallel processes are properly aggregated before generating the final Allure report.
+
 ### Prerequisites
 
 1. Install Allure on your system. Please refer to the [official Allure installation documentation](https://docs.qameta.io/allure/#_installing_a_commandline) for detailed instructions for your operating system.
@@ -372,6 +388,16 @@ By default, the Allure results will be generated in the `output/allure-results`
 behavex -t=@TAG --formatter=behavex.outputs.formatters.allure_behavex_formatter:AllureBehaveXFormatter --formatter-outdir=my-allure-results
 ```
 
+### Attaching Screenshots and Evidence to Allure Reports
+
+When using Allure reports, you should continue to use the same methods for attaching screenshots and evidence as described in the sections above:
+
+- **For screenshots**: Use the methods described in [Attaching Images to the HTML Report](#attaching-images-to-the-html-report) section. The `attach_image_file()` and `attach_image_binary()` methods from the `behavex_images` library will automatically work with Allure reports.
+
+- **For additional evidence**: Use the approach described in [Attaching Additional Execution Evidence to the HTML Report](#attaching-additional-execution-evidence-to-the-html-report) section. Files stored in the `context.evidence_path` will be automatically included in the Allure reports.
+
+The evidence and screenshots attached using these methods will be seamlessly integrated into your Allure reports, providing comprehensive test execution documentation.
+
 ### Viewing Allure Reports
 
 After running the tests, you can generate and view the Allure report using the following commands:
@@ -387,7 +413,11 @@ allure generate output/allure-results --output output/allure-report --clean --si
 allure generate output/allure-results --output output/allure-report --clean
 ```
 
-For more information about Allure reports, including features, customization options, and special tags you can use in your scenarios, please refer to the [official Allure documentation](https://docs.qameta.io/allure/).
+### Disabling Log Attachments
+By default, `scenario.log` files are attached to each scenario in the Allure report. You can disable this by passing the `--no-formatter-attach-logs` argument:
+```bash
+behavex --formatter behavex.outputs.formatters.allure_behavex_formatter:AllureBehaveXFormatter --no-formatter-attach-logs
+```
 
 ## Show Your Support
 

{behavex-4.2.0 → behavex-4.2.2}/README.md

@@ -8,6 +8,14 @@
 
 # BehaveX Documentation
 
+## 📢 Important News
+
+**🎉 NEW: Allure Reports Integration!** *(Available since BehaveX 4.2.1)*
+
+BehaveX now provides seamless integration with Allure, the popular test reporting framework! Generate beautiful, comprehensive test reports with detailed evidence.
+
+[Learn more about Allure integration](#allure-reports-integration) 👈
+
 ## Table of Contents
 - [Introduction](#introduction)
 - [Features](#features)
@@ -18,8 +26,11 @@
 - [Specific Arguments from BehaveX](#specific-arguments-from-behavex)
 - [Parallel Test Executions](#parallel-test-executions)
 - [Test Execution Reports](#test-execution-reports)
-- [Attaching Images and Evidence](#attaching-images-and-evidence)
-- [Test Logs and Metrics](#test-logs-and-metrics)
+- [Attaching Images to the HTML Report](#attaching-images-to-the-html-report)
+- [Attaching Additional Execution Evidence to the HTML Report](#attaching-additional-execution-evidence-to-the-html-report)
+- [Test Logs per Scenario](#test-logs-per-scenario)
+- [Metrics and Insights](#metrics-and-insights)
+- [Dry Runs](#dry-runs)
 - [Muting Test Scenarios](#muting-test-scenarios)
 - [Handling Failing Scenarios](#handling-failing-scenarios)
 - [Displaying Progress Bar in Console](#displaying-progress-bar-in-console)
@@ -28,20 +39,20 @@
 
 ## Introduction
 
-**BehaveX** is a BDD testing solution designed to enhance your Behave-based testing workflow by providing additional features and performance improvements. It's particularly beneficial in the following scenarios:
+**BehaveX** is a BDD testing solution built on top of the Python Behave library, orchestrating parallel test sessions to enhance your testing workflow with additional features and performance improvements. It's particularly beneficial in the following scenarios:
 
 - **Accelerating test execution**: Significantly reduce test run times through parallel execution by feature or scenario.
 - **Enhancing test reporting**: Generate comprehensive and visually appealing HTML and JSON reports for in-depth analysis and integration with other tools.
 - **Improving test visibility**: Provide detailed evidence, such as screenshots and logs, essential for understanding test failures and successes.
 - **Optimizing test automation**: Utilize features like test retries, test muting, and performance metrics for efficient test maintenance and analysis.
-- **Managing complex test suites**: Handle large test suites with advanced features for organization, execution, and reporting.
+- **Managing complex test suites**: Handle large test suites with advanced features for organization, execution, and comprehensive reporting through multiple formats and custom formatters.
 
 ## Features
 
 BehaveX provides the following features:
 
 - **Parallel Test Executions**: Execute tests using multiple processes, either by feature or by scenario.
-- **Enhanced Reporting**: Generate friendly HTML and JSON reports that can be exported and integrated with third-party tools.
+- **Enhanced Reporting**: Generate comprehensive reports in multiple formats (HTML, JSON, JUnit) and utilize custom formatters like Allure for advanced reporting capabilities that can be exported and integrated with third-party tools.
 - **Evidence Collection**: Include images/screenshots and additional evidence in the HTML report.
 - **Test Logs**: Automatically compile logs generated during test execution into individual log reports for each scenario.
 - **Test Muting**: Add the `@MUTE` tag to test scenarios to execute them without including them in JUnit reports.
@@ -151,6 +162,9 @@ Execute BehaveX in the same way as Behave from the command line, using the `beha
 - **parallel-processes** (--parallel-processes): Specifies the number of parallel Behave processes.
 - **parallel-scheme** (--parallel-scheme): Performs parallel test execution by [scenario|feature].
 - **show-progress-bar** (--show-progress-bar): Displays a progress bar in the console during parallel test execution.
+- **formatter** (--formatter): Specifies a custom formatter for test reports (e.g., Allure formatter).
+- **formatter-outdir** (--formatter-outdir): Specifies the output directory for formatter results (default: output/allure-results for Allure).
+- **no-formatter-attach-logs** (--no-formatter-attach-logs): Disables automatic attachment of scenario log files to formatter reports.
 
 ## Parallel Test Executions
 
@@ -306,6 +320,8 @@ If you are printing logs in the console, you can configure the progress bar to d
 
 BehaveX provides integration with Allure, a flexible, lightweight multi-language test reporting tool. The Allure formatter creates detailed and visually appealing reports that include comprehensive test information, evidence, and categorization of test results.
 
+**Note**: Since BehaveX is designed to run tests in parallel, the Allure formatter processes the consolidated `report.json` file after all parallel test executions are completed. This ensures that all test results from different parallel processes are properly aggregated before generating the final Allure report.
+
 ### Prerequisites
 
 1. Install Allure on your system. Please refer to the [official Allure installation documentation](https://docs.qameta.io/allure/#_installing_a_commandline) for detailed instructions for your operating system.
@@ -324,6 +340,16 @@ By default, the Allure results will be generated in the `output/allure-results`
 behavex -t=@TAG --formatter=behavex.outputs.formatters.allure_behavex_formatter:AllureBehaveXFormatter --formatter-outdir=my-allure-results
 ```
 
+### Attaching Screenshots and Evidence to Allure Reports
+
+When using Allure reports, you should continue to use the same methods for attaching screenshots and evidence as described in the sections above:
+
+- **For screenshots**: Use the methods described in [Attaching Images to the HTML Report](#attaching-images-to-the-html-report) section. The `attach_image_file()` and `attach_image_binary()` methods from the `behavex_images` library will automatically work with Allure reports.
+
+- **For additional evidence**: Use the approach described in [Attaching Additional Execution Evidence to the HTML Report](#attaching-additional-execution-evidence-to-the-html-report) section. Files stored in the `context.evidence_path` will be automatically included in the Allure reports.
+
+The evidence and screenshots attached using these methods will be seamlessly integrated into your Allure reports, providing comprehensive test execution documentation.
+
 ### Viewing Allure Reports
 
 After running the tests, you can generate and view the Allure report using the following commands:
@@ -339,7 +365,11 @@ allure generate output/allure-results --output output/allure-report --clean --si
 allure generate output/allure-results --output output/allure-report --clean
 ```
 
-For more information about Allure reports, including features, customization options, and special tags you can use in your scenarios, please refer to the [official Allure documentation](https://docs.qameta.io/allure/).
+### Disabling Log Attachments
+By default, `scenario.log` files are attached to each scenario in the Allure report. You can disable this by passing the `--no-formatter-attach-logs` argument:
+```bash
+behavex --formatter behavex.outputs.formatters.allure_behavex_formatter:AllureBehaveXFormatter --no-formatter-attach-logs
+```
 
 ## Show Your Support
 

{behavex-4.2.0 → behavex-4.2.2}/behavex/arguments.py

@@ -71,6 +71,7 @@ BEHAVEX_ARGS = [
     'show_progress_bar',
     'formatter',
     'formatter_outdir',
+    'formatter_attach_logs',
 ]
 
 
@@ -336,6 +337,15 @@ def parse_arguments(args):
         required=False,
     )
 
+    parser.add_argument(
+        '--no-formatter-attach-logs',
+        dest='formatter_attach_logs',
+        help="Do not attach scenario logs to the report formatter.",
+        action='store_false',
+        default=True,
+        required=False,
+    )
+
     # parser.add_argument('--logging-format',
     #                    help="Specify custom format to print statements. Uses "
     #                          " the same format as used by standard logging "

{behavex-4.2.0 → behavex-4.2.2}/behavex/environment.py

@@ -28,10 +28,12 @@ Context.__getattribute__ = create_custom_log_when_called
 
 hooks_already_set = False
 
+
 def _get_current_timestamp_ms():
     """Get current time as Unix epoch milliseconds."""
     return int(datetime.now().timestamp() * 1000)
 
+
 def extend_behave_hooks():
     """
     Extend Behave hooks with BehaveX hooks code.
@@ -106,7 +108,7 @@ def extend_behave_hooks():
 def before_all(context):
     """Setup up initial tests configuration."""
     try:
-        # Initialyzing log handler
+        # Initialize critical state variables to ensure consistent state
         context.bhx_log_handler = None
         context.bhx_inside_scenario = False
         # Store framework settings to make them accessible from steps
@@ -120,40 +122,68 @@ def before_feature(context, feature):
     try:
         context.bhx_execution_attempts = {}
         scenarios_instances = get_scenarios_instances(feature.scenarios)
+
         for scenario in scenarios_instances:
             scenario_tags = get_scenario_tags(scenario)
-            if get_param('dry_run'):
-                if 'MANUAL' not in scenario_tags:
-                    scenario.tags.append(u'BHX_MANUAL_DRY_RUN')
-                    scenario.tags.append(u'MANUAL')
+
+            # Handle dry run scenario tagging
+            if get_param('dry_run') and 'MANUAL' not in scenario_tags:
+                scenario.tags.extend(['BHX_MANUAL_DRY_RUN', 'MANUAL'])
+
+            # Configure scenario auto-retry
             configured_attempts = get_autoretry_attempts(scenario_tags)
             if configured_attempts > 0:
                 patch_scenario_with_autoretry(scenario, configured_attempts)
     except Exception as exception:
+        # Keep generic exception as fallback for truly unexpected errors
         _log_exception_and_continue('before_feature (behavex)', exception)
 
 
 def before_scenario(context, scenario):
     """Initialize logs for current scenario."""
+    # Initialize critical variables first to ensure they're always set
+    context.bhx_inside_scenario = True
+    # Initialize log handler to None to ensure it's always defined
+    context.bhx_log_handler = None
+
     try:
-        context.bhx_inside_scenario = True
+        # Handle execution attempts tracking
         if scenario.name not in context.bhx_execution_attempts:
             context.bhx_execution_attempts[scenario.name] = 0
         execution_attempt = context.bhx_execution_attempts[scenario.name]
         retrying_execution = True if execution_attempt > 0 else False
-
         # Calculate and store the scenario identifier hash
         scenario_identifier = f"{str(context.feature.filename)}-{str(scenario.line)}"
+        # Calculate the scenario identifier hash
         scenario.identifier_hash = get_string_hash(scenario_identifier)
-
-        context.log_path = create_log_path(scenario_identifier, retrying_execution)
+        # Create log path
+        context.log_path = create_log_path(scenario.identifier_hash, retrying_execution)
+        # Add log handler
         context.bhx_log_handler = _add_log_handler(context.log_path)
+        # Handle retry scenario cleanup
         if retrying_execution:
-            logging.info('Retrying scenario execution...\n'.format())
-            shutil.rmtree(context.evidence_path)
+            try:
+                logging.info('Retrying scenario execution...')
+                if hasattr(context, 'evidence_path') and context.evidence_path:
+                    try:
+                        shutil.rmtree(context.evidence_path)
+                    except FileNotFoundError:
+                        # Directory already removed by another process - this is fine
+                        pass
+                    except Exception as cleanup_ex:
+                        logging.warning(f"Failed to remove evidence directory {context.evidence_path}: {cleanup_ex}")
+            except Exception as retry_ex:
+                logging.warning(f"Failed to clean up evidence path during retry: {retry_ex}")
+        scenario.process_id = os.getpid()
+        if "config" in context and "worker_id" in context.config.userdata:
+            scenario.worker_id = context.config.userdata['worker_id']
+        else:
+            scenario.worker_id = str(os.getpid())
     except Exception as exception:
+        # Log the exception but ensure execution continues
         _log_exception_and_continue('before_scenario (behavex)', exception)
-    scenario.start = _get_current_timestamp_ms()
+    finally:
+        scenario.start = _get_current_timestamp_ms()
 
 
 def before_step(context, step):
@@ -191,9 +221,12 @@ def after_scenario(context, scenario):
             else:
                 global_vars.retried_scenarios[feature_name].append(scenario.name)
             context.bhx_execution_attempts[scenario.name] += 1
-        _close_log_handler(context.bhx_log_handler)
     except Exception as exception:
         _log_exception_and_continue('after_scenario (behavex)', exception)
+    finally:
+        # Always reset the scenario state flag, regardless of success or failure
+        _close_log_handler(context.bhx_log_handler)
+        context.bhx_inside_scenario = False
 
 
 # noinspection PyUnusedLocal
@@ -217,24 +250,31 @@ def after_all(context):
 
 def _add_log_handler(log_path):
     """Adding a new log handler to logger"""
-    log_filename = os.path.join(log_path, 'scenario.log')
-    file_handler = logging.FileHandler(
-        log_filename, mode='+a', encoding=LOGGING_CFG['file_handler']['encoding']
-    )
-    log_level = get_logging_level()
-    logging.getLogger().setLevel(log_level)
-    file_handler.addFilter(lambda record: setattr(record, 'msg', strip_ansi_codes(str(record.msg))) or True)
-    file_handler.setFormatter(_get_log_formatter())
-    logging.getLogger().addHandler(file_handler)
+    file_handler = None
+    try:
+        log_filename = os.path.join(log_path, 'scenario.log')
+        file_handler = logging.FileHandler(
+            log_filename, mode='+a', encoding=LOGGING_CFG['file_handler']['encoding']
+        )
+        log_level = get_logging_level()
+        logging.getLogger().setLevel(log_level)
+        file_handler.addFilter(lambda record: setattr(record, 'msg', strip_ansi_codes(str(record.msg))) or True)
+        file_handler.setFormatter(_get_log_formatter())
+        logging.getLogger().addHandler(file_handler)
+    except Exception as exception:
+        _log_exception_and_continue('_add_log_handler', exception)
     return file_handler
 
 
 def _close_log_handler(handler):
-    """Closing current log handlers and removing them from logger"""
+    """Closing current log handlers and removing them from logger."""
     if handler:
-        if hasattr(handler, 'stream') and hasattr(handler.stream, 'close'):
-            handler.stream.close()
-        logging.getLogger().removeHandler(handler)
+        try:
+            if hasattr(handler, 'stream') and hasattr(handler.stream, 'close'):
+                handler.stream.close()
+            logging.getLogger().removeHandler(handler)
+        except Exception as exception:
+            _log_exception_and_continue('_close_log_handler', exception)
 
 
 def _get_log_formatter():

{behavex-4.2.0 → behavex-4.2.2}/behavex/outputs/formatter_manager.py

@@ -69,10 +69,16 @@ class FormatterManager:
         Get the output directory for the custom formatter.
 
         Returns:
-            Absolute path to the formatter output directory
+            Absolute path to the formatter output directory, or None if no custom directory is specified
         """
         base_output = get_env('OUTPUT', 'output')
         formatter_outdir = get_param('formatter_outdir', '')
+
+        # Return None if no custom formatter output directory is specified
+        # This allows formatters to use their own default directories
+        if not formatter_outdir or formatter_outdir == 'report_artifacts':
+            return None
+
         return os.path.join(base_output, formatter_outdir)
 
     @staticmethod
@@ -92,7 +98,10 @@ class FormatterManager:
             return
 
         output_dir = FormatterManager.get_formatter_output_dir()
-        os.makedirs(output_dir, exist_ok=True)
+
+        # Create the output directory only if a custom one is specified
+        if output_dir:
+            os.makedirs(output_dir, exist_ok=True)
 
         try:
             formatter = formatter_class()
@@ -104,3 +113,5 @@ class FormatterManager:
             formatter.parse_json_to_allure(json_output)
         except Exception as e:
             print(f"Error running formatter {formatter_spec}: {str(e)}")
+            import traceback
+            traceback.print_exc()

{behavex-4.2.0 → behavex-4.2.2}/behavex/outputs/formatters/allure_behavex_formatter.py

@@ -306,18 +306,10 @@ class AllureBehaveXFormatter:
         """
         # Get the formatter output directory from FormatterManager
         formatter_output_dir = FormatterManager.get_formatter_output_dir()
-        base_output = get_env('OUTPUT', 'output')
 
-        # Check if a custom formatter output directory was explicitly set via --formatter-outdir
-        custom_outdir = get_param('formatter_outdir', '')
-
-        # Check if the user explicitly set a non-default formatter output directory
-        if custom_outdir and custom_outdir != 'report_artifacts':
-            # Use the custom directory if explicitly specified (not the default)
-            output_dir = formatter_output_dir
-        else:
-            # Default to allure-results subdirectory in the main output folder
-            output_dir = os.path.join(base_output, 'allure-results')
+        # If a custom output directory is specified, use it.
+        # Otherwise, default to 'output/allure-results'.
+        output_dir = formatter_output_dir or os.path.join(get_env('OUTPUT', 'output'), 'allure-results')
 
         os.makedirs(output_dir, exist_ok=True)
 
@@ -365,6 +357,11 @@ class AllureBehaveXFormatter:
                 if package_name:
                     test_case.labels.append({"name": "package", "value": package_name})
 
+                # Process scenario outline parameters
+                if 'parameters' in scenario and scenario['parameters']:
+                    for name, value in scenario['parameters'].items():
+                        test_case.parameters.append(Parameter(name=name, value=value))
+
                 # Process steps and look for failures
                 test_error_msg = None  # Store test's error message
 
@@ -425,8 +422,6 @@ class AllureBehaveXFormatter:
 
                 # If test failed, add its error as a direct category
                 if test_error_msg:
-                    category_name = self._sanitize_error_message(test_error_msg)
-
                     # Explicitly mark this test case as a Product Defect
                     test_case.labels.append({"name": "category", "value": "Product Defects"})
 
@@ -436,14 +431,9 @@ class AllureBehaveXFormatter:
                         "flaky": False
                     }
 
-                    # Add a parameter to help with subcategorization
-                    test_case.parameters.append(Parameter(
-                        name="Error Category",
-                        value=category_name
-                    ))
-
                 # Process tags
                 package_from_tag = None
+                test_thread_already_set = False
                 for tag in scenario['tags']:
                     if tag.startswith("epic="):
                         test_case.labels.append({"name": "epic", "value": tag.split("=")[-1]})
@@ -476,25 +466,36 @@ class AllureBehaveXFormatter:
                         test_case.labels = [label for label in test_case.labels if label.get("name") != "package"]
                         # Add the package from tag
                         test_case.labels.append({"name": "package", "value": package_from_tag})
+                    elif tag.startswith("allure.label."):
+                        label_key, label_value = tag.removeprefix("allure.label.").split(":")
+                        if label_key == "thread":
+                            test_thread_already_set = True
+                        test_case.labels.append({
+                            "name": label_key,
+                            "value": label_value
+                        })
                     else:
                         test_case.labels.append({"name": "tag", "value": tag})
-
+                # Add thread label if not already set and process_id is present
+                if "process_id" in scenario.keys() and not test_thread_already_set:
+                    test_case.labels.append({"name": "thread", "value": scenario["process_id"]})
                 # Add scenario timing
                 test_case.start = scenario.get("start", now())
                 test_case.stop = scenario.get("stop", now())
                 test_case.status = scenario['status']
 
                 # Process scenario logs as attachment
-                scenario_hash = scenario.get('identifier_hash', get_string_hash(f"{str(feature['filename'])}-{str(scenario['line'])}"))
-                log_path = os.path.join(get_env('logs', 'output/allure-results'), str(scenario_hash), 'scenario.log')
-                if os.path.exists(log_path):
-                    # Use relative path for the source if possible to avoid duplication
-                    rel_path = os.path.relpath(log_path, output_dir) if output_dir in log_path else log_path
-                    test_case.attachments.append(
-                        Attachment(source=rel_path,
-                                 name="scenario.log",
-                                 type="text/plain")
-                    )
+                if get_param('formatter_attach_logs'):
+                    scenario_hash = scenario.get('identifier_hash', get_string_hash(f"{str(feature['filename'])}-{str(scenario['line'])}"))
+                    log_path = os.path.join(get_env('logs', 'output/allure-results'), str(scenario_hash), 'scenario.log')
+                    if os.path.exists(log_path):
+                        # Use relative path for the source if possible to avoid duplication
+                        rel_path = os.path.relpath(log_path, output_dir) if output_dir in log_path else log_path
+                        test_case.attachments.append(
+                            Attachment(source=rel_path,
+                                     name="scenario.log",
+                                     type="text/plain")
+                        )
 
                 # Process evidence files
                 test_case = self._attach_evidence_files(test_case, scenario_hash, output_dir)
@@ -569,7 +570,11 @@ class AllureBehaveXFormatter:
                 # Add hierarchical labels for better organization in Allure report
                 if feature_file_path:
                     # Create hierarchical representation from feature file path
-                    hierarchical_package = feature_file_path.replace("/", ".").rstrip(".feature")
+                    hierarchical_package = feature_file_path.replace("/", ".")
+                    if hasattr(str, 'removesuffix'):  # Python 3.9+
+                        hierarchical_package = hierarchical_package.removesuffix('.feature')
+                    elif hierarchical_package.endswith('.feature'):
+                        hierarchical_package = hierarchical_package[:-len('.feature')]
 
                     # Remove existing package and suite labels to avoid duplication
                     test_case_dict["labels"] = [label for label in test_case_dict["labels"]

{behavex-4.2.0 → behavex-4.2.2}/behavex/outputs/output_strings.py

@@ -68,4 +68,20 @@ TEXTS = {
     },
     'folder': {'run_behave': u"Running folder: '{}' and feature '{}'."},
     'path': {'not_found': u'\nThe path "{}" was not found.\n'},
+    'process': {
+        'pool': {
+            'broken': u'\nWarning: Process pool was terminated abruptly: {}',
+            'broken.main': u'\nWarning: A process in the pool was terminated abruptly during main execution: {}'
+        }
+    },
+    'execution': {
+        'callback': {
+            'error': u'\nError occurred during execution callback: {}'
+        }
+    },
+    'parallel': {
+        'process': {
+            'error': u'\nError occurred during parallel process execution: {}'
+        }
+    }
 }

{behavex-4.2.0 → behavex-4.2.2}/behavex/outputs/report_json.py

@@ -182,6 +182,11 @@ def _processing_scenarios(scenarios, scenario_list, id_feature):
             scenario_info['filename'] = text(scenario.filename)
             scenario_info['feature'] = scenario.feature.name
             scenario_info['id_feature'] = id_feature
+
+            # Extract parameters for scenario outlines
+            if hasattr(scenario, '_row') and scenario._row:
+                scenario_info['parameters'] = dict(zip(scenario._row.headings, scenario._row.cells))
+
             steps = []
             for step in scenario.steps:
                 add_step_info(step, steps)
@@ -197,6 +202,8 @@ def _processing_scenarios(scenarios, scenario_list, id_feature):
             scenario_info['error_background'] = error_background
             scenario_info['id_hash'] = generate_uuid()
             scenario_info['identifier_hash'] = scenario.identifier_hash if hasattr(scenario, 'identifier_hash') else get_string_hash(f"{str(scenario.feature.filename)}-{str(scenario.line)}")
+            scenario_info['process_id'] = str(scenario.process_id) if hasattr(scenario, 'process_id') else str(os.getpid())
+            scenario_info['worker_id'] = str(scenario.worker_id) if hasattr(scenario, 'worker_id') else str(os.getpid())
             if scenario.feature.name in global_vars.retried_scenarios:
                 if (
                     scenario.name