hooks TGL_Device: mobile process.env.USE_LOCAL true process.env.LOCAL_BROWSERSTACK false ,process.env.USE_LOCAL, true,process.env.LOCAL_SHOW_BROWSER , false, TGL_Device, mobile [dotenv@17.2.1] injecting env (0) from .env -- tip: 📡 observe env with Radar: https://dotenvx.com/radar [dotenv@17.2.1] injecting env (0) from .env -- tip: 📡 version env with Radar: https://dotenvx.com/radar [dotenv@17.2.1] injecting env (0) from .env -- tip: 🔐 encrypt with Dotenvx: https://dotenvx.com [dotenv@17.2.1] injecting env (0) from .env -- tip: 🔐 encrypt with Dotenvx: https://dotenvx.com [dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ suppress all logs with { quiet: true } [dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ load multiple .env files with { path: ['.env.local', '.env'] } [dotenv@17.2.1] injecting env (0) from .env -- tip: 🔐 encrypt with Dotenvx: https://dotenvx.com [dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ enable debug logging with { debug: true } hooks TGL_Device: mobile process.env.USE_LOCAL true process.env.LOCAL_BROWSERSTACK false ,process.env.USE_LOCAL, true,process.env.LOCAL_SHOW_BROWSER , false, TGL_Device, mobile [dotenv@17.2.1] injecting env (0) from .env -- tip: 🛠️ run anywhere with `dotenvx run -- yourcommand` [dotenv@17.2.1] injecting env (0) from .env -- tip: 🔐 prevent building .env in docker: https://dotenvx.com/prebuild [dotenv@17.2.1] injecting env (0) from .env -- tip: 🛠️ run anywhere with `dotenvx run -- yourcommand` [dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ specify custom .env file path with { path: '/custom/path/.env' } [dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ load multiple .env files with { path: ['.env.local', '.env'] } hooks TGL_Device: mobile process.env.USE_LOCAL true process.env.LOCAL_BROWSERSTACK false ,process.env.USE_LOCAL, true,process.env.LOCAL_SHOW_BROWSER , false, TGL_Device, mobile [dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ override existing env vars with { override: true } [dotenv@17.2.1] injecting env (0) from .env -- tip: 📡 observe env with Radar: https://dotenvx.com/radar [dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ enable debug logging with { debug: true } Before scenario name PWA Navigate to How to use Don't Rush to Crush .[dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ override existing env vars with { override: true } [dotenv@17.2.1] injecting env (0) from .env -- tip: 🔐 prevent building .env in docker: https://dotenvx.com/prebuild [dotenv@17.2.1] injecting env (0) from .env -- tip: 📡 auto-backup env with Radar: https://dotenvx.com/radar [dotenv@17.2.1] injecting env (0) from .env -- tip: 📡 version env with Radar: https://dotenvx.com/radar [dotenv@17.2.1] injecting env (0) from .env -- tip: 🛠️ run anywhere with `dotenvx run -- yourcommand` [dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ write to custom object with { processEnv: myObject } [dotenv@17.2.1] injecting env (0) from .env -- tip: 🔐 prevent building .env in docker: https://dotenvx.com/prebuild [dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ load multiple .env files with { path: ['.env.local', '.env'] } .Before scenario name PWA Navigate to Before you rush to crush hooks TGL_Device: mobile process.env.USE_LOCAL true process.env.LOCAL_BROWSERSTACK false ,process.env.USE_LOCAL, true,process.env.LOCAL_SHOW_BROWSER , false, TGL_Device, mobile [dotenv@17.2.1] injecting env (0) from .env -- tip: 🔐 prevent committing .env to code: https://dotenvx.com/precommit [dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ enable debug logging with { debug: true } [dotenv@17.2.1] injecting env (0) from .env -- tip: 🔐 prevent building .env in docker: https://dotenvx.com/prebuild [dotenv@17.2.1] injecting env (0) from .env -- tip: 🔐 encrypt with Dotenvx: https://dotenvx.com [dotenv@17.2.1] injecting env (0) from .env -- tip: 📡 version env with Radar: https://dotenvx.com/radar [dotenv@17.2.1] injecting env (0) from .env -- tip: 🔐 prevent committing .env to code: https://dotenvx.com/precommit [dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ override existing env vars with { override: true } [dotenv@17.2.1] injecting env (0) from .env -- tip: 🔐 encrypt with Dotenvx: https://dotenvx.com hooks TGL_Device: mobile process.env.USE_LOCAL true process.env.LOCAL_BROWSERSTACK false ,process.env.USE_LOCAL, true,process.env.LOCAL_SHOW_BROWSER , false, TGL_Device, mobile .Before scenario name PWA Navigate to Enteral feeding tubes [dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ suppress all logs with { quiet: true } hooks TGL_Device: mobile process.env.USE_LOCAL true process.env.LOCAL_BROWSERSTACK false ,process.env.USE_LOCAL, true,process.env.LOCAL_SHOW_BROWSER , false, TGL_Device, mobile [dotenv@17.2.1] injecting env (0) from .env -- tip: 🛠️ run anywhere with `dotenvx run -- yourcommand` [dotenv@17.2.1] injecting env (0) from .env -- tip: 🔐 encrypt with Dotenvx: https://dotenvx.com [dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ enable debug logging with { debug: true } [dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ write to custom object with { processEnv: myObject } [dotenv@17.2.1] injecting env (0) from .env -- tip: 📡 version env with Radar: https://dotenvx.com/radar [dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ specify custom .env file path with { path: '/custom/path/.env' } [dotenv@17.2.1] injecting env (0) from .env -- tip: 📡 version env with Radar: https://dotenvx.com/radar .Before scenario name PWA Navigate to Swallowing difficulties ..[dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ write to custom object with { processEnv: myObject } [dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ override existing env vars with { override: true } [dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ suppress all logs with { quiet: true } [dotenv@17.2.1] injecting env (0) from .env -- tip: 🔐 prevent building .env in docker: https://dotenvx.com/prebuild [dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ enable debug logging with { debug: true } [dotenv@17.2.1] injecting env (0) from .env -- tip: 🔐 prevent building .env in docker: https://dotenvx.com/prebuild [dotenv@17.2.1] injecting env (0) from .env -- tip: 📡 version env with Radar: https://dotenvx.com/radar [dotenv@17.2.1] injecting env (0) from .env -- tip: 🔐 prevent committing .env to code: https://dotenvx.com/precommit .Before scenario name PWA Navigate to Gastrointestinal dysfunction hooks TGL_Device: mobile process.env.USE_LOCAL true process.env.LOCAL_BROWSERSTACK false ,process.env.USE_LOCAL, true,process.env.LOCAL_SHOW_BROWSER , false, TGL_Device, mobile [dotenv@17.2.1] injecting env (0) from .env -- tip: 🛠️ run anywhere with `dotenvx run -- yourcommand` [dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ specify custom .env file path with { path: '/custom/path/.env' } [dotenv@17.2.1] injecting env (0) from .env -- tip: 🔐 prevent committing .env to code: https://dotenvx.com/precommit [dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ override existing env vars with { override: true } [dotenv@17.2.1] injecting env (0) from .env -- tip: 📡 version env with Radar: https://dotenvx.com/radar [dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ override existing env vars with { override: true } [dotenv@17.2.1] injecting env (0) from .env -- tip: 🔐 prevent committing .env to code: https://dotenvx.com/precommit [dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️ write to custom object with { processEnv: myObject } .Before scenario name PWA Navigate to Part doses ......Desktop: menu toggle not found → menu already open .Clicking menu item: Home ..Desktop: menu toggle not found → menu already open .Clicking menu item: Home ..Desktop: menu toggle not found → menu already open .Clicking menu item: Home ..Desktop: menu toggle not found → menu already open .Clicking menu item: Home ..Desktop: menu toggle not found → menu already open .Clicking menu item: Home ..Desktop: menu toggle not found → menu already open .Clicking menu item: Home F--------F--------F--------F--------F--------..Before scenario name Verify bottom navigation in PWA ..Before scenario name Quick Access buttons navigation .Before scenario name Quick Access buttons navigation ..Before scenario name Quick Access buttons navigation ...Before scenario name Navigate to direct link pages from menu - Quick Guide Symbols F--------.......Before scenario name Navigate to direct link pages from menu - Methods .......Desktop: menu toggle not found → menu already open .Clicking menu item: Home .Mobile: menu toggle visible → clicking... .Mobile: menu toggle visible → clicking... .Mobile: menu toggle visible → clicking... .Mobile: menu toggle visible → clicking... ..Mobile: menu toggle visible → clicking... ................F---...........Before scenario name Navigate to direct link pages from menu - Glossary .....Before scenario name Navigate to direct link pages from menu - Favourites ....Before scenario name Navigate to direct link pages from menu - What's New ..Before scenario name Navigate to submenu items - How to use Don't Rush to Crush .Before scenario name Navigate to submenu items - Before you rush to crush .........Mobile: menu toggle visible → clicking... ..Before scenario name Navigate to submenu items - Decision making process .Mobile: menu toggle visible → clicking... .....Mobile: menu toggle visible → clicking... .Mobile: menu toggle visible → clicking... .Mobile: menu toggle visible → clicking... ..........Mobile: menu toggle visible → clicking... ....Before scenario name Navigate to submenu items - Comparative Tables ..........................Before scenario name Navigate to submenu items - Enteral feeding tubes .................Before scenario name Navigate to submenu items - Equipment ...Before scenario name Navigate to submenu items - Gastrointestinal dysfunction ...Mobile: menu toggle visible → clicking... ....Mobile: menu toggle visible → clicking... ...Before scenario name Navigate to submenu items - Swallowing difficulties ..........Before scenario name Navigate to submenu items - Oral liquids and thickness testing ..Mobile: menu toggle visible → clicking... .Mobile: menu toggle visible → clicking... .........Mobile: menu toggle visible → clicking... .................................Before scenario name Navigate to submenu items - Part-dosing .....Mobile: menu toggle visible → clicking... ......Before scenario name Search for monograph and verify content sections ..................Desktop: menu toggle not found → menu already open ....Before scenario name Search for monograph and verify content sections ..Before scenario name Search for monograph and verify content sections .........Before scenario name Search for monograph and verify content sections .Before scenario name Search for monograph and verify content sections ................F--------.Before scenario name Search for monograph and verify content sections ..F-----------------...Before scenario name Search for monograph and verify content sections ..F-----------------F-----------------..Before scenario name Search for monograph and verify content sections ..Before scenario name Search for monograph and verify content sections ...F-----------------..F-----------------.Before scenario name Search for monograph and verify content sections .........Before scenario name Searching for Vad in the drug search input with no matches .........F-----------------.Before scenario name Searching for XYZ in the drug search input with no matches ....F-----------------.Before scenario name Searching for xq in the drug search input with no matches ...F-----------------F-----------------.Before scenario name Searching for Hgcyum in the drug search input with no matches .....Before scenario name Monograph-Browse By Categories Abilify-aripiprazole .F-----------------...Before scenario name Monograph-Browse By Categories Bicard-bisoprolol ...F---.....Before scenario name Monograph-Browse By Categories Carvidol-carvedilol .........F---.Before scenario name Monograph-Browse By Categories Domion-agomelatine ..F---...Before scenario name Monograph-Browse By Categories Esopreze-esomeprazole .F---....F------.Before scenario name Monograph-Browse By Categories Mektovi-binimetinib ...F------..Before scenario name Monograph-Browse By Categories Neoral-ciclosporin ...F------.Before scenario name Monograph-Browse By Categories Onureg-azacitadine .........Before scenario name Monograph-Browse By Categories Pulmoris-ambrisentan ......F------F------.Before scenario name Monograph-Browse By Categories Solian-amisulpride ...Before scenario name Monograph-Browse By Categories Xelabine-capecitabine ....F------.Before scenario name Monograph-Browse By Categories Zytiga-abiraterone ......F------...Before scenario name Verify What's New page content is visible .F------....Before scenario name Search for various brand names and verify main drug appears ....F------.Before scenario name Search for various brand names and verify main drug appears ..Before scenario name Search for various brand names and verify main drug appears ....................Before scenario name Search for various brand names and verify main drug appears ...........Before scenario name Search for various brand names and verify main drug appears ..Before scenario name Search for various brand names and verify main drug appears ........................Before scenario name Search for various brand names and verify main drug appears .F------.F------.....Before scenario name Search for various brand names and verify main drug appears ..Before scenario name Search for various brand names and verify main drug appears ...Before scenario name Search for various brand names and verify main drug appears ..Before scenario name Search for various brand names and verify main drug appears ........F------...Before scenario name Search for various brand names and verify main drug appears ......Before scenario name Search for various brand names and verify main drug appears ........................................Before scenario name Search for various brand names and verify main drug appears ..Before scenario name Load Comparative tables page and verify page header ...Before scenario name Switch to Proton pump inhibitors tab and verify content ......Before scenario name Switch to ACE inhibitors tab and verify content ..Before scenario name Switch to Statins tab and verify content ...............Before scenario name Switch to Antipsychotics tab and verify content ...........................Before scenario name Switch to Antidepressants tab and verify content .......Before scenario name View decision-making process page ..........Before scenario name Load Equipment page and verify page header ..Before scenario name Switch to Equipment tab and verify content ..Before scenario name Switch to Preventing wrong-route tab and verify content .........Before scenario name Switch to EnFit connectors tab and verify content ...........Before scenario name Switch to Crushing devices tab and verify content .............Before scenario name Switch to References tab and verify content ......Before scenario name Warning callout displays prominently ...........Before scenario name Glossary Functionality -absorption ..............Before scenario name Glossary Functionality -bioavailability ......Desktop: menu toggle not found → menu already open .Clicking menu item: Glossary ..........Before scenario name Glossary Functionality -bioequivalent ...Desktop: menu toggle not found → menu already open .Clicking menu item: Glossary ....Before scenario name Glossary Functionality -disperse .....Before scenario name Glossary Functionality -high osmolarity ..Desktop: menu toggle not found → menu already open .Clicking menu item: Glossary .Before scenario name Clicking A-Z button A on Glossary page navigates correctly to A section .....Before scenario name Clicking A-Z button B on Glossary page navigates correctly to B section ...Desktop: menu toggle not found → menu already open .Clicking menu item: Glossary .Before scenario name Clicking A-Z button D on Glossary page navigates correctly to D section ..Before scenario name Clicking A-Z button H on Glossary page navigates correctly to H section .......Desktop: menu toggle not found → menu already open .Clicking menu item: Glossary .Desktop: menu toggle not found → menu already open .Clicking menu item: Glossary .Desktop: menu toggle not found → menu already open .Clicking menu item: Glossary .....Before scenario name Clicking A-Z button M on Glossary page navigates correctly to M section ...Desktop: menu toggle not found → menu already open .Clicking menu item: Glossary Desktop: menu toggle not found → menu already open .Clicking menu item: Glossary ...........Desktop: menu toggle not found → menu already open .Clicking menu item: Glossary .----NO driver -After scenario "Navigate to How to use Don't Rush to Crush": Driver was not initialized, skipping quit. ---------.----NO driver -After scenario "Navigate to Before you rush to crush": Driver was not initialized, skipping quit. ---------.---NO driver -After scenario "Navigate to Enteral feeding tubes": Driver was not initialized, skipping quit. ----------.----NO driver -After scenario "Navigate to Swallowing difficulties": Driver was not initialized, skipping quit. ---------.---NO driver -After scenario "Navigate to Gastrointestinal dysfunction": Driver was not initialized, skipping quit. ----------.---NO driver -After scenario "Navigate to Part doses": Driver was not initialized, skipping quit. ----------.Before scenario name Verify tab Enteral feeding tubes is visible and clickable ...............Before scenario name Verify tab Swallowing difficulties is visible and clickable .Before scenario name Switch to Enteral feeding tubes tab and verify content ..Before scenario name Switch to Swallowing difficulties tab and verify content ..Before scenario name Verify method section Method A. Disperse the tablet under Enteral feeding tubes tab ....................Before scenario name Verify method section Method B. Crush the tablet under Enteral feeding tubes tab ........................Before scenario name Verify method section Method C. Disperse the contents of a capsule or sachet under Enteral feeding tubes tab ......Before scenario name Expand method sections under Swallowing difficulties tab - Method D. Disperse the tablet ......Before scenario name Expand method sections under Swallowing difficulties tab - Method E. Crush the tablet ..Before scenario name Expand method sections under Swallowing difficulties tab - Method F. Disperse the contents of the capsule or sachet ..------NO driver -After scenario "Search for monograph and verify content sections": Driver was not initialized, skipping quit. -----------------.--------NO driver -After scenario "Search for monograph and verify content sections": Driver was not initialized, skipping quit. ---------------.---------NO driver -After scenario "Search for monograph and verify content sections": Driver was not initialized, skipping quit. --------------.--------NO driver -After scenario "Search for monograph and verify content sections": Driver was not initialized, skipping quit. ---------------.-------NO driver -After scenario "Search for monograph and verify content sections": Driver was not initialized, skipping quit. ----------------.-------NO driver -After scenario "Search for monograph and verify content sections": Driver was not initialized, skipping quit. ----------------.------NO driver -After scenario "Search for monograph and verify content sections": Driver was not initialized, skipping quit. -----------------.--------NO driver -After scenario "Search for monograph and verify content sections": Driver was not initialized, skipping quit. ---------------.-------NO driver -After scenario "Search for monograph and verify content sections": Driver was not initialized, skipping quit. ----------------.-------NO driver -After scenario "Search for monograph and verify content sections": Driver was not initialized, skipping quit. ----------------.-NO driver -After scenario "Verify My Account -subscription-sales-email": Driver was not initialized, skipping quit. ------.--NO driver -After scenario "Verify My Account -subscription-renew-button": Driver was not initialized, skipping quit. -----.Before scenario name PWA Verify My Account -menu-whats-new .............Before scenario name PWA Verify My Account -menu-about-legal ...........................................Before scenario name PWA Verify My Account-About Us Legal -about-link-0 .......Before scenario name PWA Verify My Account-About Us Legal -about-link-1 ..Before scenario name PWA Verify My Account-About Us Legal -about-link-2 ..Before scenario name PWA Verify My Account-About Us Legal -about-link-3 ............F---.Before scenario name PWA Verify My Account-About Us Legal -about-link-4 ..F---..--NO driver -After scenario "Load page and verify initial state": Driver was not initialized, skipping quit. ------.--NO driver -After scenario "Verify symbol Oral liquids tile is visible in the grid": Driver was not initialized, skipping quit. -----.--NO driver -After scenario "Verify symbol Disperse the tablet tile is visible in the grid": Driver was not initialized, skipping quit. -----.--NO driver -After scenario "Verify symbol Open the capsule tile is visible in the grid": Driver was not initialized, skipping quit. -----.--NO driver -After scenario "Verify symbol Crush the tablet tile is visible in the grid": Driver was not initialized, skipping quit. -----.--NO driver -After scenario "Verify symbol Do not crush tile is visible in the grid": Driver was not initialized, skipping quit. -----.--NO driver -After scenario "Verify symbol Do not open the capsule tile is visible in the grid": Driver was not initialized, skipping quit. -----.--NO driver -After scenario "Verify symbol Cytotoxic medicines tile is visible in the grid": Driver was not initialized, skipping quit. -----.--NO driver -After scenario "Verify symbol Hazardous medicine tile is visible in the grid": Driver was not initialized, skipping quit. -----.---NO driver -After scenario "Verify symbol details for Oral liquids": Driver was not initialized, skipping quit. -------.---NO driver -After scenario "Verify symbol details for Disperse the tablet": Driver was not initialized, skipping quit. -------.---NO driver -After scenario "Verify symbol details for Open the capsule": Driver was not initialized, skipping quit. -------.---NO driver -After scenario "Verify symbol details for Crush the tablet": Driver was not initialized, skipping quit. -------.---NO driver -After scenario "Verify symbol details for Do not crush": Driver was not initialized, skipping quit. -------.---NO driver -After scenario "Verify symbol details for Do not open the capsule": Driver was not initialized, skipping quit. -------.---NO driver -After scenario "Verify symbol details for Cytotoxic medicines": Driver was not initialized, skipping quit. -------.---NO driver -After scenario "Verify symbol details for Hazardous medicine": Driver was not initialized, skipping quit. -------.Before scenario name Verify symbol Oral liquids tile is visible in the grid on mobile ......F-----.......Before scenario name Verify symbol Disperse the tablet tile is visible in the grid on mobile .F-----.Before scenario name Verify symbol Open the capsule tile is visible in the grid on mobile ..F-----F-----..Before scenario name Verify symbol Crush the tablet tile is visible in the grid on mobile ..Before scenario name Verify symbol Do not crush tile is visible in the grid on mobile ..Before scenario name Verify symbol Do not open the capsule tile is visible in the grid on mobile ................................Before scenario name Verify symbol Cytotoxic medicines tile is visible in the grid on mobile ..Before scenario name Verify symbol Hazardous medicine tile is visible in the grid on mobile ......................Before scenario name Verify symbol details for Oral liquids on mobile ..Before scenario name Verify symbol details for Disperse the tablet on mobile ..Before scenario name Verify symbol details for Open the capsule on mobile ....................F-----............Before scenario name Verify symbol details for Crush the tablet on mobile ..Before scenario name Verify symbol details for Do not crush on mobile ....Before scenario name Verify symbol details for Do not open the capsule on mobile .....................Before scenario name Verify symbol details for Cytotoxic medicines on mobile ..Before scenario name Verify symbol details for Hazardous medicine on mobile ...-----NO driver -After scenario "Navigate to About this resource submenu items - How to use Don't Rush to Crush": Driver was not initialized, skipping quit. ---------.----NO driver -After scenario "Navigate to About this resource submenu items - Before you rush to crush": Driver was not initialized, skipping quit. ----------.-----NO driver -After scenario "Navigate to About this resource submenu items - Decision making process": Driver was not initialized, skipping quit. ---------.---NO driver -After scenario "Navigate to direct links under Home submenu - Quick guide symbols": Driver was not initialized, skipping quit. -------.---NO driver -After scenario "Navigate to direct links under Home submenu - Methods": Driver was not initialized, skipping quit. -------.-----NO driver -After scenario "Navigate to Background information submenu items - Comparative Tables": Driver was not initialized, skipping quit. ---------.----NO driver -After scenario "Navigate to Background information submenu items - Enteral feeding tubes": Driver was not initialized, skipping quit. ----------.----NO driver -After scenario "Navigate to Background information submenu items - Equipment": Driver was not initialized, skipping quit. ----------.----NO driver -After scenario "Navigate to Background information submenu items - Gastrointestinal dysfunction": Driver was not initialized, skipping quit. ----------.-----NO driver -After scenario "Navigate to Background information submenu items - Swallowing difficulties": Driver was not initialized, skipping quit. ---------.---NO driver -After scenario "Navigate to Background information submenu items - Oral liquids and thickness testing": Driver was not initialized, skipping quit. -----------.----NO driver -After scenario "Navigate to Background information submenu items - Part-dosing": Driver was not initialized, skipping quit. ----------.Before scenario name What's New Functionality .........Desktop: menu toggle not found → menu already open ......................................AfterAll: No global browser to close AfterAll: No driver to quit in this worker .....AfterAll: No global browser to close AfterAll: No driver to quit in this worker .AfterAll: No global browser to close AfterAll: No driver to quit in this worker .AfterAll: No global browser to close AfterAll: No driver to quit in this worker .AfterAll: No global browser to close AfterAll: No driver to quit in this worker ..AfterAll: No global browser to close AfterAll: No driver to quit in this worker Failures: 1) Scenario: PWA Navigate to How to use Don't Rush to Crush # features\DRTC\App-Home\home-landing-page.feature:23 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ When I ensure the menu is open with "menu-toggle" # features\step_definitions\layout-steps.js:4 × When I click the menu item "Home" # features\step_definitions\layout-steps.js:55 TimeoutError: Menu item "Home" not found Wait timed out after 8253ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - Given "a" element with "href" "/about/how-to-use-drtc#c-drtc-how-to-use-stem-dita" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 1 seconds # features\step_definitions\bstack-steps.js:456 - Given "h2" element with "text" "How to use Don't Rush to Crush" # features\step_definitions\visibility-steps.js:25 - And I scroll to element # features\step_definitions\scroll-steps.js:9 - And I wait for 3 seconds # features\step_definitions\bstack-steps.js:456 - Then "h2" element with "text" "How to use Don't Rush to Crush" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 2) Scenario: PWA Navigate to Before you rush to crush # features\DRTC\App-Home\home-landing-page.feature:24 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ When I ensure the menu is open with "menu-toggle" # features\step_definitions\layout-steps.js:4 × When I click the menu item "Home" # features\step_definitions\layout-steps.js:55 TimeoutError: Menu item "Home" not found Wait timed out after 8061ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - Given "a" element with "href" "/about/before-you-rush-to-crush#drtc-before-you-rush-stem-dita" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 1 seconds # features\step_definitions\bstack-steps.js:456 - Given "h2" element with "text" "Before you rush to crush" # features\step_definitions\visibility-steps.js:25 - And I scroll to element # features\step_definitions\scroll-steps.js:9 - And I wait for 3 seconds # features\step_definitions\bstack-steps.js:456 - Then "h2" element with "text" "Before you rush to crush" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 3) Scenario: PWA Navigate to Enteral feeding tubes # features\DRTC\App-Home\home-landing-page.feature:25 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ When I ensure the menu is open with "menu-toggle" # features\step_definitions\layout-steps.js:4 × When I click the menu item "Home" # features\step_definitions\layout-steps.js:55 TimeoutError: Menu item "Home" not found Wait timed out after 8048ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - Given "a" element with "href" "/background/enteral-feeding-tubes#c-drtc-enteral-feeding-tubes-stem-dita" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 1 seconds # features\step_definitions\bstack-steps.js:456 - Given "h2" element with "text" "Enteral feeding tubes" # features\step_definitions\visibility-steps.js:25 - And I scroll to element # features\step_definitions\scroll-steps.js:9 - And I wait for 3 seconds # features\step_definitions\bstack-steps.js:456 - Then "h2" element with "text" "Enteral feeding tubes" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 4) Scenario: PWA Navigate to Swallowing difficulties # features\DRTC\App-Home\home-landing-page.feature:26 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ When I ensure the menu is open with "menu-toggle" # features\step_definitions\layout-steps.js:4 × When I click the menu item "Home" # features\step_definitions\layout-steps.js:55 TimeoutError: Menu item "Home" not found Wait timed out after 8210ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - Given "a" element with "href" "/background/swallowing-difficulties#c-drtc-swallowing-difficulties-stem-dita" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 1 seconds # features\step_definitions\bstack-steps.js:456 - Given "h2" element with "text" "Swallowing difficulties" # features\step_definitions\visibility-steps.js:25 - And I scroll to element # features\step_definitions\scroll-steps.js:9 - And I wait for 3 seconds # features\step_definitions\bstack-steps.js:456 - Then "h2" element with "text" "Swallowing difficulties" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 5) Scenario: PWA Navigate to Gastrointestinal dysfunction # features\DRTC\App-Home\home-landing-page.feature:27 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ When I ensure the menu is open with "menu-toggle" # features\step_definitions\layout-steps.js:4 × When I click the menu item "Home" # features\step_definitions\layout-steps.js:55 TimeoutError: Menu item "Home" not found Wait timed out after 8171ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - Given "a" element with "href" "/background/gastrointestinal-dysfunction#c-drtc-about-gastrointestinal-dysfunction-topic-1-dita" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 1 seconds # features\step_definitions\bstack-steps.js:456 - Given "h2" element with "text" "Gastrointestinal dysfunction" # features\step_definitions\visibility-steps.js:25 - And I scroll to element # features\step_definitions\scroll-steps.js:9 - And I wait for 3 seconds # features\step_definitions\bstack-steps.js:456 - Then "h2" element with "text" "Gastrointestinal dysfunction" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 6) Scenario: PWA Navigate to Part doses # features\DRTC\App-Home\home-landing-page.feature:28 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ When I ensure the menu is open with "menu-toggle" # features\step_definitions\layout-steps.js:4 × When I click the menu item "Home" # features\step_definitions\layout-steps.js:55 TimeoutError: Menu item "Home" not found Wait timed out after 8259ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - Given "a" element with "href" "/background/part-dosing#c-drtc-part-doses-stem-dita" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 1 seconds # features\step_definitions\bstack-steps.js:456 - Given "h2" element with "text" "Part doses" # features\step_definitions\visibility-steps.js:25 - And I scroll to element # features\step_definitions\scroll-steps.js:9 - And I wait for 3 seconds # features\step_definitions\bstack-steps.js:456 - Then "h2" element with "text" "Part doses" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 7) Scenario: Verify bottom navigation in PWA # features\DRTC\App-Home\home-landing-page.feature:30 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ When I ensure the menu is open with "menu-toggle" # features\step_definitions\layout-steps.js:4 × When I click the menu item "Home" # features\step_definitions\layout-steps.js:55 TimeoutError: Menu item "Home" not found Wait timed out after 8180ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - Then element with "text" "Home" should be visible # features\step_definitions\visibility-steps.js:54 - Then element with "text" "Search" should be visible # features\step_definitions\visibility-steps.js:54 - Then element with "text" "Account" should be visible # features\step_definitions\visibility-steps.js:54 √ After # features\support\scenario-hooks.js:36 8) Scenario: Navigate to submenu items - Part-dosing # features\DRTC\App-Home\mobile-navigation.feature:63 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 √ When I ensure the menu is open with "menu-toggle" # features\step_definitions\layout-steps.js:4 √ And I wait for 1 seconds # features\step_definitions\bstack-steps.js:456 × Given element with "text" "Background information" # features\step_definitions\visibility-steps.js:13 TimeoutError: Waiting element with locator to be visible Wait timed out after 30028ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 1 seconds # features\step_definitions\bstack-steps.js:456 - Given "a" element with "href" "/background/part-dosing" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Then I should be on the "/background/part-dosing" page # features\step_definitions\bstack-steps.js:384 √ After # features\support\scenario-hooks.js:36 9) Scenario: Search for monograph and verify content sections # features\DRTC\App-Monograph\monograph-content.feature:36 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30189ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I enter "Abilify" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Then "a" element with "href" "/monograph/aripiprazole" should be visible # features\step_definitions\visibility-steps.js:94 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Given "a" element with "text" "Enteral feeding tubes" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 1 seconds # features\step_definitions\bstack-steps.js:456 - Given "div" element with "text" "For people with enteral feeding tubes" # features\step_definitions\visibility-steps.js:25 - And I scroll to element # features\step_definitions\scroll-steps.js:9 - And I wait for 3 seconds # features\step_definitions\bstack-steps.js:456 - Then "div" element with "text" "For people with enteral feeding tubes" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 10) Scenario: Search for monograph and verify content sections # features\DRTC\App-Monograph\monograph-content.feature:37 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30155ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I enter "Amlo" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Then "a" element with "href" "/monograph/amlodipine" should be visible # features\step_definitions\visibility-steps.js:94 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Given "a" element with "text" "Enteral feeding tubes" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 1 seconds # features\step_definitions\bstack-steps.js:456 - Given "div" element with "text" "For people with enteral feeding tubes" # features\step_definitions\visibility-steps.js:25 - And I scroll to element # features\step_definitions\scroll-steps.js:9 - And I wait for 3 seconds # features\step_definitions\bstack-steps.js:456 - Then "div" element with "text" "For people with enteral feeding tubes" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 11) Scenario: Search for monograph and verify content sections # features\DRTC\App-Monograph\monograph-content.feature:38 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30151ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I enter "Bisalax" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Then "a" element with "href" "/monograph/bisacodyl" should be visible # features\step_definitions\visibility-steps.js:94 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Given "a" element with "text" "Enteral feeding tubes" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 1 seconds # features\step_definitions\bstack-steps.js:456 - Given "div" element with "text" "For people with enteral feeding tubes" # features\step_definitions\visibility-steps.js:25 - And I scroll to element # features\step_definitions\scroll-steps.js:9 - And I wait for 3 seconds # features\step_definitions\bstack-steps.js:456 - Then "div" element with "text" "For people with enteral feeding tubes" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 12) Scenario: Search for monograph and verify content sections # features\DRTC\App-Monograph\monograph-content.feature:39 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30208ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I enter "Parlodel" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Then "a" element with "href" "/monograph/bromocriptine" should be visible # features\step_definitions\visibility-steps.js:94 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Given "a" element with "text" "Enteral feeding tubes" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 1 seconds # features\step_definitions\bstack-steps.js:456 - Given "div" element with "text" "For people with enteral feeding tubes" # features\step_definitions\visibility-steps.js:25 - And I scroll to element # features\step_definitions\scroll-steps.js:9 - And I wait for 3 seconds # features\step_definitions\bstack-steps.js:456 - Then "div" element with "text" "For people with enteral feeding tubes" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 13) Scenario: Search for monograph and verify content sections # features\DRTC\App-Monograph\monograph-content.feature:40 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30184ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I enter "Amantamed" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Then "a" element with "href" "/monograph/amantadine" should be visible # features\step_definitions\visibility-steps.js:94 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Given "a" element with "text" "Swallowing difficulties" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 1 seconds # features\step_definitions\bstack-steps.js:456 - Given "div" element with "text" "For people with swallowing difficulties" # features\step_definitions\visibility-steps.js:25 - And I scroll to element # features\step_definitions\scroll-steps.js:9 - And I wait for 3 seconds # features\step_definitions\bstack-steps.js:456 - Then "div" element with "text" "For people with swallowing difficulties" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 14) Scenario: Search for monograph and verify content sections # features\DRTC\App-Monograph\monograph-content.feature:41 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30204ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I enter "Atovacue" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Then "a" element with "href" "/monograph/atovaquone" should be visible # features\step_definitions\visibility-steps.js:94 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Given "a" element with "text" "Swallowing difficulties" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 1 seconds # features\step_definitions\bstack-steps.js:456 - Given "div" element with "text" "For people with swallowing difficulties" # features\step_definitions\visibility-steps.js:25 - And I scroll to element # features\step_definitions\scroll-steps.js:9 - And I wait for 3 seconds # features\step_definitions\bstack-steps.js:456 - Then "div" element with "text" "For people with swallowing difficulties" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 15) Scenario: Search for monograph and verify content sections # features\DRTC\App-Monograph\monograph-content.feature:42 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30065ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I enter "Cotellic" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Then "a" element with "href" "/monograph/cobimetinib" should be visible # features\step_definitions\visibility-steps.js:94 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Given "a" element with "text" "Swallowing difficulties" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 1 seconds # features\step_definitions\bstack-steps.js:456 - Given "div" element with "text" "For people with swallowing difficulties" # features\step_definitions\visibility-steps.js:25 - And I scroll to element # features\step_definitions\scroll-steps.js:9 - And I wait for 3 seconds # features\step_definitions\bstack-steps.js:456 - Then "div" element with "text" "For people with swallowing difficulties" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 16) Scenario: Search for monograph and verify content sections # features\DRTC\App-Monograph\monograph-content.feature:43 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30139ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I enter "Combivir" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Then "a" element with "href" "/monograph/combivir" should be visible # features\step_definitions\visibility-steps.js:94 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Given "a" element with "text" "References" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 1 seconds # features\step_definitions\bstack-steps.js:456 - Given "div" element with "text" "References" # features\step_definitions\visibility-steps.js:25 - And I scroll to element # features\step_definitions\scroll-steps.js:9 - And I wait for 3 seconds # features\step_definitions\bstack-steps.js:456 - Then "div" element with "text" "References" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 17) Scenario: Search for monograph and verify content sections # features\DRTC\App-Monograph\monograph-content.feature:44 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30207ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I enter "Combivir" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Then "a" element with "href" "/monograph/combivir" should be visible # features\step_definitions\visibility-steps.js:94 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Given "a" element with "text" "References" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 1 seconds # features\step_definitions\bstack-steps.js:456 - Given "div" element with "text" "References" # features\step_definitions\visibility-steps.js:25 - And I scroll to element # features\step_definitions\scroll-steps.js:9 - And I wait for 3 seconds # features\step_definitions\bstack-steps.js:456 - Then "div" element with "text" "References" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 18) Scenario: Search for monograph and verify content sections # features\DRTC\App-Monograph\monograph-content.feature:45 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30221ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I enter "Calindamin" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Then "a" element with "href" "/monograph/clindamycin" should be visible # features\step_definitions\visibility-steps.js:94 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Given "a" element with "text" "References" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - And I wait for 1 seconds # features\step_definitions\bstack-steps.js:456 - Given "div" element with "text" "References" # features\step_definitions\visibility-steps.js:25 - And I scroll to element # features\step_definitions\scroll-steps.js:9 - And I wait for 3 seconds # features\step_definitions\bstack-steps.js:456 - Then "div" element with "text" "References" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 19) Scenario: Searching for Vad in the drug search input with no matches # features\DRTC\App-Monograph\monograph-search.feature:16 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30211ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - When I enter "Vad" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - And "p" element with "text" "0 results found" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 20) Scenario: Searching for XYZ in the drug search input with no matches # features\DRTC\App-Monograph\monograph-search.feature:17 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30236ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - When I enter "XYZ" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - And "p" element with "text" "0 results found" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 21) Scenario: Searching for xq in the drug search input with no matches # features\DRTC\App-Monograph\monograph-search.feature:18 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30016ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - When I enter "xq" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - And "p" element with "text" "0 results found" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 22) Scenario: Searching for Hgcyum in the drug search input with no matches # features\DRTC\App-Monograph\monograph-search.feature:19 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30209ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - When I enter "Hgcyum" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - And "p" element with "text" "0 results found" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 23) Scenario: Monograph-Browse By Categories Abilify-aripiprazole # features\DRTC\App-Monograph\monograph-search.feature:34 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30089ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - When I enter "aripiprazole" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - Given "a" element with "href" "/monograph/aripiprazole" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - Then I should be on the "/monograph/aripiprazole" page # features\step_definitions\bstack-steps.js:384 √ After # features\support\scenario-hooks.js:36 24) Scenario: Monograph-Browse By Categories Bicard-bisoprolol # features\DRTC\App-Monograph\monograph-search.feature:35 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30021ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - When I enter "bisoprolol" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - Given "a" element with "href" "/monograph/bisoprolol" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - Then I should be on the "/monograph/bisoprolol" page # features\step_definitions\bstack-steps.js:384 √ After # features\support\scenario-hooks.js:36 25) Scenario: Monograph-Browse By Categories Carvidol-carvedilol # features\DRTC\App-Monograph\monograph-search.feature:36 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30026ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - When I enter "carvedilol" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - Given "a" element with "href" "/monograph/carvedilol" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - Then I should be on the "/monograph/carvedilol" page # features\step_definitions\bstack-steps.js:384 √ After # features\support\scenario-hooks.js:36 26) Scenario: Monograph-Browse By Categories Domion-agomelatine # features\DRTC\App-Monograph\monograph-search.feature:37 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30199ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - When I enter "agomelatine" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - Given "a" element with "href" "/monograph/agomelatine" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - Then I should be on the "/monograph/agomelatine" page # features\step_definitions\bstack-steps.js:384 √ After # features\support\scenario-hooks.js:36 27) Scenario: Monograph-Browse By Categories Esopreze-esomeprazole # features\DRTC\App-Monograph\monograph-search.feature:38 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30004ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - When I enter "esomeprazole" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - Given "a" element with "href" "/monograph/esomeprazole" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - Then I should be on the "/monograph/esomeprazole" page # features\step_definitions\bstack-steps.js:384 √ After # features\support\scenario-hooks.js:36 28) Scenario: Monograph-Browse By Categories Mektovi-binimetinib # features\DRTC\App-Monograph\monograph-search.feature:39 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30048ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - When I enter "binimetinib" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - Given "a" element with "href" "/monograph/binimetinib" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - Then I should be on the "/monograph/binimetinib" page # features\step_definitions\bstack-steps.js:384 √ After # features\support\scenario-hooks.js:36 29) Scenario: Monograph-Browse By Categories Neoral-ciclosporin # features\DRTC\App-Monograph\monograph-search.feature:40 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30146ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - When I enter "ciclosporin" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - Given "a" element with "href" "/monograph/ciclosporin" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - Then I should be on the "/monograph/ciclosporin" page # features\step_definitions\bstack-steps.js:384 √ After # features\support\scenario-hooks.js:36 30) Scenario: Monograph-Browse By Categories Onureg-azacitadine # features\DRTC\App-Monograph\monograph-search.feature:41 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30079ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - When I enter "azacitadine" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - Given "a" element with "href" "/monograph/azacitadine" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - Then I should be on the "/monograph/azacitadine" page # features\step_definitions\bstack-steps.js:384 √ After # features\support\scenario-hooks.js:36 31) Scenario: Monograph-Browse By Categories Pulmoris-ambrisentan # features\DRTC\App-Monograph\monograph-search.feature:42 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30179ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - When I enter "ambrisentan" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - Given "a" element with "href" "/monograph/ambrisentan" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - Then I should be on the "/monograph/ambrisentan" page # features\step_definitions\bstack-steps.js:384 √ After # features\support\scenario-hooks.js:36 32) Scenario: Monograph-Browse By Categories Solian-amisulpride # features\DRTC\App-Monograph\monograph-search.feature:43 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30009ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - When I enter "amisulpride" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - Given "a" element with "href" "/monograph/amisulpride" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - Then I should be on the "/monograph/amisulpride" page # features\step_definitions\bstack-steps.js:384 √ After # features\support\scenario-hooks.js:36 33) Scenario: Monograph-Browse By Categories Xelabine-capecitabine # features\DRTC\App-Monograph\monograph-search.feature:44 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30058ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - When I enter "capecitabine" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - Given "a" element with "href" "/monograph/capecitabine" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - Then I should be on the "/monograph/capecitabine" page # features\step_definitions\bstack-steps.js:384 √ After # features\support\scenario-hooks.js:36 34) Scenario: Monograph-Browse By Categories Zytiga-abiraterone # features\DRTC\App-Monograph\monograph-search.feature:45 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I force PWA mode # features\step_definitions\featureToggles\featureToggles.js:2 √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 × Given "input" element with "placeholder" "Search" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30111ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - When I enter "abiraterone" # features\step_definitions\element-steps.js:62 - When I press enter on element # features\step_definitions\element-steps.js:137 - Given "a" element with "href" "/monograph/abiraterone" # features\step_definitions\visibility-steps.js:25 - Then I scroll to element # features\step_definitions\scroll-steps.js:9 - And I click on element # features\step_definitions\element-steps.js:23 - Then I should be on the "/monograph/abiraterone" page # features\step_definitions\bstack-steps.js:384 √ After # features\support\scenario-hooks.js:36 35) Scenario: PWA Verify My Account -menu-whats-new # features\DRTC\My-Account\my-account.feature:13 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I setup "PWA" mode # features\step_definitions\featureToggles\featureToggles.js:13 × Given "a" element with "href" "/account" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30002ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - When I click on element # features\step_definitions\element-steps.js:23 - When I wait for 4 seconds # features\step_definitions\bstack-steps.js:456 - Then "button" element with "data-testid" "menu-whats-new" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 36) Scenario: PWA Verify My Account -menu-about-legal # features\DRTC\My-Account\my-account.feature:14 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I setup "PWA" mode # features\step_definitions\featureToggles\featureToggles.js:13 × Given "a" element with "href" "/account" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30036ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - When I click on element # features\step_definitions\element-steps.js:23 - When I wait for 4 seconds # features\step_definitions\bstack-steps.js:456 - Then "button" element with "data-testid" "menu-about-legal" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 37) Scenario: PWA Verify My Account-About Us Legal -about-link-0 # features\DRTC\My-Account\my-account.feature:25 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I setup "PWA" mode # features\step_definitions\featureToggles\featureToggles.js:13 × Given "a" element with "href" "/account" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30063ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - When I click on element # features\step_definitions\element-steps.js:23 - When I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Given element with "data-testid" "menu-about-legal" # features\step_definitions\visibility-steps.js:13 - When I click on element # features\step_definitions\element-steps.js:23 - Then "a" element with "data-testid" "about-link-0" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 38) Scenario: PWA Verify My Account-About Us Legal -about-link-1 # features\DRTC\My-Account\my-account.feature:26 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I setup "PWA" mode # features\step_definitions\featureToggles\featureToggles.js:13 × Given "a" element with "href" "/account" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30168ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - When I click on element # features\step_definitions\element-steps.js:23 - When I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Given element with "data-testid" "menu-about-legal" # features\step_definitions\visibility-steps.js:13 - When I click on element # features\step_definitions\element-steps.js:23 - Then "a" element with "data-testid" "about-link-1" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 39) Scenario: PWA Verify My Account-About Us Legal -about-link-2 # features\DRTC\My-Account\my-account.feature:27 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I setup "PWA" mode # features\step_definitions\featureToggles\featureToggles.js:13 × Given "a" element with "href" "/account" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30040ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - When I click on element # features\step_definitions\element-steps.js:23 - When I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Given element with "data-testid" "menu-about-legal" # features\step_definitions\visibility-steps.js:13 - When I click on element # features\step_definitions\element-steps.js:23 - Then "a" element with "data-testid" "about-link-2" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 40) Scenario: PWA Verify My Account-About Us Legal -about-link-3 # features\DRTC\My-Account\my-account.feature:28 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I setup "PWA" mode # features\step_definitions\featureToggles\featureToggles.js:13 × Given "a" element with "href" "/account" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30134ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - When I click on element # features\step_definitions\element-steps.js:23 - When I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 - Given element with "data-testid" "menu-about-legal" # features\step_definitions\visibility-steps.js:13 - When I click on element # features\step_definitions\element-steps.js:23 - Then "a" element with "data-testid" "about-link-3" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 41) Scenario: PWA Verify My Account-About Us Legal -about-link-4 # features\DRTC\My-Account\my-account.feature:29 √ Before # features\support\scenario-hooks.js:6 √ Before # features\support\scenario-hooks.js:23 √ Given I visit "http://localhost:3000/" # features\step_definitions\navigation-steps.js:9 √ Given I setup "PWA" mode # features\step_definitions\featureToggles\featureToggles.js:13 × Given "a" element with "href" "/account" # features\step_definitions\visibility-steps.js:25 TimeoutError: Waiting element with locator to be visible Wait timed out after 30127ms at C:\agent\_work\35\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) - When I click on element # features\step_definitions\element-steps.js:23 - When I wait for 2 seconds # features\step_definitions\bstack-steps.js:456 node.exe : ┌──────────────────────────────────────────────────────────────────────────────┐ At C:\agent\_work\35\s\node_modules\.bin\cross-env.ps1:24 char:5 + & "node$exe" "$basedir/../cross-env/dist/bin/cross-env.js" $args + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (┌─────────...─────────┐:String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError │ Share your Cucumber Report with your team at https://reports.cucumber.io │ │ │ │ Command line option: --publish │ │ Environment variable: CUCUMBER_PUBLISH_ENABLED=true │ │ │ │ More information at https://cucumber.io/docs/cucumber/environment-variables/ │ │ │ │ To disable this message, add this to your ./cucumber.js: │ - Given element with "data-testid" "menu-about-legal" # features\step_definitions\visibility-steps.js:13 - When I click on element # features\step_definitions\element-steps.js:23 - Then "a" element with "data-testid" "about-link-4" should be visible # features\step_definitions\visibility-steps.js:94 √ After # features\support\scenario-hooks.js:36 171 scenarios (41 failed, 47 skipped, 83 passed) 1705 steps (41 failed, 876 skipped, 788 passed) 6m58.046s (executing steps: 41m30.130s) │ module.exports = { default: '--publish-quiet' } │ └──────────────────────────────────────────────────────────────────────────────┘