Cucumber-JVM Reports - Tag: @rollbackAddedAuthorities

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.156	13 wrz 2021, 06:47

	Steps	Scenarios	Features
@rollbackAddedAuthorities	367	3	0	0	0	370	37	3	40	11m 6s 978ms	Failed

View Feature Company

Scenario Outline Check if it possible to create and edit company [A-6812]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-skz" 254ms

When Set basic authorities "ROLE_CREATE_COMPANY" to user "super-admin-skz" 369ms

And Clear all cache 2s 683ms

And Login as "super-admin-skz" 12s 541ms

And Create company "Firma automaty" 7s 456ms

And Edit company "Firma automaty" 3s 761ms

Then Company is successfully edited 585ms

Hooks

After Hooks.deleteCompanyAfterTest() 117ms

After Hooks.rollbackAddedAuthorities() 165ms

View Feature Company

@deleteCompanyAfterTest @rollbackAddedAuthorities

Scenario Outline Check if it possible to add company patron in company details

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-pgf" 230ms

And Set basic authorities "ROLE_CREATE_COMPANY" to user "pgf-admin" 191ms

When Create company "Twój Opiekun PGF" "supplier" by JSON file as "super-admin-pgf" 846ms

And Login as "pgf-admin" 5s 232ms

And Go to "COMPANIES_TAB" 1s 955ms

And Go to company "Twój Opiekun PGF" details 482ms

And Select company patron "PGF SUPPLY EMPLOYEE" 7s 722ms

Then Verify if "PGF SUPPLY EMPLOYEE" data is successfully added 142ms

Hooks

After Hooks.deleteCompanyAfterTest() 122ms

After Hooks.rollbackAddedAuthorities() 159ms

View Feature Company

@removeAllAddedPartnership @rollbackAddedAuthorities

Scenario Outline Check if admin can manage partnership of supplier with carrier in contractor's details - adding partnership [A-7386]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 222ms

And Set basic authorities "ROLE_SHOW_PARTNERSHIP_TABLE" to user "adama-admin" 177ms

And Login as "adama-admin" 6s 139ms

And Go to "COMPANIES_TAB" 1s 393ms

And Go to company "Dostawca Adama Automat 1" details 560ms

Then Verify that user has correct partnership management permissions "adama-admin" 771ms

And Set existing partnerships 15s 092ms

When Go to form for adding a new single partnership 227ms

Then Verify that partnership form is visible 106ms

And Verify that each company suggested in partnership form is "Przewoźnik" 1s 276ms

When Fill partnership form 1s 689ms

Then Check if "single" contractor is "visible" on partnership list "connectedCompany" 1s 590ms

When Go to "CARRIER_TAB" 1s 044ms

And Go to details of company in partnership 847ms

Then Check if "single" contractor is "invisible" on partnership list "Dostawca Adama Automat 1" 30s 282ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 917ms

View Feature Company

@removeAllAddedPartnership @rollbackAddedAuthorities

Scenario Outline Check if admin can manage partnership of supplier with carrier in contractor's details - adding partnership [A-7386]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-neuca" 232ms

And Set basic authorities "ROLE_SHOW_PARTNERSHIP_TABLE" to user "neuca-admin" 138ms

And Login as "neuca-admin" 9s 127ms

And Go to "COMPANIES_TAB" 1s 680ms

And Go to company "Przewoźnik Neuca Automat 3" details 584ms

Then Verify that user has correct partnership management permissions "neuca-admin" 460ms

And Set existing partnerships 15s 080ms

When Go to form for adding a new single partnership 266ms

Then Verify that partnership form is visible 125ms

And Verify that each company suggested in partnership form is "Dostawca" 1s 352ms

When Fill partnership form 1s 683ms

Then Check if "single" contractor is "visible" on partnership list "connectedCompany" 1s 447ms

When Go to "COMPANIES_TAB" 1s 058ms

And Go to details of company in partnership 540ms

Then Check if "single" contractor is "visible" on partnership list "Przewoźnik Neuca Automat 3" 296ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 914ms

View Feature Company

@rollbackAddedAuthorities

Scenario Outline Check if only admins have the authority to manage partnerships in the contractor's details - admins [A-7536]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-neuca" 234ms

