Cucumber Feature Report

All Scenarios

50

Passed Scenarios

45

Failed Scenarios

5

Execution Time: 01:55 Device Type: Web

Expand All | Collapse All

Metadata

Browser: Chrome

Platform: Windows

Executed: Local

Feature:Landing Page 38s 904ms 10

Scenario Outline:
Verify "Start here" section -"Start here"

3s 575ms 2

Given I visit "http://localhost:3000/" 3s 115ms

Then "h3" element with "text" "Start here" should be visible 460ms

Scenario Outline:
Verify "Start here" section -"How to use this resource"

3s 808ms 2

Given I visit "http://localhost:3000/" 3s 291ms

Then "div" element with "text" "How to use this resource" should be visible 517ms

Scenario Outline:
Verify "Start here" section -"Understanding the monographs"

3s 796ms 2

Given I visit "http://localhost:3000/" 3s 144ms

Then "div" element with "text" "Understanding the monographs" should be visible 652ms

Scenario Outline:
Verify "Core concepts" section-"Core concepts you should know"

3s 856ms 2

Given I visit "http://localhost:3000/" 3s 237ms

Then "h3" element with "text" "Core concepts you should know" should be visible 619ms

Scenario Outline:
Verify "Core concepts" section-"Body weight metrics"

3s 813ms 2

Given I visit "http://localhost:3000/" 3s 179ms

Then "div" element with "text" "Body weight metrics" should be visible 634ms

Scenario Outline:
Verify "Core concepts" section-"Pharmacokinetic changes in obesity"

3s 809ms 2

Given I visit "http://localhost:3000/" 3s 274ms

Then "div" element with "text" "Pharmacokinetic changes in obesity" should be visible 535ms

Scenario Outline:
Verify "Core concepts" section-"Kidney function and other factors"

3s 613ms 2

Given I visit "http://localhost:3000/" 3s 289ms

Then "div" element with "text" "Kidney function and other factors" should be visible 324ms

Scenario Outline:
Verify "About this resource" section-"About this resource"

4s 188ms 2

Given I visit "http://localhost:3000/" 3s 839ms

Then "h3" element with "text" "About this resource" should be visible 349ms

Scenario Outline:
Verify "About this resource" section-"obesity"

3s 654ms 2

Given I visit "http://localhost:3000/" 3s 304ms

Then "p" element with "text" "obesity" should be visible 350ms

Scenario Outline:
Verify "About this resource" section-"guidance"

4s 792ms 2

Given I visit "http://localhost:3000/" 4s 476ms

Then "p" element with "text" "guidance" should be visible 316ms

Feature:Landing Page 28s 138ms 10

Scenario Outline:
Verify "Start here" section -"Start here"

3s 803ms 3

Given I visit "http://localhost:3000/" 3s 399ms

When I ensure the menu is open with "menu-toggle" 23ms

Then "h3" element with "text" "Start here" should be visible 381ms

Scenario Outline:
Verify "Start here" section -"How to use this resource"

3s 874ms 3

Given I visit "http://localhost:3000/" 2s 792ms

When I ensure the menu is open with "menu-toggle" 22ms

Then "div" element with "text" "How to use this resource" should be visible 1s 60ms

Scenario Outline:
Verify "Start here" section -"Understanding the monographs"

2s 378ms 3

Given I visit "http://localhost:3000/" 2s 72ms

When I ensure the menu is open with "menu-toggle" 22ms

Then "div" element with "text" "Understanding the monographs" should be visible 284ms

Scenario Outline:
Verify "Core concepts" section-"Core concepts you should know"

2s 803ms 3

Given I visit "http://localhost:3000/" 2s 430ms

When I ensure the menu is open with "menu-toggle" 29ms

Then "h3" element with "text" "Core concepts you should know" should be visible 344ms

Scenario Outline:
Verify "Core concepts" section-"Body weight metrics"

2s 346ms 3

Given I visit "http://localhost:3000/" 1s 957ms

When I ensure the menu is open with "menu-toggle" 18ms

Then "div" element with "text" "Body weight metrics" should be visible 371ms

Scenario Outline:
Verify "Core concepts" section-"Pharmacokinetic changes in obesity"

2s 285ms 3

Given I visit "http://localhost:3000/" 1s 797ms

When I ensure the menu is open with "menu-toggle" 12ms

Then "div" element with "text" "Pharmacokinetic changes in obesity" should be visible 476ms

