Cucumber-JVM Reports - Tag: @rollbackAddedAuthorities

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

	Steps	Scenarios	Features
@rollbackAddedAuthorities	354	2	0	0	0	356	37	2	39	10m 11s 257ms	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" 265ms

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

And Clear all cache 2s 720ms

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

And Create company "Firma automaty" 7s 467ms

And Edit company "Firma automaty" 3s 751ms

Then Company is successfully edited 592ms

Hooks

After Hooks.deleteCompanyAfterTest() 247ms

After Hooks.rollbackAddedAuthorities() 156ms

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

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

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

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

And Go to "COMPANIES_TAB" 1s 939ms

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

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

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

Hooks

After Hooks.deleteCompanyAfterTest() 135ms

After Hooks.rollbackAddedAuthorities() 131ms

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

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

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

And Go to "COMPANIES_TAB" 1s 396ms

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

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

And Set existing partnerships 15s 062ms

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

Then Verify that partnership form is visible 090ms

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

When Fill partnership form 1s 640ms

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

When Go to "CARRIER_TAB" 1s 069ms

And Go to details of company in partnership 702ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 928ms

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

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

And Login as "neuca-admin" 8s 959ms

And Go to "COMPANIES_TAB" 1s 725ms

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

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

And Set existing partnerships 15s 075ms

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

Then Verify that partnership form is visible 123ms

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

When Fill partnership form 1s 606ms

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

When Go to "COMPANIES_TAB" 1s 073ms

And Go to details of company in partnership 533ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 868ms

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

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

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

And Go to "COMPANIES_TAB" 1s 064ms

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

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

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

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

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

And Go to "COMPANIES_TAB" 1s 011ms

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

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

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

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

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

When Go to "COMPANIES_TAB" 944ms

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

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

And Set existing partnerships 15s 102ms

When Add all partnership 1s 018ms

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

And Set number of partnerships 035ms

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

When Remove partnership 764ms

Then Check that partnership has been deleted 034ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 835ms

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

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

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

When Go to "COMPANIES_TAB" 1s 032ms

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

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

And Set existing partnerships 125ms

When Add all partnership 962ms

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

And Set number of partnerships 037ms

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

When Remove partnership 797ms

Then Check that partnership has been deleted 032ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 3s 152ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 481ms

And Select warehouse "Serownia" 1s 561ms

And Set week view 1s 216ms

And Show yesterday 1s 129ms

And Move window into the past 407ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 308ms

After Hooks.deleteTransportAfterTest() 973ms

After Hooks.rollbackAddedAuthorities() 156ms

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

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

And Go to "WAREHOUSE_TAB" 1s 122ms

When Check if pallet limit counter is visible 079ms

And Set limit to "888" 843ms

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

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

And Go to "SETTINGS_TAB" 967ms

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

And Click add authority button 220ms

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

And Click save authority button 260ms

And Expand "ANNOUNCEMENT" panel 1s 046ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 173ms

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

And Go to "SETTINGS_TAB" 880ms

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

And Click add authority button 212ms

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

And Click save authority button 258ms

And Expand "ANNOUNCEMENT" panel 1s 524ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 147ms

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

And Go to "SETTINGS_TAB" 799ms

When Go to "SALES_EMPLOYEE" authorities settings 708ms

And Click add authority button 221ms

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

And Click save authority button 256ms

And Expand "ANNOUNCEMENT" panel 669ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 167ms

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

And Go to "SETTINGS_TAB" 774ms

When Go to "ANALYST" authorities settings 620ms

And Click add authority button 195ms

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

And Click save authority button 246ms

And Expand "ANNOUNCEMENT" panel 641ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 184ms

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

And Go to "SETTINGS_TAB" 789ms

When Go to "BUYER" authorities settings 747ms

And Click add authority button 211ms

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

And Click save authority button 229ms

And Expand "ANNOUNCEMENT" panel 714ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 163ms

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

And Go to "SETTINGS_TAB" 725ms

When Go to "FORWARDING_AGENT" authorities settings 977ms

And Click add authority button 200ms

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

And Click save authority button 238ms

And Expand "ANNOUNCEMENT" panel 878ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 154ms

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

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

When Go to "TRANSPORT_TABLE" 346ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 401ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 380ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 342ms

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

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports time window dates sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 441ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 087ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 490ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 085ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports time window dates sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

When Go to "TRANSPORT_TABLE" 491ms

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 521ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 077ms

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 470ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 670ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports statuses sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 526ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 759ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 464ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 654ms

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 508ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 653ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 508ms

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

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

Then Go to "WAREHOUSE_TAB" 988ms

And Go to "TRANSPORT_TABLE" 452ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 616ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 520ms

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

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

Then Go to "WAREHOUSE_TAB" 949ms

And Go to "TRANSPORT_TABLE" 482ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 616ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 499ms

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

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

Then If user is login then logout 241ms

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

And Go to "TRANSPORT_TABLE" 482ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 584ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 485ms

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

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

Then If user is login then logout 247ms

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

And Go to "TRANSPORT_TABLE" 562ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 389ms

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

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

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

When Go to "WAREHOUSE_TAB" 1s 406ms

And Select warehouse "Serownia" 1s 595ms

And Set week view 1s 262ms

And Show yesterday 1s 163ms

And Move window into the past 451ms

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.nXQC78}, 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: 9cf8c623213683dad42f700c3a1a1e2f
	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() 940ms

After Hooks.rollbackAddedAuthorities() 135ms

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

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

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

When Go to "WAREHOUSE_TAB" 1s 442ms

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

And Set week view 1s 262ms

And Show yesterday 1s 183ms

And Move window into the past 593ms

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.nXQC78}, 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: 9cf8c623213683dad42f700c3a1a1e2f
	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() 802ms

After Hooks.rollbackAddedAuthorities() 129ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if window counter value in schedule changes

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

And Go to "WAREHOUSE_TAB" 782ms

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

And Go to next day in schedule 1s 210ms

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

And Select view "DAYS_2" 2s 169ms

And Move advice window "2" 1s 495ms

And Select view "DAY" 2s 157ms

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

And Delete created transport by API 779ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 664ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7965

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

Then Save user details 1s 051ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 642ms

After Hooks.rollbackAddedAuthorities() 248ms

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

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

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

And Expand "other" notification section 2s 427ms

And Select all notifications in "other" section 304ms

Then Save user details 1s 541ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 884ms

After Hooks.rollbackAddedAuthorities() 139ms

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

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

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

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

And Go to "USERS_TAB" 1s 485ms

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

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

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

Then Save user details 989ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 645ms

After Hooks.rollbackAddedAuthorities() 253ms

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

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

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

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

And Go to "USERS_TAB" 1s 554ms

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

And Expand "GLUE_FACTORY" notification section 542ms

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

Then Save user details 1s 823ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 927ms

After Hooks.rollbackAddedAuthorities() 221ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@rollbackAddedAuthorities	354	2	0	0	0	356	37	2	39	10m 11s 257ms	Failed

Tag Report