Cucumber-JVM Reports - Tag: @rollbackAddedAuthorities

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.151	09 wrz 2021, 06:10

	Steps	Scenarios	Features
@rollbackAddedAuthorities	367	3	0	0	0	370	37	3	40	11m 19s 126ms	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" 243ms

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

And Clear all cache 2s 759ms

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

And Create company "Firma automaty" 7s 476ms

And Edit company "Firma automaty" 3s 801ms

Then Company is successfully edited 595ms

Hooks

After Hooks.deleteCompanyAfterTest() 156ms

After Hooks.rollbackAddedAuthorities() 185ms

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" 247ms

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

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

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

And Go to "COMPANIES_TAB" 1s 915ms

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

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

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

Hooks

After Hooks.deleteCompanyAfterTest() 112ms

After Hooks.rollbackAddedAuthorities() 136ms

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" 239ms

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

And Login as "adama-admin" 5s 801ms

And Go to "COMPANIES_TAB" 1s 379ms

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

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

And Set existing partnerships 15s 057ms

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

Then Verify that partnership form is visible 111ms

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

When Fill partnership form 1s 697ms

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

When Go to "CARRIER_TAB" 1s 061ms

And Go to details of company in partnership 791ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 996ms

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" 263ms

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

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

And Go to "COMPANIES_TAB" 1s 696ms

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

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

And Set existing partnerships 15s 095ms

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

Then Verify that partnership form is visible 128ms

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

When Fill partnership form 1s 643ms

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

When Go to "COMPANIES_TAB" 1s 074ms

And Go to details of company in partnership 544ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 18s 195ms

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" 222ms

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

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

And Go to "COMPANIES_TAB" 1s 019ms

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

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

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" 247ms

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

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

And Go to "COMPANIES_TAB" 995ms

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

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

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" 251ms

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

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

When Go to "COMPANIES_TAB" 957ms

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

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

And Set existing partnerships 15s 078ms

When Add all partnership 1s 205ms

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

And Set number of partnerships 036ms

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

When Remove partnership 770ms

Then Check that partnership has been deleted 034ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 780ms

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" 246ms

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

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

When Go to "COMPANIES_TAB" 1s 071ms

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

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

And Set existing partnerships 130ms

When Add all partnership 968ms

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

And Set number of partnerships 036ms

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

When Remove partnership 773ms

Then Check that partnership has been deleted 036ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 3s 110ms

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 337ms

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

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

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

And Go to "WAREHOUSE_TAB" 1s 298ms

And Select warehouse "Serownia" 1s 574ms

And Set week view 1s 251ms

And Show yesterday 1s 161ms

And Move window into the past 420ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 342ms

After Hooks.deleteTransportAfterTest() 798ms

After Hooks.rollbackAddedAuthorities() 178ms

View Feature Schedule

@rollbackAddedAuthorities

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

And Go to "WAREHOUSE_TAB" 1s 079ms

When Check if pallet limit counter is visible 094ms

And Set limit to "888" 992ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Authorities

@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" 9s 388ms

And Go to "SETTINGS_TAB" 922ms

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

And Click add authority button 204ms

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

And Click save authority button 261ms

And Expand "ANNOUNCEMENT" panel 1s 030ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 175ms

View Feature Authorities

@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" 12s 999ms

And Go to "SETTINGS_TAB" 894ms

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

And Click add authority button 215ms

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

And Click save authority button 252ms

And Expand "ANNOUNCEMENT" panel 1s 351ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 144ms

View Feature Authorities

@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" 4s 964ms

And Go to "SETTINGS_TAB" 847ms

When Go to "SALES_EMPLOYEE" authorities settings 731ms

And Click add authority button 208ms

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

And Click save authority button 246ms

And Expand "ANNOUNCEMENT" panel 688ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 134ms

View Feature Authorities

@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" 6s 347ms

And Go to "SETTINGS_TAB" 762ms

When Go to "ANALYST" authorities settings 633ms

And Click add authority button 218ms

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

And Click save authority button 239ms

And Expand "ANNOUNCEMENT" panel 588ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 141ms

View Feature Authorities

@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-adama" and set token of apiUsername "super-admin-adama" 5s 282ms

And Go to "SETTINGS_TAB" 738ms

When Go to "BUYER" authorities settings 724ms

And Click add authority button 219ms

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

And Click save authority button 243ms

And Expand "ANNOUNCEMENT" panel 732ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 170ms

View Feature Authorities

@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" 6s 274ms

And Go to "SETTINGS_TAB" 723ms

When Go to "FORWARDING_AGENT" authorities settings 900ms

And Click add authority button 214ms

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

And Click save authority button 239ms

And Expand "ANNOUNCEMENT" panel 981ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 153ms

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 450ms

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

When Go to "TRANSPORT_TABLE" 402ms

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

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

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 434ms

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

When Go to "TRANSPORT_TABLE" 403ms

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

Then Verify that "UNLOAD_TIME_WINDOW" icon is "fa-sort-up" 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 387ms

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

When Go to "TRANSPORT_TABLE" 408ms

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

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

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 475ms

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

