hooks TGL_Device: web process.env.USE_LOCAL true process.env.LOCAL_BROWSERSTACK false ,process.env.USE_LOCAL, true,process.env.LOCAL_SHOW_BROWSER , false, TGL_Device, web
[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: 🔐 encrypt with Dotenvx: https://dotenvx.com
[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: ⚙️  enable debug logging with { debug: true }
[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 building .env in docker: https://dotenvx.com/prebuild
[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: ⚙️  suppress all logs with { quiet: true }
hooks TGL_Device: web process.env.USE_LOCAL true process.env.LOCAL_BROWSERSTACK false ,process.env.USE_LOCAL, true,process.env.LOCAL_SHOW_BROWSER , false, TGL_Device, web
[dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️  write to custom object with { processEnv: myObject }
hooks TGL_Device: web process.env.USE_LOCAL true process.env.LOCAL_BROWSERSTACK false ,process.env.USE_LOCAL, true,process.env.LOCAL_SHOW_BROWSER , false, TGL_Device, web
[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: 📡 auto-backup 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
[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: 🛠️  run anywhere with `dotenvx run -- yourcommand`
[dotenv@17.2.1] injecting env (0) from .env -- tip: 🛠️  run anywhere with `dotenvx run -- yourcommand`
NO driver -After scenario "PWA Navigate to  How to use Don't Rush to Crush": Driver was not initialized, skipping quit.
-------------.----NO driver -After scenario "PWA Navigate to  Before you rush to crush": Driver was not initialized, skipping quit.
---------.----NO driver -After scenario "PWA Navigate to  Enteral feeding tubes": Driver was not initialized, skipping quit.
---------.----NO driver -After scenario "PWA Navigate to  Swallowing difficulties": Driver was not initialized, skipping quit.
---------.---NO driver -After scenario "PWA Navigate to  Gastrointestinal dysfunction": Driver was not initialized, skipping quit.
----------.---NO driver -After scenario "PWA Navigate to  Part-dosing": Driver was not initialized, skipping quit.
----------.--NO driver -After scenario "PWA Navigate to  Acknowledgments": Driver was not initialized, skipping quit.
-----------.--NO driver -After scenario "Quick Access buttons navigation": Driver was not initialized, skipping quit.
--------.--NO driver -After scenario "Quick Access buttons navigation": Driver was not initialized, skipping quit.
--------.--NO driver -After scenario "Quick Access buttons navigation": Driver was not initialized, skipping quit.
--------.-NO driver -After scenario "Navigate to direct link pages from menu - Quick Guide Symbols": Driver was not initialized, skipping quit.
---------.-NO driver -After scenario "Navigate to direct link pages from menu - Methods": Driver was not initialized, skipping quit.
---------.-NO driver -After scenario "Navigate to direct link pages from menu - Glossary": Driver was not initialized, skipping quit.
---------.--NO driver -After scenario "Navigate to direct link pages from menu - Favourites": Driver was not initialized, skipping quit.
--------.--NO driver -After scenario "Navigate to direct link pages from menu - What's New": Driver was not initialized, skipping quit.
--------.--NO driver -After scenario "Navigate to submenu items - How to use Don't Rush to Crush": Driver was not initialized, skipping quit.
-------------.-NO driver -After scenario "Navigate to submenu items - Before you rush to crush": Driver was not initialized, skipping quit.
--------------.----NO driver -After scenario "Navigate to submenu items - Decision making process": Driver was not initialized, skipping quit.
-----------.--NO driver -After scenario "Navigate to submenu items - Enteral feeding tubes": Driver was not initialized, skipping quit.
----[dotenv@17.2.1] injecting env (0) from .env -- tip: 📡 auto-backup env with Radar: https://dotenvx.com/radar
---------.---NO driver -After scenario "Navigate to submenu items - Equipment": Driver was not initialized, skipping quit.
------------.----NO driver -After scenario "Navigate to submenu items - Gastrointestinal dysfunction": Driver was not initialized, skipping quit.
-----------.---NO driver -After scenario "Navigate to submenu items - Swallowing difficulties": Driver was not initialized, skipping quit.
------------.-----NO driver -After scenario "Navigate to submenu items - Oral liquids and thickness testing": Driver was not initialized, skipping quit.
----------.-----NO driver -After scenario "Navigate to submenu items - Part-dosing": 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.
--------------[dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️  override existing env vars with { override: true }
--.--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.
-----------------.[dotenv@17.2.1] injecting env (0) from .env -- tip: 🔐 encrypt with Dotenvx: https://dotenvx.com
--NO driver -After scenario "Searching for Vad in the drug search input with  no matches": Driver was not initialized, skipping quit.
---[dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️  override existing env vars with { override: true }
---.--NO driver -After scenario "Searching for XYZ in the drug search input with  no matches": Driver was not initialized, skipping quit.
------.--NO driver -After scenario "Searching for xq in the drug search input with  no matches": Driver was not initialized, skipping quit.
------.[dotenv@17.2.1] injecting env (0) from .env -- tip: 🔐 prevent committing .env to code: https://dotenvx.com/precommit
--NO driver -After scenario "Searching for Hgcyum in the drug search input with  no matches": Driver was not initialized, skipping quit.
------.[dotenv@17.2.1] injecting env (0) from .env -- tip: 🛠️  run anywhere with `dotenvx run -- yourcommand`
---NO driver -After scenario "Monograph-Browse By Categories Abilify-aripiprazole": Driver was not initialized, skipping quit.
--------.---NO driver -After scenario "Monograph-Browse By Categories Bicard-bisoprolol": Driver was not initialized, skipping quit.
----[dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️  suppress all logs with { quiet: true }
----.--NO driver -After scenario "Monograph-Browse By Categories Carvidol-carvedilol": Driver was not initialized, skipping quit.
---------.-NO driver -After scenario "Monograph-Browse By Categories Domion-agomelatine": Driver was not initialized, skipping quit.
----[dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️  enable debug logging with { debug: true }
------.----NO driver -After scenario "Monograph-Browse By Categories Esopreze-esomeprazole": Driver was not initialized, skipping quit.
-------.---NO driver -After scenario "Monograph-Browse By Categories Mektovi-binimetinib": Driver was not initialized, skipping quit.
--------.----NO driver -After scenario "Monograph-Browse By Categories Neoral-ciclosporin": Driver was not initialized, skipping quit.
-------.----NO driver -After scenario "Monograph-Browse By Categories Onureg-azacitadine": Driver was not initialized, skipping quit.
-------.----NO driver -After scenario "Monograph-Browse By Categories Pulmoris-ambrisentan": Driver was not initialized, skipping quit.
-------.----NO driver -After scenario "Monograph-Browse By Categories Solian-amisulpride": Driver was not initialized, skipping quit.
-------.----NO driver -After scenario "Monograph-Browse By Categories Xelabine-capecitabine": Driver was not initialized, skipping quit.
-------.---NO driver -After scenario "Monograph-Browse By Categories Zytiga-abiraterone": Driver was not initialized, skipping quit.
--------.Before scenario name Search for various brand names and verify main drug appears
.-----NO driver -After scenario "Verify What's New page content is visible": Driver was not initialized, skipping quit.
..Before scenario name Search for various brand names and verify main drug appears
hooks TGL_Device: web process.env.USE_LOCAL true process.env.LOCAL_BROWSERSTACK false ,process.env.USE_LOCAL, true,process.env.LOCAL_SHOW_BROWSER , false, TGL_Device, web
[dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️  override existing env vars with { override: true }
hooks TGL_Device: web process.env.USE_LOCAL true process.env.LOCAL_BROWSERSTACK false ,process.env.USE_LOCAL, true,process.env.LOCAL_SHOW_BROWSER , false, TGL_Device, web
[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: ⚙️  suppress all logs with { quiet: 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: ⚙️  override existing env vars with { override: true }
[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: ⚙️  suppress all logs with { quiet: true }
[dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️  override existing env vars with { override: true }
.Before scenario name Search for various brand names and verify main drug appears
[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: ⚙️  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
[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: 🔐 encrypt with Dotenvx: https://dotenvx.com
[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: 📡 auto-backup env with Radar: https://dotenvx.com/radar
.Before scenario name Search for various brand names and verify main drug appears
hooks TGL_Device: web process.env.USE_LOCAL true process.env.LOCAL_BROWSERSTACK false ,process.env.USE_LOCAL, true,process.env.LOCAL_SHOW_BROWSER , false, TGL_Device, web
[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: ⚙️  override existing env vars with { override: true }
[dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️  suppress all logs with { quiet: true }
hooks TGL_Device: web process.env.USE_LOCAL true process.env.LOCAL_BROWSERSTACK false ,process.env.USE_LOCAL, true,process.env.LOCAL_SHOW_BROWSER , false, TGL_Device, web
[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: ⚙️  specify custom .env file path with { path: '/custom/path/.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: ⚙️  load multiple .env files with { path: ['.env.local', '.env'] }
.Before scenario name Search for various brand names and verify main drug appears
[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: 📡 auto-backup env with Radar: https://dotenvx.com/radar
[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: ⚙️  write to custom object with { processEnv: myObject }
[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: ⚙️  enable debug logging with { debug: true }
[dotenv@17.2.1] injecting env (0) from .env -- tip: ⚙️  suppress all logs with { quiet: true }
.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
..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
.......F----F----F----.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
.......F----.F----F-..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 Warning callout displays prominently
...............Before scenario name Glossary Functionality -absorption
..Desktop: menu toggle not found → menu already open
.Clicking menu item: Glossary
...Before scenario name Glossary Functionality -bioavailability
..F----F.Desktop: menu toggle not found → menu already open
.Clicking menu item: Glossary
.Before scenario name Glossary Functionality -bioequivalent
..Before scenario name Glossary Functionality -disperse
...F----...Before scenario name Glossary Functionality -high osmolarity
..Before scenario name Clicking A-Z button A on Glossary page navigates correctly to A 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
.......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
.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 D on Glossary page navigates correctly to D section
...F----..Before scenario name Clicking A-Z button H on Glossary page navigates correctly to H section
....F----......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
..Before scenario name Navigate to  How to use Don't Rush to Crush
...Before scenario name Navigate to  Before you rush to crush
.....Before scenario name Navigate to  Acknowledgments
.....Desktop: menu toggle not found → menu already open
.Clicking menu item: Glossary
Desktop: menu toggle not found → menu already open
.Clicking menu item: Home
..Desktop: menu toggle not found → menu already open
Clicking menu item: Home
......Before scenario name Navigate to  Enteral feeding tubes
....Desktop: menu toggle not found → menu already open
.Clicking menu item: Home
................Desktop: menu toggle not found → menu already open
.Clicking menu item: Home
...Before scenario name Navigate to  Swallowing difficulties
...........Desktop: menu toggle not found → menu already open
.Clicking menu item: Home
.Before scenario name Navigate to  Gastrointestinal dysfunction
........Desktop: menu toggle not found → menu already open
.Clicking menu item: Home
.....F---F---.Before scenario name Navigate to  Part-dosing
..Before scenario name Verify tab Enteral feeding tubes is visible and clickable
.F---...Before scenario name Verify tab Swallowing difficulties is visible and clickable
...Desktop: menu toggle not found → menu already open
.Clicking menu item: Home
F---..Before scenario name Switch to Enteral feeding tubes tab and verify content
........F---..Before scenario name Switch to Swallowing difficulties tab and verify content
..F---.Before scenario name Verify method section Method A. Disperse the tablet under Enteral feeding tubes tab
....F-----F-----.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
..F---..Before scenario name Expand method sections under "Enteral feeding tubes" - Method A. Disperse the tablet
.F----....Before scenario name Expand method sections under "Enteral feeding tubes" - Method B. Crush the tablet
....F----.Before scenario name Expand method sections under "Enteral feeding tubes" - Method C. Disperse the contents of a capsule or sachet
.F-------....Before scenario name Expand method sections under "Swallowing difficulties" - Method D. Disperse the tablet
..F-------F-------.Before scenario name Expand method sections under "Swallowing difficulties" - Method E. Crush the tablet
..F-------.Before scenario name Expand method sections under "Swallowing difficulties" - Method F. Disperse the contents of the capsule or sachet
....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-------..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-------.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-------...Before scenario name Search for monograph and verify content sections
.....................F-------.Before scenario name Glossary Link-Monograph Page  Abilify-aripiprazole
..........F-------...Before scenario name Glossary Link-Monograph Page  Bicalox-bicalutamide
....................Before scenario name Glossary Link-Monograph Page  Amlodipine-amlodipine
...F-------.Before scenario name Verify My Account -Favourites
.F-------...........---NO driver -After scenario "PWA Verify My Account -menu-whats-new": Driver was not initialized, skipping quit.
-.-NO driver -After scenario "PWA Verify My Account -menu-about-legal": Driver was not initialized, skipping quit.
---.-NO driver -After scenario "PWA Verify My Account-About Us Legal -about-link-0": Driver was not initialized, skipping quit.
-----.--NO driver -After scenario "PWA Verify My Account-About Us Legal -about-link-1": Driver was not initialized, skipping quit.
----.--NO driver -After scenario "PWA Verify My Account-About Us Legal -about-link-2": Driver was not initialized, skipping quit.
----.-NO driver -After scenario "PWA Verify My Account-About Us Legal -about-link-3": Driver was not initialized, skipping quit.
-----.--NO driver -After scenario "PWA Verify My Account-About Us Legal -about-link-4": Driver was not initialized, skipping quit.
----.Before scenario name Load page and verify initial state
.................Before scenario name Verify symbol Oral liquids tile is visible in the grid
..........Before scenario name Verify symbol Disperse the tablet tile is visible in the grid
...........F-------.Before scenario name Verify symbol Open the capsule tile is visible in the grid
.......Before scenario name Verify symbol Crush the tablet tile is visible in the grid
...Before scenario name Verify symbol Do not crush tile is visible in the grid
......Before scenario name Verify symbol Do not open the capsule tile is visible in the grid
.F-------........Before scenario name Verify symbol Cytotoxic medicines tile is visible in the grid
...........Before scenario name Verify symbol Hazardous medicine tile is visible in the grid
..Before scenario name Verify symbol details for Oral liquids
........Before scenario name Verify symbol details for Disperse the tablet
..Before scenario name Verify symbol details for Open the capsule
.............Before scenario name Verify symbol details for Crush the tablet
......Before scenario name Verify symbol details for Do not crush
...........................Before scenario name Verify symbol details for Do not open the capsule
..................Before scenario name Verify symbol details for Cytotoxic medicines
......Before scenario name Verify symbol details for Hazardous medicine
.----NO driver -After scenario "Verify symbol Oral liquids tile is visible in the grid on mobile": Driver was not initialized, skipping quit.
-------.--NO driver -After scenario "Verify symbol Disperse the tablet tile is visible in the grid on mobile": Driver was not initialized, skipping quit.
---------.------NO driver -After scenario "Verify symbol Open the capsule tile is visible in the grid on mobile": Driver was not initialized, skipping quit.
-----.---NO driver -After scenario "Verify symbol Crush the tablet tile is visible in the grid on mobile": Driver was not initialized, skipping quit.
--------.NO driver -After scenario "Verify symbol Do not crush tile is visible in the grid on mobile": Driver was not initialized, skipping quit.
-----------.--NO driver -After scenario "Verify symbol Do not open the capsule tile is visible in the grid on mobile": Driver was not initialized, skipping quit.
---------.---NO driver -After scenario "Verify symbol Cytotoxic medicines tile is visible in the grid on mobile": Driver was not initialized, skipping quit.
--------.----NO driver -After scenario "Verify symbol Hazardous medicine tile is visible in the grid on mobile": Driver was not initialized, skipping quit.
-------.---NO driver -After scenario "Verify symbol details for Oral liquids on mobile": Driver was not initialized, skipping quit.
--------.---NO driver -After scenario "Verify symbol details for Disperse the tablet on mobile": Driver was not initialized, skipping quit.
--------.---NO driver -After scenario "Verify symbol details for Open the capsule on mobile": Driver was not initialized, skipping quit.
--------.---NO driver -After scenario "Verify symbol details for Crush the tablet on mobile": Driver was not initialized, skipping quit.
--------.---NO driver -After scenario "Verify symbol details for Do not crush on mobile": Driver was not initialized, skipping quit.
--------.---NO driver -After scenario "Verify symbol details for Do not open the capsule on mobile": Driver was not initialized, skipping quit.
--------.------NO driver -After scenario "Verify symbol details for Cytotoxic medicines on mobile": Driver was not initialized, skipping quit.
-----.---NO driver -After scenario "Verify symbol details for Hazardous medicine on mobile": Driver was not initialized, skipping quit.
--------.Before scenario name Navigate to top-level pages - Home
.......Before scenario name Navigate to top-level pages - Favourites
........Before scenario name Navigate to top-level pages - Glossary
...Desktop: menu toggle not found → menu already open
.Clicking menu item: Home
..........Desktop: menu toggle not found → menu already open
.Clicking menu item: Favourites
.....Desktop: menu toggle not found → menu already open
.Clicking menu item: Glossary
........Before scenario name Navigate to direct link pages - Glossary
........Before scenario name Navigate to direct link pages - What's New
.......Before scenario name Navigate to About this resource submenu items - How to use Don't Rush to Crush
...Before scenario name Navigate to About this resource submenu items - Before you rush to crush
..Before scenario name Navigate to About this resource submenu items - Decision making process
..Before scenario name Navigate to direct links under Home submenu - Quick guide symbols
....Desktop: menu toggle not found → menu already open
....Desktop: menu toggle not found → menu already open
.......Desktop: menu toggle not found → menu already open
...Desktop: menu toggle not found → menu already open
......Desktop: menu toggle not found → menu already open
.Desktop: menu toggle not found → menu already open
...................................Before scenario name Navigate to direct links under Home submenu - Methods
...Before scenario name Navigate to Background information submenu items - Enteral feeding tubes
...Before scenario name Navigate to Background information submenu items - Equipment
......Before scenario name Navigate to Background information submenu items - Gastrointestinal dysfunction
..Before scenario name Navigate to Background information submenu items - Swallowing difficulties
.....Before scenario name Navigate to Background information submenu items - Oral liquids and thickness testing
..Desktop: menu toggle not found → menu already open
..Desktop: menu toggle not found → menu already open
....Desktop: menu toggle not found → menu already open
.......Desktop: menu toggle not found → menu already open
.......Desktop: menu toggle not found → menu already open
..........Desktop: menu toggle not found → menu already open
.................................Before scenario name Navigate to Background information submenu items - Part-dosing
..Before scenario name What's New Functionality
..........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
..Desktop: menu toggle not found → menu already open
.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


Failures:

1) Scenario: Switch to Proton pump inhibitors tab and verify content # features\DRTC\ComparativeTables\comparative-tables.feature:22
   √ Before # features\support\scenario-hooks.js:6
   √ Before # features\support\scenario-hooks.js:23
   √ Given I visit "http://localhost:3000/background/comparative-tables" # features\step_definitions\navigation-steps.js:9
   √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456
   × Given "a" element with "text" "Proton pump inhibitors" # features\step_definitions\visibility-steps.js:25
       TimeoutError: Waiting element with locator to be visible
       Wait timed out after 30114ms
           at C:\agent\_work\34\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 2 seconds # features\step_definitions\bstack-steps.js:456
   - Then element with "text" "Comparative information for proton pump inhibitors" should be visible # features\step_definitions\visibility-steps.js:54
   √ After # features\support\scenario-hooks.js:36

2) Scenario: Switch to ACE inhibitors tab and verify content # features\DRTC\ComparativeTables\comparative-tables.feature:23
   √ Before # features\support\scenario-hooks.js:6
   √ Before # features\support\scenario-hooks.js:23
   √ Given I visit "http://localhost:3000/background/comparative-tables" # features\step_definitions\navigation-steps.js:9
   √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456
   × Given "a" element with "text" "ACE inhibitors" # features\step_definitions\visibility-steps.js:25
       TimeoutError: Waiting element with locator to be visible
       Wait timed out after 30027ms
           at C:\agent\_work\34\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 2 seconds # features\step_definitions\bstack-steps.js:456
   - Then element with "text" "Comparative information for ACE inhibitors" should be visible # features\step_definitions\visibility-steps.js:54
   √ After # features\support\scenario-hooks.js:36

3) Scenario: Switch to Statins tab and verify content # features\DRTC\ComparativeTables\comparative-tables.feature:24
   √ Before # features\support\scenario-hooks.js:6
   √ Before # features\support\scenario-hooks.js:23
   √ Given I visit "http://localhost:3000/background/comparative-tables" # features\step_definitions\navigation-steps.js:9
   √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456
   × Given "a" element with "text" "Statins" # features\step_definitions\visibility-steps.js:25
       TimeoutError: Waiting element with locator to be visible
       Wait timed out after 30127ms
           at C:\agent\_work\34\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 2 seconds # features\step_definitions\bstack-steps.js:456
   - Then element with "text" "Comparative information for statins" should be visible # features\step_definitions\visibility-steps.js:54
   √ After # features\support\scenario-hooks.js:36

4) Scenario: Switch to Antipsychotics tab and verify content # features\DRTC\ComparativeTables\comparative-tables.feature:25
   √ Before # features\support\scenario-hooks.js:6
   √ Before # features\support\scenario-hooks.js:23
   √ Given I visit "http://localhost:3000/background/comparative-tables" # features\step_definitions\navigation-steps.js:9
   √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456
   × Given "a" element with "text" "Antipsychotics" # features\step_definitions\visibility-steps.js:25
       TimeoutError: Waiting element with locator to be visible
       Wait timed out after 30006ms
           at C:\agent\_work\34\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 2 seconds # features\step_definitions\bstack-steps.js:456
   - Then element with "text" "Comparative information for antipsychotics" should be visible # features\step_definitions\visibility-steps.js:54
   √ After # features\support\scenario-hooks.js:36

5) Scenario: Switch to Antidepressants tab and verify content # features\DRTC\ComparativeTables\comparative-tables.feature:26
   √ Before # features\support\scenario-hooks.js:6
   √ Before # features\support\scenario-hooks.js:23
   √ Given I visit "http://localhost:3000/background/comparative-tables" # features\step_definitions\navigation-steps.js:9
   √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456
   × Given "a" element with "text" "Antidepressants" # features\step_definitions\visibility-steps.js:25
       TimeoutError: Waiting element with locator to be visible
       Wait timed out after 30028ms
           at C:\agent\_work\34\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 2 seconds # features\step_definitions\bstack-steps.js:456
   - Then element with "text" "Comparative information for antidepressants" should be visible # features\step_definitions\visibility-steps.js:54
   √ After # features\support\scenario-hooks.js:36

6) Scenario: View decision-making process page # features\DRTC\DecisionMakingProcess\decision-making-process.feature:3
   √ Before # features\support\scenario-hooks.js:6
   √ Before # features\support\scenario-hooks.js:23
   √ Given I visit "http://localhost:3000/background/decision-making-process" # features\step_definitions\navigation-steps.js:9
   × Then element with "text" "The decision-making process" should be visible # features\step_definitions\visibility-steps.js:54
       TimeoutError: Waiting element with locator to be visible
       Wait timed out after 30158ms
           at C:\agent\_work\34\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17
           at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
   - And element with "text" "Decision pathway for medication modification in patients with swallowing difficulties or an enteral tube" should be visible # features\step_definitions\visibility-steps.js:54
   √ After # features\support\scenario-hooks.js:36

7) Scenario: Load Equipment page and verify page header # features\DRTC\Equipment\equipment.feature:8
   √ Before # features\support\scenario-hooks.js:6
   √ Before # features\support\scenario-hooks.js:23
   √ Given I visit "http://localhost:3000/background/equipment" # features\step_definitions\navigation-steps.js:9
   √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456
   √ Then I should be on the "/background/equipment" page # features\step_definitions\bstack-steps.js:384
   × And element with "text" "Equipment" should be visible # features\step_definitions\visibility-steps.js:54
       TimeoutError: Waiting element with locator to be visible
       Wait timed out after 30231ms
           at C:\agent\_work\34\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17
           at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
   √ After # features\support\scenario-hooks.js:36

8) Scenario: Switch to Equipment tab and verify content # features\DRTC\Equipment\equipment.feature:22
   √ Before # features\support\scenario-hooks.js:6
   √ Before # features\support\scenario-hooks.js:23
   √ Given I visit "http://localhost:3000/background/equipment" # features\step_definitions\navigation-steps.js:9
   √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456
   × Given "a" element with "text" "Equipment" # features\step_definitions\visibility-steps.js:25
       TimeoutError: Waiting element with locator to be visible
       Wait timed out after 30032ms
           at C:\agent\_work\34\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 2 seconds # features\step_definitions\bstack-steps.js:456
   - Then element with "text" "Equipment" should be visible # features\step_definitions\visibility-steps.js:54
   √ After # features\support\scenario-hooks.js:36

9) Scenario: Switch to Preventing wrong-route tab and verify content # features\DRTC\Equipment\equipment.feature:23
   √ Before # features\support\scenario-hooks.js:6
   √ Before # features\support\scenario-hooks.js:23
   √ Given I visit "http://localhost:3000/background/equipment" # features\step_definitions\navigation-steps.js:9
   √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456
   × Given "a" element with "text" "Preventing wrong-route" # features\step_definitions\visibility-steps.js:25
       TimeoutError: Waiting element with locator to be visible
       Wait timed out after 30056ms
           at C:\agent\_work\34\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 2 seconds # features\step_definitions\bstack-steps.js:456
   - Then element with "text" "Preventing wrong-route" should be visible # features\step_definitions\visibility-steps.js:54
   √ After # features\support\scenario-hooks.js:36

10) Scenario: Switch to EnFit connectors tab and verify content # features\DRTC\Equipment\equipment.feature:24
    √ Before # features\support\scenario-hooks.js:6
    √ Before # features\support\scenario-hooks.js:23
    √ Given I visit "http://localhost:3000/background/equipment" # features\step_definitions\navigation-steps.js:9
    √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456
    × Given "a" element with "text" "EnFit connectors" # features\step_definitions\visibility-steps.js:25
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30042ms
            at C:\agent\_work\34\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 2 seconds # features\step_definitions\bstack-steps.js:456
    - Then element with "text" "EnFit connectors" should be visible # features\step_definitions\visibility-steps.js:54
    √ After # features\support\scenario-hooks.js:36

11) Scenario: Switch to Crushing devices tab and verify content # features\DRTC\Equipment\equipment.feature:25
    √ Before # features\support\scenario-hooks.js:6
    √ Before # features\support\scenario-hooks.js:23
    √ Given I visit "http://localhost:3000/background/equipment" # features\step_definitions\navigation-steps.js:9
    √ And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456
    × Given "a" element with "text" "Crushing devices" # features\step_definitions\visibility-steps.js:25
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30048ms
            at C:\agent\_work\34\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 2 seconds # features\step_definitions\bstack-steps.js:456
    - Then element with "text" "Crushing devices" should be visible # features\step_definitions\visibility-steps.js:54
    √ After # features\support\scenario-hooks.js:36

12) Scenario: Navigate to  How to use Don't Rush to Crush # features\DRTC\Home\home-landing-page.feature:21
    √ 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
    √ 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
    √ 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
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30038ms
            at C:\agent\_work\34\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17
            at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    - 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

13) Scenario: Navigate to  Before you rush to crush # features\DRTC\Home\home-landing-page.feature:22
    √ 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
    √ 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
    √ 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
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30158ms
            at C:\agent\_work\34\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17
            at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    - 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

14) Scenario: Navigate to  Acknowledgments # features\DRTC\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
    √ 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
    √ Given "a" element with "href" "/about/acknowledgments#drtc-acknowledgments-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" "Acknowledgments" # features\step_definitions\visibility-steps.js:25
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30224ms
            at C:\agent\_work\34\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17
            at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    - 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" "Acknowledgments" should be visible # features\step_definitions\visibility-steps.js:94
    √ After # features\support\scenario-hooks.js:36

15) Scenario: Navigate to  Enteral feeding tubes # features\DRTC\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
    √ 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
    √ 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
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30062ms
            at C:\agent\_work\34\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17
            at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    - 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

16) Scenario: Navigate to  Swallowing difficulties # features\DRTC\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
    √ 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
    √ 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
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30203ms
            at C:\agent\_work\34\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17
            at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    - 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

17) Scenario: Navigate to  Gastrointestinal dysfunction # features\DRTC\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
    √ 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
    √ 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
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30115ms
            at C:\agent\_work\34\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17
            at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    - 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

18) Scenario: Navigate to  Part-dosing # features\DRTC\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
    √ 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
    √ 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-dosing" # features\step_definitions\visibility-steps.js:25
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30200ms
            at C:\agent\_work\34\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17
            at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    - 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-dosing" should be visible # features\step_definitions\visibility-steps.js:94
    √ After # features\support\scenario-hooks.js:36

19) Scenario: Verify tab Enteral feeding tubes is visible and clickable # features\DRTC\Methods\methods.feature:16
    √ Before # features\support\scenario-hooks.js:6
    √ Before # features\support\scenario-hooks.js:23
    √ Given I visit "http://localhost:3000/about/methods" # features\step_definitions\navigation-steps.js:9
    × Given "a" element with "text" "Enteral feeding tubes" # features\step_definitions\visibility-steps.js:25
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30091ms
            at C:\agent\_work\34\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 wait for 1 seconds # features\step_definitions\bstack-steps.js:456
    - 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 element with "text" "Enteral feeding tubes" should be visible # features\step_definitions\visibility-steps.js:54
    √ After # features\support\scenario-hooks.js:36

20) Scenario: Verify tab Swallowing difficulties is visible and clickable # features\DRTC\Methods\methods.feature:17
    √ Before # features\support\scenario-hooks.js:6
    √ Before # features\support\scenario-hooks.js:23
    √ Given I visit "http://localhost:3000/about/methods" # features\step_definitions\navigation-steps.js:9
    × Given "a" element with "text" "Swallowing difficulties" # features\step_definitions\visibility-steps.js:25
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30119ms
            at C:\agent\_work\34\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 wait for 1 seconds # features\step_definitions\bstack-steps.js:456
    - 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 element with "text" "Swallowing difficulties" should be visible # features\step_definitions\visibility-steps.js:54
    √ After # features\support\scenario-hooks.js:36

21) Scenario: Switch to Enteral feeding tubes tab and verify content # features\DRTC\Methods\methods.feature:29
    √ Before # features\support\scenario-hooks.js:6
    √ Before # features\support\scenario-hooks.js:23
    √ Given I visit "http://localhost:3000/about/methods" # features\step_definitions\navigation-steps.js:9
    × Given "a" element with "text" "Enteral feeding tubes" # features\step_definitions\visibility-steps.js:25
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30089ms
            at C:\agent\_work\34\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 2 seconds # features\step_definitions\bstack-steps.js:456
    - Then element with "text" "How to prepare medicines for people with enteral feeding tubes" should be visible # features\step_definitions\visibility-steps.js:54
    √ After # features\support\scenario-hooks.js:36

22) Scenario: Switch to Swallowing difficulties tab and verify content # features\DRTC\Methods\methods.feature:30
    √ Before # features\support\scenario-hooks.js:6
    √ Before # features\support\scenario-hooks.js:23
    √ Given I visit "http://localhost:3000/about/methods" # features\step_definitions\navigation-steps.js:9
    × Given "a" element with "text" "Swallowing difficulties" # features\step_definitions\visibility-steps.js:25
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30042ms
            at C:\agent\_work\34\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 2 seconds # features\step_definitions\bstack-steps.js:456
    - Then element with "text" "How to prepare medicines for people with swallowing difficulties" should be visible # features\step_definitions\visibility-steps.js:54
    √ After # features\support\scenario-hooks.js:36

23) Scenario: Verify method section Method A. Disperse the tablet under Enteral feeding tubes tab # features\DRTC\Methods\methods.feature:45
    √ Before # features\support\scenario-hooks.js:6
    √ Before # features\support\scenario-hooks.js:23
    √ Given I visit "http://localhost:3000/about/methods" # features\step_definitions\navigation-steps.js:9
    × Given "a" element with "text" "Enteral feeding tubes" # features\step_definitions\visibility-steps.js:25
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30065ms
            at C:\agent\_work\34\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 2 seconds # features\step_definitions\bstack-steps.js:456
    - Given "div" element with "text" "Method A. Disperse the tablet" # features\step_definitions\visibility-steps.js:25
    - Then I scroll to element # features\step_definitions\scroll-steps.js:9
    - And I wait for 1 seconds # features\step_definitions\bstack-steps.js:456
    - Then element with "text" "Method A. Disperse the tablet" should be visible # features\step_definitions\visibility-steps.js:54
    √ After # features\support\scenario-hooks.js:36

24) Scenario: Verify method section Method B. Crush the tablet under Enteral feeding tubes tab # features\DRTC\Methods\methods.feature:46
    √ Before # features\support\scenario-hooks.js:6
    √ Before # features\support\scenario-hooks.js:23
    √ Given I visit "http://localhost:3000/about/methods" # features\step_definitions\navigation-steps.js:9
    × Given "a" element with "text" "Enteral feeding tubes" # features\step_definitions\visibility-steps.js:25
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30254ms
            at C:\agent\_work\34\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 2 seconds # features\step_definitions\bstack-steps.js:456
    - Given "div" element with "text" "Method B. Crush the tablet" # features\step_definitions\visibility-steps.js:25
    - Then I scroll to element # features\step_definitions\scroll-steps.js:9
    - And I wait for 1 seconds # features\step_definitions\bstack-steps.js:456
    - Then element with "text" "Method B. Crush the tablet" should be visible # features\step_definitions\visibility-steps.js:54
    √ After # features\support\scenario-hooks.js:36

25) Scenario: Verify method section Method C. Disperse the contents of a capsule or sachet under Enteral feeding tubes tab # features\DRTC\Methods\methods.feature:47
    √ Before # features\support\scenario-hooks.js:6
    √ Before # features\support\scenario-hooks.js:23
    √ Given I visit "http://localhost:3000/about/methods" # features\step_definitions\navigation-steps.js:9
    × Given "a" element with "text" "Enteral feeding tubes" # features\step_definitions\visibility-steps.js:25
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30213ms
            at C:\agent\_work\34\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 2 seconds # features\step_definitions\bstack-steps.js:456
    - Given "div" element with "text" "Method C. Disperse the contents of a capsule or sachet" # features\step_definitions\visibility-steps.js:25
    - Then I scroll to element # features\step_definitions\scroll-steps.js:9
    - And I wait for 1 seconds # features\step_definitions\bstack-steps.js:456
    - Then element with "text" "Method C. Disperse the contents of a capsule or sachet" should be visible # features\step_definitions\visibility-steps.js:54
    √ After # features\support\scenario-hooks.js:36

26) Scenario: Expand method sections under "Enteral feeding tubes" - Method A. Disperse the tablet # features\DRTC\Methods\methods.feature:62
    √ Before # features\support\scenario-hooks.js:6
    √ Before # features\support\scenario-hooks.js:23
    √ Given I visit "http://localhost:3000/about/methods" # features\step_definitions\navigation-steps.js:9
    × Given "a" element with "text" "Enteral feeding tubes" # features\step_definitions\visibility-steps.js:25
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30080ms
            at C:\agent\_work\34\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17
            at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    - 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 element with "text" "Method A. Disperse the tablet" # features\step_definitions\visibility-steps.js:13
    - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456
    - 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 "div" element with "aria-expanded" "true" should be visible # features\step_definitions\visibility-steps.js:94
    √ After # features\support\scenario-hooks.js:36