And Set basic authorities "ROLE_SHOW_PARTNERSHIP_TABLE" to user "neuca-admin" 138ms

And Login as "neuca-admin" 2s 363ms

And Go to "COMPANIES_TAB" 1s 021ms

And Go to company "Przewoźnik Neuca Automat 1" details 581ms

Then Verify that user has correct partnership management permissions "neuca-admin" 458ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Company

@rollbackAddedAuthorities

Scenario Outline Check if only admins have the authority to manage partnerships in the contractor's details - admins [A-7536]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-neuca" 241ms

And Set basic authorities "ROLE_SHOW_PARTNERSHIP_TABLE" to user "super-admin-neuca" 155ms

And Login as "super-admin-neuca" 8s 326ms

And Go to "COMPANIES_TAB" 1s 056ms

And Go to company "Przewoźnik Neuca Automat 1" details 583ms

Then Verify that user has correct partnership management permissions "super-admin-neuca" 469ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Company

@removeAllAddedPartnership @rollbackAddedAuthorities

Scenario Outline Removal of partnership by admin [A-7482]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 252ms

And Set basic authorities "ROLE_SHOW_PARTNERSHIP_TABLE" to user "adama-admin" 149ms

And Login as "adama-admin" 2s 209ms

When Go to "COMPANIES_TAB" 916ms

And Go to company "Dostawca Adama Automat 2" details 535ms

Then Verify that user has correct partnership management permissions "adama-admin" 772ms

And Set existing partnerships 15s 064ms

When Add all partnership 1s 048ms

Then Check if "all" contractor is "visible" on partnership list "connectedCompany" 1s 077ms

And Set number of partnerships 029ms

And Check if only companies from principal are visible "Adama" 102ms

When Remove partnership 758ms

Then Check that partnership has been deleted 032ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 726ms

View Feature Company

@removeAllAddedPartnership @rollbackAddedAuthorities

Scenario Outline Removal of partnership by admin [A-7482]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-neuca" 238ms

And Set basic authorities "ROLE_SHOW_PARTNERSHIP_TABLE" to user "neuca-admin" 141ms

And Login as "neuca-admin" 2s 166ms

When Go to "COMPANIES_TAB" 1s 012ms

And Go to company "Przewoźnik Neuca Automat 2" details 585ms

Then Verify that user has correct partnership management permissions "neuca-admin" 644ms

And Set existing partnerships 119ms

When Add all partnership 945ms

Then Check if "all" contractor is "visible" on partnership list "connectedCompany" 1s 212ms

And Set number of partnerships 033ms

And Check if only companies from principal are visible "Neuca" 140ms

When Remove partnership 762ms

Then Check that partnership has been deleted 031ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 3s 007ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackAddedAuthorities

Scenario Outline Check if mail was sent to after transport delay

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 9s 192ms

And Prepare user "pha2-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 168ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 250ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 153ms

And Go to "WAREHOUSE_TAB" 1s 382ms

And Select warehouse "Serownia" 1s 567ms

And Set week view 1s 267ms

And Show yesterday 1s 164ms

And Move window into the past 420ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "spóźnił się na" 52s 028ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 368ms

After Hooks.deleteTransportAfterTest() 767ms

After Hooks.rollbackAddedAuthorities() 185ms

View Feature Schedule

@rollbackAddedAuthorities

Scenario Outline Check if it is possible to change pallet limit in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 2s 282ms

And Set basic authorities "ROLE_CAN_CREATE_MAX_PALLET" to user "pgf-admin" 190ms

And Go to "WAREHOUSE_TAB" 1s 158ms

When Check if pallet limit counter is visible 080ms

And Set limit to "888" 915ms

Then Verify if pallet limit in schedule changed to "888" 153ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities

Scenario Outline Check if icons change correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "sempertrans-admin" and set token of apiUsername "super-admin-sempertrans" 2s 470ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "sempertrans-admin" 158ms

When Go to "TRANSPORT_TABLE" 420ms

And Click button "UNLOAD_TIME_WINDOW" "0" times 3s 047ms

Then Verify that "UNLOAD_TIME_WINDOW" icon is "fa-sort" 070ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities

Scenario Outline Check if icons change correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "sempertrans-admin" and set token of apiUsername "super-admin-sempertrans" 2s 526ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "sempertrans-admin" 151ms