Scenario Outline:
Verify "Core concepts" section-"Kidney function and other factors"

2s 442ms 3

Given I visit "http://localhost:3000/" 1s 334ms

When I ensure the menu is open with "menu-toggle" 623ms

Then "div" element with "text" "Kidney function and other factors" should be visible 485ms

Scenario Outline:
Verify "About this resource" section-"About this resource"

2s 605ms 3

Given I visit "http://localhost:3000/" 1s 611ms

When I ensure the menu is open with "menu-toggle" 648ms

Then "h3" element with "text" "About this resource" should be visible 346ms

Scenario Outline:
Verify "About this resource" section-"obesity"

2s 842ms 3

Given I visit "http://localhost:3000/" 2s 394ms

When I ensure the menu is open with "menu-toggle" 15ms

Then "p" element with "text" "obesity" should be visible 433ms

Scenario Outline:
Verify "About this resource" section-"guidance"

2s 760ms 3

Given I visit "http://localhost:3000/" 2s 375ms

When I ensure the menu is open with "menu-toggle" 14ms

Then "p" element with "text" "guidance" should be visible 371ms

Feature:Monograph Search Page 2m 6s 238ms 15

Scenario Outline:
Verify elements are visible on the page

3s 992ms 4

Given I visit "http://localhost:3000/" 2s 65ms

When I ensure the menu is open with "menu-toggle" 717ms

When I click the menu item "Monographs (A-Z)" 1s 176ms

Then element with "text" "Drug search" should be visible 34ms

Scenario Outline:
Clicking A-Z button "A" navigates correctly

8s 438ms 7

Given I visit "http://localhost:3000/" 2s 184ms

When I ensure the menu is open with "menu-toggle" 43ms

When I click the menu item "Monographs (A-Z)" 1s 194ms

Given element with "data-testid" "monograph-search-az-button-A" 29ms

And I wait for 4 seconds 4s 8ms

And I click on element 742ms

Given I visit path "/search?letter=A" 238ms

Scenario Outline:
Clicking A-Z button "B" navigates correctly

10s 122ms 7

Given I visit "http://localhost:3000/" 2s 799ms

When I ensure the menu is open with "menu-toggle" 46ms

When I click the menu item "Monographs (A-Z)" 1s 747ms

Given element with "data-testid" "monograph-search-az-button-B" 80ms

And I wait for 4 seconds 4s 7ms

And I click on element 591ms

Given I visit path "/search?letter=B" 852ms

Scenario Outline:
Clicking A-Z button "C" navigates correctly

11s 317ms 7

Given I visit "http://localhost:3000/" 5s 269ms

When I ensure the menu is open with "menu-toggle" 69ms

When I click the menu item "Monographs (A-Z)" 1s 158ms

Given element with "data-testid" "monograph-search-az-button-C" 70ms

And I wait for 4 seconds 4s 4ms

And I click on element 586ms

Given I visit path "/search?letter=C" 161ms

Scenario Outline:
Clicking A-Z button "D" navigates correctly

8s 809ms 7

Given I visit "http://localhost:3000/" 2s 706ms

When I ensure the menu is open with "menu-toggle" 13ms

When I click the menu item "Monographs (A-Z)" 1s 275ms

Given element with "data-testid" "monograph-search-az-button-D" 38ms

And I wait for 4 seconds 4s 7ms

And I click on element 586ms

Given I visit path "/search?letter=D" 184ms

Scenario Outline:
Clicking A-Z button "L" navigates correctly

8s 739ms 7

Given I visit "http://localhost:3000/" 2s 572ms

When I ensure the menu is open with "menu-toggle" 46ms

When I click the menu item "Monographs (A-Z)" 1s 246ms

Given element with "data-testid" "monograph-search-az-button-L" 73ms

And I wait for 4 seconds 4s 9ms

And I click on element 619ms

Given I visit path "/search?letter=L" 174ms

Scenario Outline:
Clicking A-Z button "M" navigates correctly

8s 465ms 7

Given I visit "http://localhost:3000/" 2s 499ms

When I ensure the menu is open with "menu-toggle" 37ms

When I click the menu item "Monographs (A-Z)" 1s 136ms

Given element with "data-testid" "monograph-search-az-button-M" 49ms

And I wait for 4 seconds 4s 10ms

And I click on element 584ms

Given I visit path "/search?letter=M" 150ms

Scenario Outline:
Clicking A-Z button "N" navigates correctly