27) Scenario: Expand method sections under "Enteral feeding tubes" - Method B. Crush the tablet # features\DRTC\Methods\methods.feature:63
    √ Before # features\support\scenario-hooks.js:6
    √ Before # features\support\scenario-hooks.js:23
    √ Given I visit "http://localhost:3000/about/methods" # features\step_definitions\navigation-steps.js:9
    × Given "a" element with "text" "Enteral feeding tubes" # features\step_definitions\visibility-steps.js:25
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30020ms
            at C:\agent\_work\34\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17
            at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    - 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 element with "text" "Method B. Crush the tablet" # features\step_definitions\visibility-steps.js:13
    - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456
    - 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 "div" element with "aria-expanded" "true" should be visible # features\step_definitions\visibility-steps.js:94
    √ After # features\support\scenario-hooks.js:36

28) Scenario: Expand method sections under "Enteral feeding tubes" - Method C. Disperse the contents of a capsule or sachet # features\DRTC\Methods\methods.feature:64
    √ Before # features\support\scenario-hooks.js:6
    √ Before # features\support\scenario-hooks.js:23
    √ Given I visit "http://localhost:3000/about/methods" # features\step_definitions\navigation-steps.js:9
    × Given "a" element with "text" "Enteral feeding tubes" # features\step_definitions\visibility-steps.js:25
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30015ms
            at C:\agent\_work\34\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17
            at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    - 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 element with "text" "Method C. Disperse the contents of a capsule or sachet" # features\step_definitions\visibility-steps.js:13
    - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456
    - 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 "div" element with "aria-expanded" "true" should be visible # features\step_definitions\visibility-steps.js:94
    √ After # features\support\scenario-hooks.js:36

