René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"allure-behave: extend scenario_history_id to use optional environment variable","articleBody":"\u003c!---\nThank you so much for sending us a pull request! \n\nMake sure you have a clear name for your pull request. \nThe name should start with a capital letter and no dot is required in the end of the sentence.\nTo link the request with issues use the following notation: (fixes #123, fixes #321\\)\n\nAn example of good pull request names:\n* Add Cucumber integration (fixes #123\\)\n* Add an ability to disable default plugins\n* Support emoji in test descriptions\n--\u003e\n\n### Context\n\u003c!---\nDescribe the problem or feature in addition to a link to the issues\n--\u003e\n\n# allure-behave: extend scenario_history_id to use optional environment variable\n\nWe have a problem where we want to run the same test-suite in different environments. For example:\n\n1. **Execute Test-Suite for Different Browser:** Firefox, Chrome, ... (i.e. 'BROWSER=firefox behave' 'BROWSER=chromium behave' etc.)\n2. **Execute Test-Suite for Different Systems:** Linux armx64, Linux amd64, Win amd64, ...\n\nIf we collect all JSON allure-results and generate an allure report we only see **one** result for each test-scenario. Other executions are shown only in the \"retries\" section. We need to change the history ID so that each execution appears as a separate test. \n\nWe want to solve this by adding additional information into the historyId. It would have been nice to use additional user-modifiable information from the Scenario object, but this is not possible since scenario_history_id() is called before the before_scenario() hook (environment.py). Therefore not action in the before_scenario hook function (like changing scenario name or adding other information, can impact the historyId. \n\nThus, we designed a solution that uses an environment variable to pass this information. Our proposal is to the set an environment variable in `environment.py` that is used to influence the `historyId`.\n\nIn `allure-python/allure-behave/src/utils.py`:\n\n```python\ndef scenario_history_id(scenario) -\u003e str:\n    \"\"\"\n    Create a historyId for a scenario.\n    - Always based on feature name and scenario name\n    - Optional: can append a value from an environment variable\n    \"\"\"\n    parts = [scenario.feature.name, scenario.name]\n\n    if hasattr(scenario, \"_row\") and scenario._row:\n        row = scenario._row\n        parts.extend([f\"{name}={value}\" for name, value in zip(row.headings, row.cells)])\n\n    # Optional: append environment variable to differentiate runs\n    history_id = os.getenv(\"ALLURE_HISTORY_ID\")\n    if history_id:\n        parts.append(history_id)\n\n    return md5(*parts)\n```\n\nTo use this feature, add the environment variable in `environment.py`:\n\n```python\nfrom enum import Enum\nimport os\n\nclass Option(str, Enum):\n    OPTION_A = \"Option A\"\n    OPTION_B = \"Option B\"\n\ndef before_all(context):\n    os.environ[\"ALLURE_HISTORY_ID\"] = Option.OPTION_B.name\n```\n\nPull Request: #879 ","author":{"url":"https://github.com/Monstertoaster","@type":"Person","name":"Monstertoaster"},"datePublished":"2025-10-08T13:47:46.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/880/allure-python/issues/880"}