When Go to "TRANSPORT_TABLE" 345ms

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

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

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" 230ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 463ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 090ms

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" 223ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 516ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 093ms

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" 232ms

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 944ms

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

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

When Go to "TRANSPORT_TABLE" 519ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 145ms

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" 220ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 365ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 056ms

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" 250ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 494ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 615ms

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" 227ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 527ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 693ms

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" 231ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 483ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 626ms

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" 238ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 511ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 559ms

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" 239ms

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

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 039ms

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

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

When Go to "TRANSPORT_TABLE" 540ms

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

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

Then Go to "WAREHOUSE_TAB" 970ms

And Go to "TRANSPORT_TABLE" 462ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 602ms

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" 245ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 480ms

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

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

Then Go to "WAREHOUSE_TAB" 963ms

And Go to "TRANSPORT_TABLE" 440ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 589ms

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" 137ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 477ms

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

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

Then If user is login then logout 265ms

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

And Go to "TRANSPORT_TABLE" 473ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 565ms

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" 230ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 478ms

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

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

Then If user is login then logout 255ms

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

And Go to "TRANSPORT_TABLE" 478ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 471ms

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) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 950ms

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

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

When Go to "WAREHOUSE_TAB" 1s 384ms

And Select warehouse "Serownia" 1s 613ms

And Set week view 1s 218ms

And Show yesterday 1s 143ms

And Move window into the past 428ms

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

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.15 (660fc11082ba57405eca2e8c49c3e1af756fbfae-refs/branch-heads/4577@{#203}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.36num1}, 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: 677d9294694cb13a6848660ebccec1e0
	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() 929ms

After Hooks.rollbackAddedAuthorities() 133ms

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 472ms

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

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

When Go to "WAREHOUSE_TAB" 1s 411ms

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

And Set week view 1s 276ms

And Show yesterday 1s 180ms

And Move window into the past 604ms

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

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.15 (660fc11082ba57405eca2e8c49c3e1af756fbfae-refs/branch-heads/4577@{#203}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.36num1}, 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: 677d9294694cb13a6848660ebccec1e0
	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() 818ms

After Hooks.rollbackAddedAuthorities() 132ms

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) 001ms

Steps

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

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

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

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

When Show all transport types 1s 153ms

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

And Set advice window in schedule 3s 378ms

And Fill advice form 12s 969ms

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

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

And Set week view 2s 341ms

And Show yesterday 1s 247ms

And Move window into the past 1s 286ms

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

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.15 (660fc11082ba57405eca2e8c49c3e1af756fbfae-refs/branch-heads/4577@{#203}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.36num1}, 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: 677d9294694cb13a6848660ebccec1e0
	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() 842ms

After Hooks.rollbackAddedAuthorities() 123ms

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 171ms

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

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

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

And Go to "WAREHOUSE_TAB" 803ms

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

And Go to next day in schedule 1s 203ms

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

And Select view "DAYS_2" 2s 164ms

And Move advice window "2" 1s 503ms

And Select view "DAY" 2s 168ms

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

And Delete created transport by API 776ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 659ms

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" 232ms

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_USERS_MAIN_DATA" to user "oaa1-receiver-2@qa.qa-test" 382ms

When Login as "oaa1-receiver-2@qa.qa-test" 4s 386ms

And Go to user "oaa1-receiver@qa.qa-test" details edition by prepared link 160ms

And Change user details "email" to "newEmailAddress@newEmail.com" 1s 122ms

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

Then Save user details 986ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 657ms

After Hooks.rollbackAddedAuthorities() 260ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Login as "pskza1-carrier-2@qa.qa-test" 7s 231ms

And Go to user "pskza1-carrier@qa.qa-test" details edition by prepared link 101ms

And Expand "other" notification section 2s 456ms

And Select all notifications in "other" section 275ms

Then Save user details 1s 458ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 909ms

After Hooks.rollbackAddedAuthorities() 160ms

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" 235ms

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;ROLE_EDIT_USERS_MAIN_DATA" to user "adama-buyer@qa.qa-test" 454ms

And Set user details json of user "oaa1-receiver@qa.qa-test" 010ms

When Login as "adama-buyer@qa.qa-test" 5s 014ms

And Go to "USERS_TAB" 1s 470ms

And Find user "oaa1-receiver@qa.qa-test" 3s 705ms

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

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

Then Save user details 1s 049ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 672ms

After Hooks.rollbackAddedAuthorities() 254ms

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" 233ms

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;EDIT_USERS_NOTIFICATION" to user "swisskrono-tradesman@qa.qa-test" 358ms

And Set user details json of user "pskza1-carrier@qa.qa-test" 018ms

When Login as "swisskrono-tradesman@qa.qa-test" 9s 251ms

And Go to "USERS_TAB" 1s 592ms

And Find user "pskza1-carrier@qa.qa-test" 3s 687ms

And Expand "GLUE_FACTORY" notification section 542ms

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

Then Save user details 1s 914ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 082ms

After Hooks.rollbackAddedAuthorities() 254ms

	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 19s 126ms	Failed

Tag Report