29) Scenario: Expand method sections under "Swallowing difficulties" - Method D. Disperse the tablet # features\DRTC\Methods\methods.feature:65
    √ Before # features\support\scenario-hooks.js:6
    √ Before # features\support\scenario-hooks.js:23
    √ Given I visit "http://localhost:3000/about/methods" # features\step_definitions\navigation-steps.js:9
    × Given "a" element with "text" "Swallowing difficulties" # features\step_definitions\visibility-steps.js:25
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30127ms
            at C:\agent\_work\34\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17
            at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    - 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 element with "text" "Method D. Disperse the tablet" # features\step_definitions\visibility-steps.js:13
    - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456
    - 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 "div" element with "aria-expanded" "true" should be visible # features\step_definitions\visibility-steps.js:94
    √ After # features\support\scenario-hooks.js:36

30) Scenario: Expand method sections under "Swallowing difficulties" - Method E. Crush the tablet # features\DRTC\Methods\methods.feature:66
    √ Before # features\support\scenario-hooks.js:6
    √ Before # features\support\scenario-hooks.js:23
    √ Given I visit "http://localhost:3000/about/methods" # features\step_definitions\navigation-steps.js:9
    × Given "a" element with "text" "Swallowing difficulties" # features\step_definitions\visibility-steps.js:25
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30037ms
            at C:\agent\_work\34\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17
            at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    - 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 element with "text" "Method E. Crush the tablet" # features\step_definitions\visibility-steps.js:13
    - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456
    - 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 "div" element with "aria-expanded" "true" should be visible # features\step_definitions\visibility-steps.js:94
    √ After # features\support\scenario-hooks.js:36

