René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Issue with Allure Reporting Structure for Playwright + PyTest","articleBody":"I am currently working on integrating Allure reporting with our Playwright Python test suite, and I’ve encountered a limitation in the reporting structure that impacts test readability.\n\nIssue Description:\nWe are using with allure.step(...) blocks inside a single test function to log detailed steps\n\n(e.g., Login into the application,\nSelect use case,\nVerify Ongoing Threads UI,\nAsk Question .. etc.).\n\nThese steps correctly appear under Execution → Test body in the Allure report.\nHowever, they do not appear in the left-side panel under the test title. The sidebar only shows the main test case title (e.g., Verify OngoingThreads UI elements), making it harder to quickly identify which step passed or failed and how much time each step took.\n\nCurrent Behavior:\nAll steps are nested inside one test case.\nSidebar shows only one entry per test function.\nExecution details (steps and timing) are visible only when expanding the test case.\n\n\nPFA\n\n\n\n\nExpected Behavior:\nEach major step (or at least its name) should be visible in the left-side panel under the main test title for better visibility of:\nWhich step passed or failed\nExecution time per step\nOverall progress during test runs\n\nModule1\nEpic/Story1\nTitle1\n--Test step1\n--Test step2\n--Test step3\nEpic/Story2\n    -Title1\n--Test step1\n--Test step2\n--Test step3\n\nImpact:\nDifficult to quickly analyze failures and performance at a granular step level.\nReduces clarity for stakeholders reviewing reports.\nCurrent Implementation:\nUsing pytest.mark.asyncio for async tests.\nAllure decorators like @allure.epic, @allure.story, @allure.title for grouping.\nSteps logged with with allure.step(...) inside a single test function.\nQuestion:\nIs there a recommended approach or configuration in Allure to display these steps in the sidebar?\nAlternatively, should we split each major step into separate test functions with individual @allure.title annotations for better visibility?\nAttached:\nScreenshot of current Allure report structure.\nSample test code and conftest.py implementation for reference.\n\n","author":{"url":"https://github.com/harimulaguri9","@type":"Person","name":"harimulaguri9"},"datePublished":"2025-12-01T04:37:34.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/885/allure-python/issues/885"}