-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
Hi Petr,
I'm using your plugin as per the (README). Our tests use session‑scoped fixtures (e.g. shared browser) and require detailed, step‑level Robot reports.
Currently, each test decorated with @pytest_execute triggers its own pytest.main(), starting a new session. This forces reinitialization of session‑scoped fixtures.
Example test:
@pytest_execute
@pytest.mark.description("Should open nav item")
def test_ui_scenario_step1(playwright_page):
playwright_page.goto_mode("Composer")
playwright_page.navbar.service_chain_profiles.open()
assert playwright_page.navbar.is_panel_open(playwright_page.navbar.service_chain_profiles.name)
@pytest_execute
@pytest.mark.description("Nav item should still be open")
def test_ui_scenario_step2(playwright_page):
assert playwright_page.navbar.is_panel_open(playwright_page.navbar.service_chain_profiles.name)Robot suite calls:
*** Settings ***
Library ui.test_scenario
*** Test Cases ***
Module scoped test
Test UI Scenario Step1 opscenter_scenario
Test UI Scenario Step2 opscenter_scenario
Is it possible to add a batch execution mode and call pytest.main() once? That way session‑scoped fixtures are shared and each test can yield step‑level data in the Robot report.
Metadata
Metadata
Assignees
Labels
No labels