31) Scenario: Expand method sections under "Swallowing difficulties" - Method F. Disperse the contents of the capsule or sachet # features\DRTC\Methods\methods.feature:67
    √ Before # features\support\scenario-hooks.js:6
    √ Before # features\support\scenario-hooks.js:23
    √ Given I visit "http://localhost:3000/about/methods" # features\step_definitions\navigation-steps.js:9
    × Given "a" element with "text" "Swallowing difficulties" # features\step_definitions\visibility-steps.js:25
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30140ms
            at C:\agent\_work\34\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17
            at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    - 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 element with "text" "Method F. Disperse the contents of the capsule or sachet" # features\step_definitions\visibility-steps.js:13
    - And I wait for 2 seconds # features\step_definitions\bstack-steps.js:456
    - 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 "div" element with "aria-expanded" "true" should be visible # features\step_definitions\visibility-steps.js:94
    √ After # features\support\scenario-hooks.js:36

32) Scenario: Search for monograph and verify content sections # features\DRTC\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
    √ 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
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30217ms
            at C:\agent\_work\34\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 "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

33) Scenario: Search for monograph and verify content sections # features\DRTC\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
    √ 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
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30058ms
            at C:\agent\_work\34\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 "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

34) Scenario: Search for monograph and verify content sections # features\DRTC\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
    √ 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
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30017ms
            at C:\agent\_work\34\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 "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

