René's URL Explorer Experiment


Title: [allure-behave] Steps from tag-excluded scenarios bleed into the next matching scenario's result when hide_excluded=true · Issue #902 · allure-framework/allure-python · GitHub

Open Graph Title: [allure-behave] Steps from tag-excluded scenarios bleed into the next matching scenario's result when hide_excluded=true · Issue #902 · allure-framework/allure-python

X Title: [allure-behave] Steps from tag-excluded scenarios bleed into the next matching scenario's result when hide_excluded=true · Issue #902 · allure-framework/allure-python

Description: Allure integrations for Python test frameworks. Contribute to allure-framework/allure-python development by creating an account on GitHub.

Open Graph Description: Allure integrations for Python test frameworks. Contribute to allure-framework/allure-python development by creating an account on GitHub.

X Description: Allure integrations for Python test frameworks. Contribute to allure-framework/allure-python development by creating an account on GitHub.

Opengraph URL: https://github.com/allure-framework/allure-python

X: @github

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[allure-behave] Steps from tag-excluded scenarios bleed into the next matching scenario's result when hide_excluded=true","articleBody":"## Environment\n  - allure-behave: 2.15.3\n  - allure-commons: (run `pip show allure-commons`)\n  - behave: 1.3.3\n  - Python: 3.12\n\n  ## Describe the Bug\n\n  When running behave with a tag filter (e.g. `-t ETS-TC-372`) and\n  `-D AllureFormatter.hide_excluded=true`, the Allure result JSON for the\n  **matching scenario** accumulates steps from all tag-excluded scenarios that\n  appeared before it in the same feature file.\n\n  For example: if Sample.feature has 12 scenarios before ETS-TC-372, and\n  those 12 scenarios collectively have 179 steps, the result JSON for ETS-TC-372\n  shows 227 steps (179 orphaned + 48 real) instead of 48.\n\n  ## Root Cause\n\n  Behave calls `formatter.step(step)` for **every** scenario — including\n  tag-excluded ones — because `show_skipped=True` by default\n  (`run_scenario or show_skipped` in `Scenario.run()`).\n\n  This schedules excluded scenario steps into `AllureListener.self.steps` (a\n  `deque`).\n\n  In `stop_scenario()`, excluded scenarios hit the `should_drop_excluded=True`\n  branch and call `self.logger.drop_test(uuid)` immediately, **without ever\n  calling `flush_steps()` or clearing the deque**. All accumulated steps remain\n  in the deque.\n\n  When the first *matching* scenario runs, its steps are appended to the\n  already-populated deque. `match_step()` pops from the front (FIFO), consuming\n  the orphaned steps and stamping them into the matching scenario's `TestResult`.\n\n  ## Reproduction Steps\n\n  1. Create a feature file with 5+ scenarios where only the last one has\n     `@target-tag`.\n  2. Run:\n     ```bash\n     behave -t target-tag my.feature \\\n       --format allure_behave.formatter:AllureFormatter \\\n       --outfile allure-results \\\n       -D AllureFormatter.hide_excluded=true\n  3. Inspect allure-results/*-result.json — the step count will be\n  (sum of all excluded scenario steps) + (target scenario steps). \n\n  Expected Behaviour                                                                                                                                                                 \n   \n  The result JSON for the matching scenario should contain only its own                                                                                                              \n  steps.          \n                                                                                                                                                                                     \n  Fix\n                                                                                                                                                                                     \n  In AllureListener.stop_scenario(), clear the deque before dropping the\n  test so orphaned steps do not leak into the next scenario:\n                                                                                                                                                                                     \n  # listener.py  — stop_scenario()\n  if should_drop_skipped_by_option or should_drop_excluded:                                                                                                                          \n      self.steps.clear()          # ← add this line                                                                                                                                  \n      self.logger.drop_test(self.current_scenario_uuid)\n                                                                                                                                                                                     \n  This one-line fix prevents accumulated steps from tag-excluded scenarios                                                                                                           \n  bleeding into any subsequent scenario's result.","author":{"url":"https://github.com/mahanth967","@type":"Person","name":"mahanth967"},"datePublished":"2026-04-10T17:54:42Z","url":"https://github.com/allure-framework/allure-python/issues/902"}