7s 774ms 7

Given I visit "http://localhost:3000/" 1s 736ms

When I ensure the menu is open with "menu-toggle" 13ms

When I click the menu item "Monographs (A-Z)" 1s 147ms

Given element with "data-testid" "monograph-search-az-button-N" 36ms

And I wait for 4 seconds 4s 8ms

And I click on element 647ms

Given I visit path "/search?letter=N" 187ms

Scenario Outline:
Clicking A-Z button "R" navigates correctly

7s 607ms 7

Given I visit "http://localhost:3000/" 1s 454ms

When I ensure the menu is open with "menu-toggle" 14ms

When I click the menu item "Monographs (A-Z)" 1s 172ms

Given element with "data-testid" "monograph-search-az-button-R" 35ms

And I wait for 4 seconds 4s 12ms

And I click on element 733ms

Given I visit path "/search?letter=R" 187ms

Scenario Outline:
Clicking A-Z button "S" navigates correctly

9s 846ms 7

Given I visit "http://localhost:3000/" 3s 596ms

When I ensure the menu is open with "menu-toggle" 26ms

When I click the menu item "Monographs (A-Z)" 1s 204ms

Given element with "data-testid" "monograph-search-az-button-S" 124ms

And I wait for 4 seconds 4s 8ms

And I click on element 710ms

Given I visit path "/search?letter=S" 178ms

Scenario Outline:
Clicking A-Z button "T" navigates correctly

8s 662ms 7

Given I visit "http://localhost:3000/" 2s 701ms

When I ensure the menu is open with "menu-toggle" 31ms

When I click the menu item "Monographs (A-Z)" 1s 67ms

Given element with "data-testid" "monograph-search-az-button-T" 67ms

And I wait for 4 seconds 4s 12ms

And I click on element 567ms

Given I visit path "/search?letter=T" 217ms

Scenario Outline:
Clicking A-Z button "U" navigates correctly

8s 268ms 7

Given I visit "http://localhost:3000/" 2s 222ms

When I ensure the menu is open with "menu-toggle" 15ms

When I click the menu item "Monographs (A-Z)" 1s 206ms

Given element with "data-testid" "monograph-search-az-button-U" 31ms

And I wait for 4 seconds 4s 8ms

And I click on element 612ms

Given I visit path "/search?letter=U" 174ms

Scenario Outline:
Clicking A-Z button "V" navigates correctly

8s 127ms 7

Given I visit "http://localhost:3000/" 2s 195ms

When I ensure the menu is open with "menu-toggle" 15ms

When I click the menu item "Monographs (A-Z)" 1s 91ms

Given element with "data-testid" "monograph-search-az-button-V" 47ms

And I wait for 4 seconds 4s 2ms

And I click on element 606ms

Given I visit path "/search?letter=V" 171ms

Scenario Outline:
Clicking A-Z button "W" navigates correctly

8s 595ms 7

Given I visit "http://localhost:3000/" 2s 655ms

When I ensure the menu is open with "menu-toggle" 14ms

When I click the menu item "Monographs (A-Z)" 1s 112ms

Given element with "data-testid" "monograph-search-az-button-W" 64ms

And I wait for 4 seconds 4s 10ms

And I click on element 585ms

Given I visit path "/search?letter=W" 155ms

Scenario Outline:
Clicking A-Z button "Z" navigates correctly

7s 477ms 7

Given I visit "http://localhost:3000/" 1s 498ms

When I ensure the menu is open with "menu-toggle" 13ms

When I click the menu item "Monographs (A-Z)" 1s 165ms

Given element with "data-testid" "monograph-search-az-button-Z" 49ms

And I wait for 4 seconds 4s 15ms

And I click on element 566ms

Given I visit path "/search?letter=Z" 171ms

Feature:Monograph Search Page 20s 501ms 4

Scenario Outline:
Verify pharmacodynamics content

4s 761ms 1

Given I visit "http://localhost:3000" 4s 761ms Show Error +

                                            
 WebDriverError: unknown error: net::ERR_CONNECTION_REFUSED
  (Session info: chrome=139.0.7258.68)
    at Object.throwDecodedError (C:\agent\_work\26\s\node_modules\selenium-webdriver\lib\error.js:522:15)
    at parseHttpResponse (C:\agent\_work\26\s\node_modules\selenium-webdriver\lib\http.js:549:13)
    at Executor.execute (C:\agent\_work\26\s\node_modules\selenium-webdriver\lib\http.js:475:28)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Driver.execute (C:\agent\_work\26\s\node_modules\selenium-webdriver\lib\webdriver.js:735:17)
    at async World.getUrlWithCookie (C:\agent\_work\26\s\features\support\browser-utils.js:132:18)
    at async World.(anonymous) (C:\agent\_work\26\s\features\step_definitions\navigation-steps.js:17:5)