35) Scenario: Search for monograph and verify content sections # features\DRTC\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
    √ 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
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30115ms
            at C:\agent\_work\34\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 "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

36) Scenario: Search for monograph and verify content sections # features\DRTC\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
    √ 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
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30205ms
            at C:\agent\_work\34\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 "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

37) Scenario: Search for monograph and verify content sections # features\DRTC\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
    √ 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
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30088ms
            at C:\agent\_work\34\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 "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

38) Scenario: Search for monograph and verify content sections # features\DRTC\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
    √ 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
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30141ms
            at C:\agent\_work\34\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 "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

39) Scenario: Search for monograph and verify content sections # features\DRTC\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
    √ 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" "Swallowing difficulties" # features\step_definitions\visibility-steps.js:25
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30026ms
            at C:\agent\_work\34\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 "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

40) Scenario: Search for monograph and verify content sections # features\DRTC\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
    √ 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 "Esomeprazole" # 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/esomeprazole" 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
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30041ms
            at C:\agent\_work\34\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 "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

41) Scenario: Search for monograph and verify content sections # features\DRTC\Monograph\monograph-content.feature:45
    √ Before # features\support\scenario-hooks.js:6
node.exe : ┌──────────────────────────────────────────────────────────────────────────────┐
At C:\agent\_work\34\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:                     │
│ module.exports = { default: '--publish-quiet' }                              │
    √ 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
    √ 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" "Swallowing difficulties" # features\step_definitions\visibility-steps.js:25
        TimeoutError: Waiting element with locator to be visible
        Wait timed out after 30160ms
            at C:\agent\_work\34\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 "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

179 scenarios (41 failed, 74 skipped, 64 passed)
1727 steps (41 failed, 970 skipped, 716 passed)
7m03.390s (executing steps: 41m33.075s)