react-profiling0
react-import-mapreact,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322
route-pattern/:user_id/:repository/issues/:id(.:format)
route-controllerissues
route-actionshow
fetch-noncev2:889104e4-041b-74f6-963d-4df644860d9b
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-idB2A6:9905:98767:D745A:6AFD4A5F
html-safe-nonce4eac4161b6955d8e794db27c55c0024d8079ed52b1c801056fae487ec15d19d4
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCMkE2Ojk5MDU6OTg3Njc6RDc0NUE6NkFGRDRBNUYiLCJ2aXNpdG9yX2lkIjoiNTU1NjE5NDg1OTU2MTA3NzM0MyIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9
visitor-hmac82f3b4289ed7e36e5162df5b3701edd34dd44ecc50ed4f6636b9c990e1e96659
hovercard-subject-tagrepository:79346720
github-keyboard-shortcutsrepository,issues,copilot
google-site-verificationApib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I
octolytics-urlhttps://collector.github.com/github/collect
analytics-location///issues/show
fb:app_id1401488693436528
apple-itunes-appapp-id=1477376905, app-argument=https://github.com/allure-framework/allure-python/issues/902
twitter:imagehttps://opengraph.githubassets.com/4fb4b7c65d2d1acf41a85aa1b1fb010246e6d236295417a7fb848060dd033574/allure-framework/allure-python
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/4fb4b7c65d2d1acf41a85aa1b1fb010246e6d236295417a7fb848060dd033574/allure-framework/allure-python
og:image:altAllure integrations for Python test frameworks. Contribute to allure-framework/allure-python development by creating an account on GitHub.
og:image:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
hostnamegithub.com
expected-hostnamegithub.com
None66653c2e55a6fff2930be1bdf07ee4f8aa137e3956d056c822563be6f878755e
turbo-cache-controlno-cache
go-importgithub.com/allure-framework/allure-python git https://github.com/allure-framework/allure-python.git
octolytics-dimension-user_id5879127
octolytics-dimension-user_loginallure-framework
octolytics-dimension-repository_id79346720
octolytics-dimension-repository_nwoallure-framework/allure-python
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id79346720
octolytics-dimension-repository_network_root_nwoallure-framework/allure-python
turbo-body-classeslogged-out env-production page-responsive
disable-turbofalse
browser-stats-urlhttps://api.github.com/_private/browser/stats
browser-errors-urlhttps://api.github.com/_private/browser/errors
releaseb6f01f7cb9f35f8c09949773241a3d49dd04b340
ui-targetfull
theme-color#1e2327
color-schemelight dark
react-app-nameissues

Links:

Skip to contenthttps://github.com/allure-framework/allure-python/issues/902#start-of-content
https://github.com/
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fallure-framework%2Fallure-python%2Fissues%2F902
GitHubRepository hosting, code review, and collaborationhttps://github.com/platform
CopilotAI coding agent for tasks, projects, and automated workhttps://github.com/features/copilot
ActionsCI/CD and automationhttps://github.com/features/actions
Code QualityQuality analysis, fixes, and enforcementhttps://github.com/features/code-quality
CodespacesCloud development environmentshttps://github.com/features/codespaces
Code SecurityVulnerability detection and remediationhttps://github.com/security/advanced-security/code-security
Secret ProtectionSecret scanning and leak preventionhttps://github.com/security/advanced-security/secret-protection
All Featureshttps://github.com/features
Documentationhttps://docs.github.com/en
Traininghttps://learn.github.com/skills
Certificationshttps://learn.github.com/credentials
Build with Copilothttps://github.com/features/ai
Customize Copilothttps://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-copilot-overview
Integrationshttps://github.com/marketplace
Trending reposhttps://github.com/trending
GitHub Sponsorshttps://github.com/open-source/sponsors
Developer articleshttps://github.com/resources/articles
ChangelogYour source for the latest features, improvements, and fixes across GitHub products, all in one place.https://github.blog/changelog/
Enterpriseshttps://github.com/enterprise
Teamhttps://github.com/team
Startupshttps://github.com/enterprise/startups
Nonprofitshttps://github.com/solutions/industry/nonprofits
Healthcarehttps://github.com/solutions/industry/healthcare
Financial serviceshttps://github.com/solutions/industry/financial-services
Manufacturinghttps://github.com/solutions/industry/manufacturing
Governmenthttps://github.com/solutions/industry/government
See all industrieshttps://github.com/solutions/industry
Why GitHubhttps://github.com/why-github
Customer Storieshttps://github.com/customer-stories
Business insightshttps://github.com/solutions/executive-insights
Trust Centerhttps://github.com/trust-center
GitHub Advanced SecurityEnterprise-grade code securityhttps://github.com/security/advanced-security
Copilot for businessEnterprise-grade AI featureshttps://github.com/features/copilot/copilot-business
Premium SupportEnterprise-grade 24/7 supporthttps://github.com/enterprise/premium-support
Documentationhttps://docs.github.com/en
Resource centerhttps://github.com/resources
Bloghttps://github.blog/
Events & webinarshttps://github.com/resources/events
Community Forumhttps://github.com/orgs/community/discussions
Customer Storieshttps://github.com/customer-stories
Integrationshttps://github.com/marketplace
Customer supporthttps://help.github.com/
Traininghttps://learn.github.com/skills
GitHub Statushttps://www.githubstatus.com/
Abouthttps://github.com/about
Partnershttps://github.com/partners
Changeloghttps://github.blog/changelog/
GitHub UniverseThe event for developers, by developers — talks, workshops, and what’s next for GitHub.https://githubuniverse.com/
Pricinghttps://github.com/pricing
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fallure-framework%2Fallure-python%2Fissues%2F902
Sign uphttps://github.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fissues%2Fshow&source=header-repo&source_repo=allure-framework%2Fallure-python
Reloadhttps://github.com/allure-framework/allure-python/issues/902
Reloadhttps://github.com/allure-framework/allure-python/issues/902
Reloadhttps://github.com/allure-framework/allure-python/issues/902
https://github.com/allure-framework/allure-python
New issuehttps://github.com/login?return_to=https://github.com/allure-framework/allure-python/issues/902
New issuehttps://github.com/login?return_to=https://github.com/allure-framework/allure-python/issues/902
#922https://github.com/allure-framework/allure-python/pull/922
[allure-behave] Steps from tag-excluded scenarios bleed into the next matching scenario's result when hide_excluded=truehttps://github.com/allure-framework/allure-python/issues/902#top
#922https://github.com/allure-framework/allure-python/pull/922
https://github.com/mahanth967
mahanth967https://github.com/mahanth967
on Apr 10, 2026https://github.com/allure-framework/allure-python/issues/902#issue-4240851701
Sign up for freehttps://github.com/signup?return_to=https://github.com/allure-framework/allure-python/issues/902
Sign in to commenthttps://github.com/login?return_to=https://github.com/allure-framework/allure-python/issues/902
https://github.com
Termshttps://docs.github.com/site-policy/github-terms/github-terms-of-service
Privacyhttps://docs.github.com/site-policy/privacy-policies/github-privacy-statement
Securityhttps://github.com/security
Statushttps://www.githubstatus.com/
Communityhttps://github.community/
Docshttps://docs.github.com/
Contacthttps://support.github.com?tags=dotcom-footer

Viewport: width=device-width


URLs of crawlers that visited me.