When Go to "TRANSPORT_TABLE" 425ms

And Click button "UNLOAD_TIME_WINDOW" "1" times 3s 152ms

Then Verify that "UNLOAD_TIME_WINDOW" icon is "fa-sort-up" 076ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities

Scenario Outline Check if icons change correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "sempertrans-admin" and set token of apiUsername "super-admin-sempertrans" 2s 436ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "sempertrans-admin" 156ms

When Go to "TRANSPORT_TABLE" 347ms

And Click button "UNLOAD_TIME_WINDOW" "2" times 3s 251ms

Then Verify that "UNLOAD_TIME_WINDOW" icon is "fa-sort-down" 071ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities

Scenario Outline Check if icons change correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "sempertrans-admin" and set token of apiUsername "super-admin-sempertrans" 2s 398ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "sempertrans-admin" 140ms

When Go to "TRANSPORT_TABLE" 404ms

And Click button "UNLOAD_TIME_WINDOW" "3" times 3s 321ms

Then Verify that "UNLOAD_TIME_WINDOW" icon is "fa-sort" 068ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports time window dates sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-sempertrans" 225ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "sempertrans-admin" 139ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-sempertrans" in "0" days 1s 964ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-sempertrans" 1s 955ms

And Login as "sempertrans-admin" 2s 138ms

When Go to "TRANSPORT_TABLE" 491ms

And Click button "UNLOAD_TIME_WINDOW" "1" times 3s 158ms

Then Verify that values in "UNLOAD_TIME_WINDOW" are sorted "asc" in "sempertrans" "DELIVERY" 115ms

Hooks

After Hooks.deleteTransportsAfterTest() 1s 020ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports time window dates sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-sempertrans" 229ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "sempertrans-admin" 139ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-sempertrans" in "0" days 1s 954ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-sempertrans" 1s 942ms

And Login as "sempertrans-admin" 2s 187ms

When Go to "TRANSPORT_TABLE" 498ms

And Click button "UNLOAD_TIME_WINDOW" "2" times 3s 268ms

Then Verify that values in "UNLOAD_TIME_WINDOW" are sorted "desc" in "sempertrans" "DELIVERY" 134ms

Hooks

After Hooks.deleteTransportsAfterTest() 1s 115ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports time window dates sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-sempertrans" 217ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "sempertrans-admin" 148ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-sempertrans" in "0" days 1s 941ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-sempertrans" 1s 900ms

And Login as "sempertrans-admin" 2s 198ms

When Go to "TRANSPORT_TABLE" 522ms

And Click button "UNLOAD_TIME_WINDOW" "4" times 3s 500ms

Then Verify that values in "UNLOAD_TIME_WINDOW" are sorted "asc" in "sempertrans" "DELIVERY" 146ms

Hooks

After Hooks.deleteTransportsAfterTest() 1s 085ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports time window dates sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-sempertrans" 219ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "sempertrans-admin" 124ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-sempertrans" in "0" days 1s 925ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-sempertrans" 1s 980ms

And Login as "sempertrans-admin" 2s 099ms

When Go to "TRANSPORT_TABLE" 498ms

And Click button "UNLOAD_TIME_WINDOW" "5" times 3s 554ms

Then Verify that values in "UNLOAD_TIME_WINDOW" are sorted "desc" in "sempertrans" "DELIVERY" 110ms

Hooks

After Hooks.deleteTransportsAfterTest() 1s 031ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports statuses sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-neuca" 251ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "neuca-admin" 154ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "0" days 3s 149ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 3s 062ms

When Confirm status "ARRIVE" by Public API "v1" 774ms

And Login as "neuca-admin" 2s 167ms

When Go to "TRANSPORT_TABLE" 505ms

And Click button "STATUS" "1" times 3s 172ms

Then Verify that values in "STATUS" are sorted "asc" in "neuca" "DELIVERY" 172ms

Hooks

After Hooks.deleteTransportsAfterTest() 1s 607ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports statuses sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-neuca" 229ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "neuca-admin" 149ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "0" days 3s 157ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 3s 060ms

When Confirm status "ARRIVE" by Public API "v1" 541ms

And Login as "neuca-admin" 2s 284ms

