Cucumber-JVM Reports - Tag: @rollbackAddedAuthorities

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.148	07 wrz 2021, 06:21

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

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

And Clear all cache 2s 956ms

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

And Create company "Firma automaty" 7s 526ms

And Edit company "Firma automaty" 3s 849ms

Then Company is successfully edited 589ms

Hooks

After Hooks.deleteCompanyAfterTest() 238ms

After Hooks.rollbackAddedAuthorities() 163ms

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

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

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

And Go to "COMPANIES_TAB" 2s 014ms

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

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

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

Hooks

After Hooks.deleteCompanyAfterTest() 126ms

After Hooks.rollbackAddedAuthorities() 150ms

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

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

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

And Go to "COMPANIES_TAB" 1s 393ms

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

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

And Set existing partnerships 15s 103ms

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

Then Verify that partnership form is visible 132ms

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

When Fill partnership form 1s 663ms

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

When Go to "CARRIER_TAB" 1s 151ms

And Go to details of company in partnership 748ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 939ms

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

Steps

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

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

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

And Go to "COMPANIES_TAB" 1s 763ms

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

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

And Set existing partnerships 15s 114ms

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

Then Verify that partnership form is visible 119ms

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

When Fill partnership form 1s 660ms

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

When Go to "COMPANIES_TAB" 1s 107ms

And Go to details of company in partnership 535ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 883ms

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

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

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

And Go to "COMPANIES_TAB" 1s 034ms

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

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

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

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

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

And Go to "COMPANIES_TAB" 1s 031ms

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

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

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

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

When Go to "COMPANIES_TAB" 891ms

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

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

And Set existing partnerships 15s 055ms

When Add all partnership 1s 054ms

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

And Set number of partnerships 038ms

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

When Remove partnership 774ms

Then Check that partnership has been deleted 030ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 812ms

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

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

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

When Go to "COMPANIES_TAB" 1s 039ms

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

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

And Set existing partnerships 129ms

When Add all partnership 1s 001ms

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

And Set number of partnerships 036ms

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

When Remove partnership 778ms

Then Check that partnership has been deleted 033ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 3s 389ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackAddedAuthorities

Scenario Outline Check if mail was sent to after transport delay

Hooks

Before Hooks.showScenarioName(Scenario) 005ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 8s 942ms

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

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

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

And Go to "WAREHOUSE_TAB" 1s 323ms

And Select warehouse "Serownia" 1s 587ms

And Set week view 1s 250ms

And Show yesterday 1s 174ms

And Move window into the past 437ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 427ms

After Hooks.deleteTransportAfterTest() 800ms

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

Steps

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

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

And Go to "WAREHOUSE_TAB" 1s 074ms

When Check if pallet limit counter is visible 090ms

And Set limit to "888" 944ms

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

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

Steps

Given Login as "super-admin-skz" and set token of apiUsername "super-admin-skz" 9s 785ms

And Go to "SETTINGS_TAB" 906ms

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

And Click add authority button 217ms

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

And Click save authority button 265ms

And Expand "ANNOUNCEMENT" panel 1s 099ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 199ms

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

And Go to "SETTINGS_TAB" 896ms

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

And Click add authority button 215ms

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

And Click save authority button 238ms

And Expand "ANNOUNCEMENT" panel 1s 435ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 145ms

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

And Go to "SETTINGS_TAB" 886ms

When Go to "SALES_EMPLOYEE" authorities settings 689ms

And Click add authority button 202ms

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

And Click save authority button 245ms

And Expand "ANNOUNCEMENT" panel 707ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 162ms

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

And Go to "SETTINGS_TAB" 751ms

When Go to "ANALYST" authorities settings 662ms

And Click add authority button 204ms

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

And Click save authority button 252ms

And Expand "ANNOUNCEMENT" panel 639ms

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

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

And Go to "SETTINGS_TAB" 777ms

When Go to "BUYER" authorities settings 880ms

And Click add authority button 230ms

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

