Cucumber-JVM Reports - Tag: @rollbackAddedAuthorities

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.149	08 wrz 2021, 06:16

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

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

And Clear all cache 2s 790ms

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

And Create company "Firma automaty" 7s 575ms

And Edit company "Firma automaty" 3s 761ms

Then Company is successfully edited 526ms

Hooks

After Hooks.deleteCompanyAfterTest() 139ms

After Hooks.rollbackAddedAuthorities() 177ms

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

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

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

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

And Go to "COMPANIES_TAB" 1s 936ms

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

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

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

Hooks

After Hooks.deleteCompanyAfterTest() 153ms

After Hooks.rollbackAddedAuthorities() 146ms

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

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

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

And Go to "COMPANIES_TAB" 1s 351ms

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

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

And Set existing partnerships 15s 049ms

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

Then Verify that partnership form is visible 123ms

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

When Fill partnership form 1s 680ms

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

When Go to "CARRIER_TAB" 1s 144ms

And Go to details of company in partnership 778ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 986ms

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

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

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

And Go to "COMPANIES_TAB" 1s 737ms

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

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

And Set existing partnerships 15s 052ms

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

Then Verify that partnership form is visible 123ms

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

When Fill partnership form 1s 645ms

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

When Go to "COMPANIES_TAB" 1s 104ms

And Go to details of company in partnership 536ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 977ms

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

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

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

And Go to "COMPANIES_TAB" 988ms

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

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

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

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

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

And Go to "COMPANIES_TAB" 999ms

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

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

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

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

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

When Go to "COMPANIES_TAB" 937ms

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

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

And Set existing partnerships 15s 064ms

When Add all partnership 1s 085ms

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

And Set number of partnerships 046ms

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

When Remove partnership 768ms

Then Check that partnership has been deleted 029ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 885ms

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

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

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

When Go to "COMPANIES_TAB" 1s 002ms

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

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

And Set existing partnerships 132ms

When Add all partnership 957ms

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

And Set number of partnerships 037ms

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

When Remove partnership 769ms

Then Check that partnership has been deleted 041ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 3s 022ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 413ms

And Select warehouse "Serownia" 1s 646ms

And Set week view 1s 262ms

And Show yesterday 1s 175ms

And Move window into the past 436ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 433ms

After Hooks.deleteTransportAfterTest() 773ms

After Hooks.rollbackAddedAuthorities() 189ms

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

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

And Go to "WAREHOUSE_TAB" 1s 103ms

When Check if pallet limit counter is visible 088ms

And Set limit to "888" 985ms

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

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

And Go to "SETTINGS_TAB" 923ms

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

And Click add authority button 221ms

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

And Click save authority button 255ms

And Expand "ANNOUNCEMENT" panel 1s 077ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 180ms

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" 13s 214ms

And Go to "SETTINGS_TAB" 921ms

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

And Click add authority button 226ms

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

And Click save authority button 258ms

And Expand "ANNOUNCEMENT" panel 1s 458ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 156ms

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

And Go to "SETTINGS_TAB" 828ms

When Go to "SALES_EMPLOYEE" authorities settings 732ms

And Click add authority button 214ms

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

And Click save authority button 248ms

And Expand "ANNOUNCEMENT" panel 679ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 157ms

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

And Go to "SETTINGS_TAB" 788ms

When Go to "ANALYST" authorities settings 635ms

And Click add authority button 228ms

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

And Click save authority button 242ms

And Expand "ANNOUNCEMENT" panel 615ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 133ms

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

And Go to "SETTINGS_TAB" 811ms

When Go to "BUYER" authorities settings 806ms

And Click add authority button 223ms

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

And Click save authority button 243ms

And Expand "ANNOUNCEMENT" panel 713ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 154ms

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

And Go to "SETTINGS_TAB" 741ms

When Go to "FORWARDING_AGENT" authorities settings 911ms

And Click add authority button 206ms

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

And Click save authority button 250ms

And Expand "ANNOUNCEMENT" panel 953ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 169ms

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

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

When Go to "TRANSPORT_TABLE" 414ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 344ms

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

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

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

When Go to "TRANSPORT_TABLE" 406ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 390ms

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

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

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

Steps

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 489ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 083ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 527ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 106ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 494ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 096ms

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

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

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

When Go to "TRANSPORT_TABLE" 494ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 099ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 499ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 4s 502ms

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 525ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 631ms

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 498ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 645ms

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 529ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 609ms

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 476ms

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

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

Then Go to "WAREHOUSE_TAB" 948ms

And Go to "TRANSPORT_TABLE" 435ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 518ms

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 545ms

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

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

Then Go to "WAREHOUSE_TAB" 1s 034ms

And Go to "TRANSPORT_TABLE" 442ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 608ms

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 516ms

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

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

Then If user is login then logout 243ms

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

And Go to "TRANSPORT_TABLE" 481ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 550ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 469ms

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

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

Then If user is login then logout 498ms

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

And Go to "TRANSPORT_TABLE" 482ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 610ms

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" 3s 007ms

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

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

When Go to "WAREHOUSE_TAB" 1s 480ms

And Select warehouse "Serownia" 1s 595ms

And Set week view 1s 219ms

And Show yesterday 1s 146ms

And Move window into the past 438ms

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

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.YcHu2J}, 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: 13fedc522d7dee1a732dea1116ebf13a
	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() 844ms

After Hooks.rollbackAddedAuthorities() 179ms

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

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

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

When Go to "WAREHOUSE_TAB" 1s 465ms

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

And Set week view 1s 295ms

And Show yesterday 1s 181ms

And Move window into the past 615ms

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

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.YcHu2J}, 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: 13fedc522d7dee1a732dea1116ebf13a
	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() 832ms

After Hooks.rollbackAddedAuthorities() 134ms

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

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 996ms

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

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

When Show all transport types 1s 157ms

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

And Set advice window in schedule 3s 372ms

And Fill advice form 12s 846ms

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

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

And Set week view 2s 425ms

And Show yesterday 1s 225ms

And Move window into the past 1s 218ms

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

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.YcHu2J}, 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: 13fedc522d7dee1a732dea1116ebf13a
	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() 885ms

After Hooks.rollbackAddedAuthorities() 146ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 700ms

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

And Go to next day in schedule 1s 425ms

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

And Select view "DAYS_2" 2s 194ms

And Move advice window "2" 1s 503ms

And Select view "DAY" 2s 160ms

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

And Delete created transport by API 803ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 680ms

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

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

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

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

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

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

Then Save user details 981ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 658ms

After Hooks.rollbackAddedAuthorities() 279ms

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

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

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

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

And Expand "other" notification section 2s 435ms

And Select all notifications in "other" section 283ms

Then Save user details 1s 498ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 876ms

After Hooks.rollbackAddedAuthorities() 147ms

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

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

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

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

And Go to "USERS_TAB" 1s 452ms

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

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

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

Then Save user details 986ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 765ms

After Hooks.rollbackAddedAuthorities() 286ms

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

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

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

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

And Go to "USERS_TAB" 1s 606ms

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

And Expand "GLUE_FACTORY" notification section 595ms

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

Then Save user details 1s 907ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 005ms

After Hooks.rollbackAddedAuthorities() 231ms

	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 26s 192ms	Failed

Tag Report