When Go to "TRANSPORT_TABLE" 517ms

And Click button "STATUS" "2" times 3s 291ms

Then Verify that values in "STATUS" are sorted "desc" in "neuca" "DELIVERY" 171ms

Hooks

After Hooks.deleteTransportsAfterTest() 1s 612ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports statuses sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-neuca" 222ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "neuca-admin" 135ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "0" days 3s 085ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 3s 103ms

When Confirm status "ARRIVE" by Public API "v1" 563ms

And Login as "neuca-admin" 2s 085ms

When Go to "TRANSPORT_TABLE" 471ms

And Click button "STATUS" "3" times 3s 381ms

Then Verify that values in "STATUS" are sorted "asc" in "neuca" "DELIVERY" 135ms

Hooks

After Hooks.deleteTransportsAfterTest() 1s 600ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports statuses sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-neuca" 240ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "neuca-admin" 136ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "0" days 3s 081ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 3s 104ms

When Confirm status "ARRIVE" by Public API "v1" 561ms

And Login as "neuca-admin" 2s 160ms

When Go to "TRANSPORT_TABLE" 492ms

And Click button "STATUS" "2" times 3s 283ms

Then Verify that values in "STATUS" are sorted "desc" in "neuca" "DELIVERY" 156ms

Hooks

After Hooks.deleteTransportsAfterTest() 1s 622ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports are correctly sorted after switching tabs

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-neuca" 223ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "neuca-admin" 150ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "0" days 3s 061ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 3s 041ms

When Confirm status "ARRIVE" by Public API "v1" 548ms

And Login as "neuca-admin" 2s 099ms

When Go to "TRANSPORT_TABLE" 460ms

And Click button "STATUS" "1" times 3s 179ms

And Verify that values in "STATUS" are sorted "asc" in "neuca" "DELIVERY" 156ms

Then Go to "WAREHOUSE_TAB" 976ms

And Go to "TRANSPORT_TABLE" 439ms

And Verify that values in "STATUS" are sorted "asc" in "neuca" "DELIVERY" 295ms

Hooks

After Hooks.deleteTransportsAfterTest() 1s 567ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports are correctly sorted after switching tabs

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-neuca" 220ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "neuca-admin" 136ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "0" days 3s 100ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 3s 085ms

When Confirm status "ARRIVE" by Public API "v1" 537ms

And Login as "neuca-admin" 2s 079ms

When Go to "TRANSPORT_TABLE" 496ms

And Click button "STATUS" "2" times 3s 277ms

And Verify that values in "STATUS" are sorted "desc" in "neuca" "DELIVERY" 137ms

Then Go to "WAREHOUSE_TAB" 975ms

And Go to "TRANSPORT_TABLE" 479ms

And Verify that values in "STATUS" are sorted "desc" in "neuca" "DELIVERY" 304ms

Hooks

After Hooks.deleteTransportsAfterTest() 1s 584ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports are correctly sorted after logging in again

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-neuca" 222ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "neuca-admin" 135ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "0" days 3s 043ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 3s 074ms

When Confirm status "ARRIVE" by Public API "v1" 533ms

And Login as "neuca-admin" 2s 065ms

When Go to "TRANSPORT_TABLE" 480ms

And Click button "STATUS" "1" times 3s 170ms

And Verify that values in "STATUS" are sorted "asc" in "neuca" "DELIVERY" 142ms

Then If user is login then logout 255ms

And Login as "neuca-admin" 2s 302ms

And Go to "TRANSPORT_TABLE" 489ms

And Verify that values in "STATUS" are sorted "asc" in "neuca" "DELIVERY" 307ms

Hooks

After Hooks.deleteTransportsAfterTest() 1s 577ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports are correctly sorted after logging in again

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-neuca" 221ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "neuca-admin" 144ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "0" days 3s 047ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 3s 086ms

When Confirm status "ARRIVE" by Public API "v1" 536ms

And Login as "neuca-admin" 2s 140ms

When Go to "TRANSPORT_TABLE" 450ms

And Click button "STATUS" "2" times 3s 296ms

And Verify that values in "STATUS" are sorted "desc" in "neuca" "DELIVERY" 140ms

Then If user is login then logout 256ms

And Login as "neuca-admin" 2s 188ms

