Cucumber-JVM Reports - Tag: @rollbackAddedAuthorities

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.145	04 wrz 2021, 06:09

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

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

And Clear all cache 2s 866ms

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

And Create company "Firma automaty" 7s 651ms

And Edit company "Firma automaty" 3s 766ms

Then Company is successfully edited 631ms

Hooks

After Hooks.deleteCompanyAfterTest() 296ms

After Hooks.rollbackAddedAuthorities() 201ms

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

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

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

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

And Go to "COMPANIES_TAB" 1s 931ms

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

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

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

Hooks

After Hooks.deleteCompanyAfterTest() 137ms

After Hooks.rollbackAddedAuthorities() 151ms

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

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

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

And Go to "COMPANIES_TAB" 1s 379ms

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

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

And Set existing partnerships 15s 062ms

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

Then Verify that partnership form is visible 116ms

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

When Fill partnership form 1s 679ms

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

When Go to "CARRIER_TAB" 1s 096ms

And Go to details of company in partnership 1s 069ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 869ms

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

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

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

And Go to "COMPANIES_TAB" 1s 710ms

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

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

And Set existing partnerships 15s 050ms

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

Then Verify that partnership form is visible 128ms

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

When Fill partnership form 1s 662ms

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

When Go to "COMPANIES_TAB" 1s 016ms

And Go to details of company in partnership 534ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 822ms

View Feature Company

@rollbackAddedAuthorities

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Go to "COMPANIES_TAB" 1s 027ms

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

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

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

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

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

And Go to "COMPANIES_TAB" 1s 031ms

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

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

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

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

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

When Go to "COMPANIES_TAB" 947ms

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

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

And Set existing partnerships 15s 054ms

When Add all partnership 1s 044ms

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

And Set number of partnerships 033ms

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

When Remove partnership 775ms

Then Check that partnership has been deleted 031ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 843ms

View Feature Company

@removeAllAddedPartnership @rollbackAddedAuthorities

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

When Go to "COMPANIES_TAB" 1s 011ms

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

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

And Set existing partnerships 142ms

When Add all partnership 989ms

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

And Set number of partnerships 033ms

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

When Remove partnership 770ms

Then Check that partnership has been deleted 031ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 3s 033ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 369ms

And Select warehouse "Serownia" 1s 582ms

And Set week view 1s 261ms

And Show yesterday 1s 163ms

And Move window into the past 410ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 538ms

After Hooks.deleteTransportAfterTest() 825ms

After Hooks.rollbackAddedAuthorities() 127ms

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" 5s 427ms

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

And Go to "WAREHOUSE_TAB" 1s 122ms

When Check if pallet limit counter is visible 081ms

And Set limit to "888" 874ms

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

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

And Go to "SETTINGS_TAB" 921ms

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

And Click add authority button 232ms

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

And Click save authority button 261ms

And Expand "ANNOUNCEMENT" panel 1s 054ms

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

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

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 13s 066ms

And Go to "SETTINGS_TAB" 929ms

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

And Click add authority button 210ms

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

And Click save authority button 266ms

And Expand "ANNOUNCEMENT" panel 1s 472ms

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

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

And Go to "SETTINGS_TAB" 809ms

When Go to "SALES_EMPLOYEE" authorities settings 700ms

And Click add authority button 203ms

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

And Click save authority button 243ms

And Expand "ANNOUNCEMENT" panel 651ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 158ms

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

And Go to "SETTINGS_TAB" 736ms

When Go to "ANALYST" authorities settings 641ms

And Click add authority button 203ms

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

And Click save authority button 246ms

And Expand "ANNOUNCEMENT" panel 612ms

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

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

And Go to "SETTINGS_TAB" 781ms

When Go to "BUYER" authorities settings 838ms

And Click add authority button 211ms

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

And Click save authority button 235ms

And Expand "ANNOUNCEMENT" panel 710ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 160ms

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

And Go to "SETTINGS_TAB" 738ms

When Go to "FORWARDING_AGENT" authorities settings 921ms

And Click add authority button 214ms

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

And Click save authority button 234ms

And Expand "ANNOUNCEMENT" panel 914ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 142ms

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

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

When Go to "TRANSPORT_TABLE" 378ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 396ms

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

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities

Scenario Outline Check if icons change correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Go to "TRANSPORT_TABLE" 362ms

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

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

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

When Go to "TRANSPORT_TABLE" 382ms

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

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports time window dates sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 467ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 195ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 495ms

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

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

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

Steps

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

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

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

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

When Go to "TRANSPORT_TABLE" 493ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 078ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 529ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 057ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 481ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 666ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 541ms

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

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

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 492ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 621ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 518ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 699ms

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 476ms

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

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

Then Go to "WAREHOUSE_TAB" 947ms

And Go to "TRANSPORT_TABLE" 444ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 625ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports are correctly sorted after switching tabs

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 544ms

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

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

Then Go to "WAREHOUSE_TAB" 984ms

And Go to "TRANSPORT_TABLE" 429ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 554ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 486ms

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

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

Then If user is login then logout 257ms

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

And Go to "TRANSPORT_TABLE" 481ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 645ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 468ms

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

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

Then If user is login then logout 255ms

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

And Go to "TRANSPORT_TABLE" 483ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 533ms

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

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

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

When Go to "WAREHOUSE_TAB" 1s 416ms

And Select warehouse "Serownia" 1s 613ms

And Set week view 1s 258ms

And Show yesterday 1s 150ms

And Move window into the past 447ms

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

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.v9eBqc}, 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: 812da860b6da29d004a03a7609d673fc
	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() 797ms

After Hooks.rollbackAddedAuthorities() 197ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

When Go to "WAREHOUSE_TAB" 1s 479ms

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

And Set week view 1s 230ms

And Show yesterday 1s 144ms

And Move window into the past 578ms

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-2/temp/buildTmp/.com.google.Chrome.v9eBqc}, 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: 812da860b6da29d004a03a7609d673fc
	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() 852ms

After Hooks.rollbackAddedAuthorities() 139ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 746ms

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

And Go to next day in schedule 1s 188ms

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

And Select view "DAYS_2" 2s 166ms

And Move advice window "2" 1s 521ms

And Select view "DAY" 2s 151ms

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

And Delete created transport by API 825ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 651ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7965

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

Then Save user details 1s 012ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 656ms

After Hooks.rollbackAddedAuthorities() 283ms

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

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

When Login as "pskza1-carrier-2@qa.qa-test" 6s 993ms

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

And Expand "other" notification section 2s 434ms

And Select all notifications in "other" section 256ms

Then Save user details 1s 484ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 898ms

After Hooks.rollbackAddedAuthorities() 153ms

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

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

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

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

And Go to "USERS_TAB" 1s 588ms

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

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

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

Then Save user details 1s 057ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 649ms

After Hooks.rollbackAddedAuthorities() 244ms

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

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

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

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

And Go to "USERS_TAB" 1s 527ms

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

And Expand "GLUE_FACTORY" notification section 529ms

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

Then Save user details 1s 856ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 056ms

After Hooks.rollbackAddedAuthorities() 243ms

	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 17s 023ms	Failed

Tag Report