Scenario Outline:
Verify other PK/PD factors

8s 510ms 1

Given I visit "http://localhost:3000" 8s 510ms Show Error +

                                            
 WebDriverError: unknown error: net::ERR_CONNECTION_REFUSED
  (Session info: chrome=139.0.7258.68)
    at Object.throwDecodedError (C:\agent\_work\26\s\node_modules\selenium-webdriver\lib\error.js:522:15)
    at parseHttpResponse (C:\agent\_work\26\s\node_modules\selenium-webdriver\lib\http.js:549:13)
    at Executor.execute (C:\agent\_work\26\s\node_modules\selenium-webdriver\lib\http.js:475:28)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Driver.execute (C:\agent\_work\26\s\node_modules\selenium-webdriver\lib\webdriver.js:735:17)
    at async World.getUrlWithCookie (C:\agent\_work\26\s\features\support\browser-utils.js:132:18)
    at async World.(anonymous) (C:\agent\_work\26\s\features\step_definitions\navigation-steps.js:17:5)

Scenario Outline:
Verify standard dosing information

3s 640ms 1

Given I visit "http://localhost:3000" 3s 640ms Show Error +

                                            
 WebDriverError: unknown error: net::ERR_CONNECTION_REFUSED
  (Session info: chrome=139.0.7258.68)
    at Object.throwDecodedError (C:\agent\_work\26\s\node_modules\selenium-webdriver\lib\error.js:522:15)
    at parseHttpResponse (C:\agent\_work\26\s\node_modules\selenium-webdriver\lib\http.js:549:13)
    at Executor.execute (C:\agent\_work\26\s\node_modules\selenium-webdriver\lib\http.js:475:28)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Driver.execute (C:\agent\_work\26\s\node_modules\selenium-webdriver\lib\webdriver.js:735:17)
    at async World.getUrlWithCookie (C:\agent\_work\26\s\features\support\browser-utils.js:132:18)
    at async World.(anonymous) (C:\agent\_work\26\s\features\step_definitions\navigation-steps.js:17:5)

Scenario Outline:
Verify standard dosing information

3s 590ms 1

Given I visit "http://localhost:3000" 3s 590ms Show Error +

                                            
 WebDriverError: unknown error: net::ERR_CONNECTION_REFUSED
  (Session info: chrome=139.0.7258.68)
    at Object.throwDecodedError (C:\agent\_work\26\s\node_modules\selenium-webdriver\lib\error.js:522:15)
    at parseHttpResponse (C:\agent\_work\26\s\node_modules\selenium-webdriver\lib\http.js:549:13)
    at Executor.execute (C:\agent\_work\26\s\node_modules\selenium-webdriver\lib\http.js:475:28)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Driver.execute (C:\agent\_work\26\s\node_modules\selenium-webdriver\lib\webdriver.js:735:17)
    at async World.getUrlWithCookie (C:\agent\_work\26\s\features\support\browser-utils.js:132:18)
    at async World.(anonymous) (C:\agent\_work\26\s\features\step_definitions\navigation-steps.js:17:5)

Feature:Monograph Search Page No Results 23s 270ms 4

Scenario Outline:
Searching for "Vad" in the drug search input with no matches

5s 524ms 7

Given I visit "http://localhost:3000/" 540ms

When I ensure the menu is open with "menu-toggle" 1s 462ms

When I click the menu item "Monographs (A-Z)" 1s 148ms

Given "input" element with "data-testid" "monograph-search-input" 48ms

When I enter "Vad" 98ms

When I press enter on element 2s 183ms

Then element with "data-testid" "monograph-search-no-results" should be visible 45ms

Scenario Outline:
Searching for "XYZ" in the drug search input with no matches

6s 368ms 7

Given I visit "http://localhost:3000/" 2s 824ms

When I ensure the menu is open with "menu-toggle" 16ms

When I click the menu item "Monographs (A-Z)" 1s 147ms

Given "input" element with "data-testid" "monograph-search-input" 65ms

When I enter "XYZ" 119ms

When I press enter on element 2s 162ms