And Go to "TRANSPORT_TABLE" 484ms

And Verify that values in "STATUS" are sorted "desc" in "neuca" "DELIVERY" 316ms

Hooks

After Hooks.deleteTransportsAfterTest() 1s 566ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if time window turns red when moved into the past

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 013ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 240ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 262ms

When Go to "WAREHOUSE_TAB" 1s 325ms

And Select warehouse "Serownia" 1s 566ms

And Set week view 1s 252ms

And Show yesterday 1s 157ms

And Move window into the past 442ms

Then Check if window is "red" 4s 078ms

Error message

org.openqa.selenium.StaleElementReferenceException: stale element reference: element is not attached to the page document
  (Session info: headless chrome=93.0.4577.63)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/stale_element_reference.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=93.0.4577.63 (ff5c0da2ec0adeaed5550e6c7e98417dac77d98a-refs/branch-heads/4577@{#1135}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.iewX6Y}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=93.0.4577.63, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 79aba532e9cdc3a3f8d36c56f2016381
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:279)
	at org.openqa.selenium.remote.RemoteWebElement.getAttribute(RemoteWebElement.java:128)
	at Utils.TestUtil.elementHasColor(TestUtil.java:30)
	at CucumberTests.Schedule.ScheduleTest.checkIfWindowIs(ScheduleTest.java:58)
	at ✽.Check if window is "red"(file:Features/Atom/TimeWindow/TransportWindow.feature:14)

Hooks

After Hooks.deleteTransportAfterTest() 843ms

After Hooks.rollbackAddedAuthorities() 128ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if time window turns red when moved into the past

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 442ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 878ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "lantmannen-admin" 197ms

When Go to "WAREHOUSE_TAB" 1s 372ms

And Select warehouse "Magazyn - Nowa Sól" 2s 257ms

And Set week view 1s 298ms

And Show yesterday 1s 182ms

And Move window into the past 617ms

Then Check if window is "red" 4s 085ms

Error message

org.openqa.selenium.StaleElementReferenceException: stale element reference: element is not attached to the page document
  (Session info: headless chrome=93.0.4577.63)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/stale_element_reference.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=93.0.4577.63 (ff5c0da2ec0adeaed5550e6c7e98417dac77d98a-refs/branch-heads/4577@{#1135}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.iewX6Y}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=93.0.4577.63, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 79aba532e9cdc3a3f8d36c56f2016381
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:279)
	at org.openqa.selenium.remote.RemoteWebElement.getAttribute(RemoteWebElement.java:128)
	at Utils.TestUtil.elementHasColor(TestUtil.java:30)
	at CucumberTests.Schedule.ScheduleTest.checkIfWindowIs(ScheduleTest.java:58)
	at ✽.Check if window is "red"(file:Features/Atom/TimeWindow/TransportWindow.feature:14)

Hooks

After Hooks.deleteTransportAfterTest() 825ms

After Hooks.rollbackAddedAuthorities() 140ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if time window turns red when moved into the past after add advice by advice button in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 700ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 014ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "piast-admin" 189ms

And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 000ms

When Show all transport types 1s 143ms

And Click button advice in transport table "DELIVERY" 275ms

And Set advice window in schedule 3s 327ms

And Fill advice form 12s 964ms

And Click advice save button and wait for advice form to disappear 33s 515ms

And Select warehouse "Magazyn Hala A" 1s 674ms

And Set week view 2s 523ms

And Show yesterday 1s 230ms

And Move window into the past 968ms

Then Check if window is "red" 4s 099ms

Error message

org.openqa.selenium.StaleElementReferenceException: stale element reference: element is not attached to the page document
  (Session info: headless chrome=93.0.4577.63)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/stale_element_reference.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=93.0.4577.63 (ff5c0da2ec0adeaed5550e6c7e98417dac77d98a-refs/branch-heads/4577@{#1135}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.iewX6Y}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=93.0.4577.63, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 79aba532e9cdc3a3f8d36c56f2016381
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:279)
	at org.openqa.selenium.remote.RemoteWebElement.getAttribute(RemoteWebElement.java:128)
	at Utils.TestUtil.elementHasColor(TestUtil.java:30)
	at CucumberTests.Schedule.ScheduleTest.checkIfWindowIs(ScheduleTest.java:58)
	at ✽.Check if window is "red"(file:Features/Atom/TimeWindow/TransportWindow.feature:35)

Hooks

After Hooks.deleteTransportAfterTest() 880ms

After Hooks.rollbackAddedAuthorities() 148ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if window counter value in schedule changes

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 3s 195ms

And Set basic authorities "ROLE_ACCESS_TO_NUMBER_OF_WINDOWS" to user "keeeper-admin" 181ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 919ms

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD" as "super-admin-keeeper" 3s 292ms

And Go to "WAREHOUSE_TAB" 774ms

And Select warehouse "Magazyn Wyrobów Gotowych" 2s 059ms

And Go to next day in schedule 1s 250ms

And Check if time window counter value equals "1" 219ms

And Select view "DAYS_2" 2s 164ms

And Move advice window "2" 1s 484ms

And Select view "DAY" 2s 133ms

Then Check if time window counter value equals "0" 188ms

And Delete created transport by API 776ms

And Check if time window counter value equals "0" 151ms

And Click in free spot in schedule page to create gray window 553ms

And Check if time window counter value equals "0" 152ms

And Click in free spot in schedule page to create dedicated window 2s 131ms

And Check if time window counter value equals "0" 155ms

Hooks

After Hooks.deleteTransportAfterTest() 651ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7965

Scenario Outline Permission - Edit user main data [A-7965]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 226ms

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_USERS_MAIN_DATA" to user "oaa1-receiver-2" 407ms

When Login as "oaa1-receiver-2" 4s 131ms

And Go to user "oaa1-receiver" details edition by prepared link 155ms

And Change user details "email" to "newEmailAddress@newEmail.com" 985ms

And Change user details "phone" to "123456789" 517ms

Then Save user details 941ms

And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 148ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 647ms

After Hooks.rollbackAddedAuthorities() 234ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

Scenario Outline Permission - Edit user notifications [A-7887]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-skz" 229ms

And Set basic authorities "ROLE_USERS_TAB;EDIT_USERS_NOTIFICATION" to user "pskza1-carrier-2" 201ms

When Login as "pskza1-carrier-2" 6s 923ms

And Go to user "pskza1-carrier" details edition by prepared link 095ms

And Expand "other" notification section 2s 322ms

And Select all notifications in "other" section 272ms

Then Save user details 1s 530ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 057ms

After Hooks.rollbackAddedAuthorities() 167ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

Scenario Outline Permission - Edit user main data from other company [A-7887]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 227ms

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;ROLE_EDIT_USERS_MAIN_DATA" to user "adama-buyer" 443ms

And Set user details json of user "oaa1-receiver" 015ms

When Login as "adama-buyer" 4s 974ms

And Go to "USERS_TAB" 1s 435ms

And Find user "oaa1-receiver" 3s 578ms

And Change user details "email" to "newEmailAddress@newEmail.com" 778ms

And Change user details "phone" to "123456789" 455ms

Then Save user details 1s 062ms

And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 153ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 661ms

After Hooks.rollbackAddedAuthorities() 220ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

Scenario Outline Permission - Edit user notifications from other company [A-7887]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-skz" 225ms

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;EDIT_USERS_NOTIFICATION" to user "swisskrono-tradesman" 354ms

And Set user details json of user "pskza1-carrier" 010ms

When Login as "swisskrono-tradesman" 8s 979ms

And Go to "USERS_TAB" 1s 555ms

And Find user "pskza1-carrier" 3s 589ms

And Expand "GLUE_FACTORY" notification section 560ms

And Select all notifications in "GLUE_FACTORY" section 1s 397ms

Then Save user details 1s 881ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 052ms

After Hooks.rollbackAddedAuthorities() 232ms

View Feature UserAuthority

@rollbackAddedAuthorities @TmsLink=A-7052

Scenario Outline Check if it is possible to add new basic authority to user role group [A-7052]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skz" and set token of apiUsername "super-admin-skz" 2s 945ms

And Go to "SETTINGS_TAB" 913ms

When Go to "PRODUCER" authorities settings 1s 200ms

And Click add authority button 205ms

And Select "Dostęp do zakładki Ogłoszenia" in basic authority select 1s 142ms

And Click save authority button 234ms

And Expand "ANNOUNCEMENT" panel 1s 027ms

Then Check if authority "Dostęp do zakładki Ogłoszenia" is "visible" in "ANNOUNCEMENT" authority panel 087ms

Hooks

After Hooks.rollbackAddedAuthorities() 139ms

View Feature UserAuthority

@rollbackAddedAuthorities @TmsLink=A-7052

Scenario Outline Check if it is possible to add new basic authority to user role group [A-7052]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 3s 241ms

And Go to "SETTINGS_TAB" 853ms

When Go to "WAREHOUSE_MANAGER" authorities settings 1s 396ms

And Click add authority button 344ms

And Select "Dostęp do zakładki Ogłoszenia" in basic authority select 953ms

And Click save authority button 225ms

And Expand "ANNOUNCEMENT" panel 1s 387ms

Then Check if authority "Dostęp do zakładki Ogłoszenia" is "visible" in "ANNOUNCEMENT" authority panel 072ms

Hooks

After Hooks.rollbackAddedAuthorities() 149ms

View Feature UserAuthority

@rollbackAddedAuthorities @TmsLink=A-7052

Scenario Outline Check if it is possible to add new basic authority to user role group [A-7052]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 2s 673ms

And Go to "SETTINGS_TAB" 817ms

When Go to "SALES_EMPLOYEE" authorities settings 722ms

And Click add authority button 208ms

And Select "Dostęp do zakładki Ogłoszenia" in basic authority select 1s 038ms

And Click save authority button 502ms

And Expand "ANNOUNCEMENT" panel 839ms

Then Check if authority "Dostęp do zakładki Ogłoszenia" is "visible" in "ANNOUNCEMENT" authority panel 074ms

Hooks

After Hooks.rollbackAddedAuthorities() 148ms

View Feature UserAuthority

@rollbackAddedAuthorities @TmsLink=A-7052

Scenario Outline Check if it is possible to add new basic authority to user role group [A-7052]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-farmacol" and set token of apiUsername "super-admin-farmacol" 8s 040ms

And Go to "SETTINGS_TAB" 758ms

When Go to "ANALYST" authorities settings 615ms

And Click add authority button 203ms

And Select "Dostęp do zakładki Ogłoszenia" in basic authority select 1s 013ms

And Click save authority button 254ms

And Expand "ANNOUNCEMENT" panel 577ms

Then Check if authority "Dostęp do zakładki Ogłoszenia" is "visible" in "ANNOUNCEMENT" authority panel 078ms

Hooks

After Hooks.rollbackAddedAuthorities() 142ms

View Feature UserAuthority

@rollbackAddedAuthorities @TmsLink=A-7052

Scenario Outline Check if it is possible to add new basic authority to user role group [A-7052]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "super-admin-adama" and set token of apiUsername "super-admin-adama" 2s 660ms

And Go to "SETTINGS_TAB" 736ms

When Go to "BUYER" authorities settings 831ms

And Click add authority button 226ms

And Select "Dostęp do zakładki Ogłoszenia" in basic authority select 1s 012ms

And Click save authority button 293ms

And Expand "ANNOUNCEMENT" panel 726ms

Then Check if authority "Dostęp do zakładki Ogłoszenia" is "visible" in "ANNOUNCEMENT" authority panel 075ms

Hooks

After Hooks.rollbackAddedAuthorities() 159ms

View Feature UserAuthority

@rollbackAddedAuthorities @TmsLink=A-7052

Scenario Outline Check if it is possible to add new basic authority to user role group [A-7052]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 838ms

And Go to "SETTINGS_TAB" 759ms

When Go to "FORWARDING_AGENT" authorities settings 913ms

And Click add authority button 199ms

And Select "Dostęp do zakładki Ogłoszenia" in basic authority select 1s 003ms

And Click save authority button 316ms

And Expand "ANNOUNCEMENT" panel 910ms

Then Check if authority "Dostęp do zakładki Ogłoszenia" is "visible" in "ANNOUNCEMENT" authority panel 067ms

Hooks

After Hooks.rollbackAddedAuthorities() 149ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@rollbackAddedAuthorities	367	3	0	0	0	370	37	3	40	11m 6s 978ms	Failed

Tag Report