And Click save authority button 243ms

And Expand "ANNOUNCEMENT" panel 752ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 151ms

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

And Go to "SETTINGS_TAB" 739ms

When Go to "FORWARDING_AGENT" authorities settings 928ms

And Click add authority button 230ms

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

And Click save authority button 255ms

And Expand "ANNOUNCEMENT" panel 921ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 136ms

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

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

When Go to "TRANSPORT_TABLE" 420ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 373ms

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

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities

Scenario Outline Check if icons change correctly

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

When Go to "TRANSPORT_TABLE" 383ms

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

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

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

When Go to "TRANSPORT_TABLE" 352ms

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

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 511ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 064ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 493ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 089ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 504ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 182ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 495ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 053ms

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 492ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 541ms

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 490ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 676ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 477ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 715ms

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 504ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 628ms

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 483ms

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

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

Then Go to "WAREHOUSE_TAB" 1s 121ms

And Go to "TRANSPORT_TABLE" 493ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 532ms

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 500ms

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

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

Then Go to "WAREHOUSE_TAB" 1s 020ms

And Go to "TRANSPORT_TABLE" 451ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 598ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 495ms

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

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

Then If user is login then logout 261ms

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

And Go to "TRANSPORT_TABLE" 480ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 630ms

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

Steps

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 488ms

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

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

Then If user is login then logout 549ms

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

And Go to "TRANSPORT_TABLE" 480ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 546ms

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

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

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

When Go to "WAREHOUSE_TAB" 1s 618ms

And Select warehouse "Serownia" 1s 594ms

And Set week view 1s 201ms

And Show yesterday 1s 129ms

And Move window into the past 410ms

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

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/temp/buildTmp/.com.google.Chrome.pT0sMq}, 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: e5d58e1fdd819e571fce73e37d49ce81
	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() 858ms

After Hooks.rollbackAddedAuthorities() 131ms

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

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

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

When Go to "WAREHOUSE_TAB" 1s 433ms

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

And Set week view 1s 241ms

And Show yesterday 1s 146ms

And Move window into the past 625ms

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

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/temp/buildTmp/.com.google.Chrome.pT0sMq}, 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: e5d58e1fdd819e571fce73e37d49ce81
	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() 902ms

After Hooks.rollbackAddedAuthorities() 118ms

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

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

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

When Show all transport types 1s 135ms

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

And Set advice window in schedule 3s 346ms

And Fill advice form 13s 141ms

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

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

And Set week view 2s 638ms

And Show yesterday 1s 226ms

And Move window into the past 1s 398ms

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

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/temp/buildTmp/.com.google.Chrome.pT0sMq}, 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: e5d58e1fdd819e571fce73e37d49ce81
	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() 911ms

After Hooks.rollbackAddedAuthorities() 138ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 727ms

And Select warehouse "Magazyn Wyrobów Gotowych" 1s 990ms

And Go to next day in schedule 1s 265ms

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

And Select view "DAYS_2" 2s 153ms

And Move advice window "2" 1s 504ms

And Select view "DAY" 2s 169ms

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

And Delete created transport by API 839ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 663ms

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

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

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

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

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

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

Then Save user details 1s 060ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 659ms

After Hooks.rollbackAddedAuthorities() 254ms

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

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

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

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

And Expand "other" notification section 2s 475ms

And Select all notifications in "other" section 292ms

Then Save user details 1s 527ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 909ms

After Hooks.rollbackAddedAuthorities() 143ms

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

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

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

When Login as "adama-buyer@qa.qa-test" 4s 963ms

And Go to "USERS_TAB" 1s 465ms

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

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

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

Then Save user details 1s 002ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 657ms

After Hooks.rollbackAddedAuthorities() 249ms

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

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

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

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

And Go to "USERS_TAB" 1s 537ms

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

And Expand "GLUE_FACTORY" notification section 539ms

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

Then Save user details 1s 835ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 036ms

After Hooks.rollbackAddedAuthorities() 232ms

	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 29s 936ms	Failed

Tag Report