Then element with "data-testid" "monograph-search-no-results" should be visible 35ms

Scenario Outline:
Searching for "Abs" in the drug search input with no matches

5s 899ms 7

Given I visit "http://localhost:3000/" 2s 418ms

When I ensure the menu is open with "menu-toggle" 12ms

When I click the menu item "Monographs (A-Z)" 1s 101ms

Given "input" element with "data-testid" "monograph-search-input" 54ms

When I enter "Abs" 126ms

When I press enter on element 2s 157ms

Then element with "data-testid" "monograph-search-no-results" should be visible 31ms

Scenario Outline:
Searching for "Hgcyum" in the drug search input with no matches

5s 479ms 7

Given I visit "http://localhost:3000/" 1s 761ms

When I ensure the menu is open with "menu-toggle" 14ms

When I click the menu item "Monographs (A-Z)" 1s 94ms

Given "input" element with "data-testid" "monograph-search-input" 62ms

When I enter "Hgcyum" 254ms

When I press enter on element 2s 261ms

Then element with "data-testid" "monograph-search-no-results" should be visible 33ms

Feature:Sidebar menu navigation 6s 119ms 2

Scenario Outline:
Menu item "Monographs (A-Z)" navigates to the correct page

2s 859ms 5

Given I visit "http://localhost:3000/" 1s 675ms

When I ensure the menu is open with "menu-toggle" 11ms

And I set browser to offline mode 2ms

When I click the menu item "Monographs (A-Z)" 1s 109ms

Then "h3" element with "text" "Browse A-Z" should be visible 62ms

Scenario Outline:
Menu item "Calculator" navigates to the correct page

3s 260ms 5

Given I visit "http://localhost:3000/" 1s 980ms

When I ensure the menu is open with "menu-toggle" 12ms

And I set browser to offline mode 2ms

When I click the menu item "Calculator" 1s 172ms

Then "input" element with "data-testid" "height-input" should be visible 94ms

Feature:Sidebar menu navigation 46s 309ms 4 1

Scenario Outline:
Menu item "Home" navigates to the correct page

32s 575ms 4 1

Given I visit "http://localhost:3000/" 1s 222ms

When I ensure the menu is open with "menu-toggle" 26ms

Then the menu should display the following items: 409ms

Home
Calculator
Monographs (A-Z)
Favourites

When I click the menu item "Home" 856ms

Then "h3" element with "text" "Features testing:" should be visible 30s 62ms Show Error +

                                            
 TimeoutError: Waiting element with locator to be visible
Wait timed out after 30060ms
    at C:\agent\_work\26\s\node_modules\selenium-webdriver\lib\webdriver.js:901:17
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Scenario Outline:
Menu item "Calculator" navigates to the correct page

2s 852ms 5

Given I visit "http://localhost:3000/" 1s 481ms

When I ensure the menu is open with "menu-toggle" 12ms

Then the menu should display the following items: 421ms

Home
Calculator
Monographs (A-Z)
Favourites

When I click the menu item "Calculator" 899ms

Then "input" element with "data-testid" "height-input" should be visible 39ms

Scenario Outline:
Menu item "Monographs (A-Z)" navigates to the correct page

2s 599ms 5

Given I visit "http://localhost:3000/" 695ms

When I ensure the menu is open with "menu-toggle" 684ms

Then the menu should display the following items: 340ms

Home
Calculator
Monographs (A-Z)
Favourites

When I click the menu item "Monographs (A-Z)" 857ms

Then "h3" element with "text" "Browse A-Z" should be visible 23ms

Scenario Outline:
Menu item "Favourites" navigates to the correct page

4s 494ms 5

Given I visit "http://localhost:3000/" 3s 98ms

When I ensure the menu is open with "menu-toggle" 13ms

Then the menu should display the following items: 443ms

Home
Calculator
Monographs (A-Z)
Favourites

When I click the menu item "Favourites" 912ms

Then "p" element with "text" "💿 Hey developer 👋" should be visible 28ms

Scenario Outline:
Menu item "Glossary" navigates to the correct page

3s 789ms 5

Given I visit "http://localhost:3000/" 2s 457ms

When I ensure the menu is open with "menu-toggle" 9ms

Then the menu should display the following items: 320ms

Home
Calculator
Monographs (A-Z)
Favourites

When I click the menu item "Glossary" 977ms

Then "p" element with "text" "💿 Hey developer 👋" should be visible 26ms