Cucumber-JVM Reports - Tag: @rollbackAddedAuthorities

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.125	20 sie 2021, 05:38

	Steps	Scenarios	Features
@rollbackAddedAuthorities	364	1	5	0	0	370	39	1	40	10m 44s 164ms	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" 236ms

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

And Clear all cache 2s 787ms

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

And Create company "Firma automaty" 6s 517ms

And Edit company "Firma automaty" 2s 754ms

Then Company is successfully edited 585ms

Hooks

After Hooks.deleteCompanyAfterTest() 116ms

After Hooks.rollbackAddedAuthorities() 158ms

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

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

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

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

And Go to "COMPANIES_TAB" 1s 910ms

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

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

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

Hooks

After Hooks.deleteCompanyAfterTest() 117ms

After Hooks.rollbackAddedAuthorities() 149ms

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

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

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

And Go to "COMPANIES_TAB" 1s 369ms

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

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

And Set existing partnerships 15s 104ms

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

Then Verify that partnership form is visible 129ms

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

When Fill partnership form 1s 642ms

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

When Go to "CARRIER_TAB" 1s 138ms

And Go to details of company in partnership 776ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 18s 077ms

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

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

And Login as "neuca-admin" 10s 647ms

And Go to "COMPANIES_TAB" 1s 802ms

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

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

And Set existing partnerships 15s 096ms

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

Then Verify that partnership form is visible 086ms

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

When Fill partnership form 1s 600ms

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

When Go to "COMPANIES_TAB" 1s 119ms

And Go to details of company in partnership 541ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 18s 291ms

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

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

And Go to "COMPANIES_TAB" 1s 057ms

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

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

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

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

And Login as "super-admin-neuca" 9s 919ms

And Go to "COMPANIES_TAB" 1s 059ms

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

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Company

@removeAllAddedPartnership @rollbackAddedAuthorities

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

When Go to "COMPANIES_TAB" 919ms

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

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

And Set existing partnerships 15s 105ms

When Add all partnership 1s 040ms

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

And Set number of partnerships 034ms

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

When Remove partnership 788ms

Then Check that partnership has been deleted 032ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 847ms

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

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

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

When Go to "COMPANIES_TAB" 1s 040ms

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

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

And Set existing partnerships 125ms

When Add all partnership 979ms

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

And Set number of partnerships 031ms

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

When Remove partnership 786ms

Then Check that partnership has been deleted 035ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 3s 124ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 338ms

And Select warehouse "Serownia" 1s 541ms

And Set week view 1s 239ms

And Show yesterday 1s 163ms

And Move window into the past 422ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 343ms

After Hooks.deleteTransportAfterTest() 798ms

After Hooks.rollbackAddedAuthorities() 159ms

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

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

And Go to "WAREHOUSE_TAB" 1s 074ms

When Check if pallet limit counter is visible 101ms

And Set limit to "888" 976ms

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

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

And Go to "SETTINGS_TAB" 898ms

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

And Click add authority button 218ms

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

And Click save authority button 267ms

And Expand "ANNOUNCEMENT" panel 1s 062ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 154ms

View Feature Authorities

@rollbackAddedAuthorities @TmsLink=A-7052

Scenario Outline Check if it is possible to add new basic authority to user role group [A-7052]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Go to "SETTINGS_TAB" 877ms

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

And Click add authority button 222ms

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

And Click save authority button 251ms

And Expand "ANNOUNCEMENT" panel 1s 399ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 143ms

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

And Go to "SETTINGS_TAB" 793ms

When Go to "SALES_EMPLOYEE" authorities settings 676ms

And Click add authority button 235ms

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

And Click save authority button 248ms

And Expand "ANNOUNCEMENT" panel 663ms

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

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-farmacol" and set token of apiUsername "super-admin-farmacol" 7s 140ms

And Go to "SETTINGS_TAB" 765ms

When Go to "ANALYST" authorities settings 615ms

And Click add authority button 222ms

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

And Click save authority button 260ms

And Expand "ANNOUNCEMENT" panel 636ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 172ms

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

And Go to "SETTINGS_TAB" 788ms

When Go to "BUYER" authorities settings 790ms

And Click add authority button 220ms

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

And Click save authority button 247ms

And Expand "ANNOUNCEMENT" panel 715ms

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

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

And Go to "SETTINGS_TAB" 700ms

When Go to "FORWARDING_AGENT" authorities settings 907ms

And Click add authority button 218ms

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

And Click save authority button 248ms

And Expand "ANNOUNCEMENT" panel 906ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 166ms

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

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

When Go to "TRANSPORT_TABLE" 362ms

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

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities

Scenario Outline Check if icons change correctly

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

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

When Go to "TRANSPORT_TABLE" 421ms

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

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities

Scenario Outline Check if icons change correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Go to "TRANSPORT_TABLE" 396ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 360ms

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

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

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

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-sempertrans" 2s 003ms

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

When Go to "TRANSPORT_TABLE" 367ms

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

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 491ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 051ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 522ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 060ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 487ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 061ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 507ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 682ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 510ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 587ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 497ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 644ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports statuses sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 481ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 661ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 519ms

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

And Go to "TRANSPORT_TABLE" 455ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 604ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 472ms

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

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

Then Go to "WAREHOUSE_TAB" 1s 011ms

And Go to "TRANSPORT_TABLE" 428ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 623ms

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 489ms

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

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

Then If user is login then logout 242ms

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

And Go to "TRANSPORT_TABLE" 479ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 591ms

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 477ms

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

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

Then If user is login then logout 255ms

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

And Go to "TRANSPORT_TABLE" 470ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 655ms

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

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

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

When Go to "WAREHOUSE_TAB" 1s 378ms

And Select warehouse "Serownia" 1s 578ms

And Set week view 1s 263ms

And Show yesterday 1s 170ms

And Move window into the past 402ms

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

Hooks

After Hooks.deleteTransportAfterTest() 823ms

After Hooks.rollbackAddedAuthorities() 183ms

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

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

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

When Go to "WAREHOUSE_TAB" 1s 339ms

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

And Set week view 1s 292ms

And Show yesterday 1s 186ms

And Move window into the past 621ms

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

Hooks

After Hooks.deleteTransportAfterTest() 790ms

After Hooks.rollbackAddedAuthorities() 130ms

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

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

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

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

When Show all transport types 1s 150ms

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

And Set advice window in schedule 3s 425ms

And Fill advice form 13s 074ms

And Click advice save button and wait for advice form to disappear 10s 738ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='save'] (tried for 10 second(s) with 500 MILLISECONDS interval)
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=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.vEGcDT}, 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=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: a49ddeab5d6912da551cc3077a4ae0a5
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:217)
	at Pages.Transport.AdviceFormPage.confirm(AdviceFormPage.java:27)
	at CucumberTests.Transport.AdviceTransport.clickAdviceSaveButtonAndWaitForAdviceFormToDisappear(AdviceTransport.java:179)
	at ✽.Click advice save button and wait for advice form to disappear(file:Features/Atom/TimeWindow/TransportWindow.feature:30)

And Select warehouse "Magazyn Hala A" 000ms

And Set week view 000ms

And Show yesterday 000ms

And Move window into the past 000ms

Then Check if window is "red" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 520ms

After Hooks.rollbackAddedAuthorities() 141ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 767ms

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

And Go to next day in schedule 1s 198ms

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

And Select view "DAYS_2" 2s 160ms

And Move advice window "2" 1s 517ms

And Select view "DAY" 2s 154ms

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

And Delete created transport by API 760ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 659ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7965

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

Then Save user details 984ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 677ms

After Hooks.rollbackAddedAuthorities() 304ms

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

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

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

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

And Expand "other" notification section 2s 600ms

And Select all notifications in "other" section 266ms

Then Save user details 1s 505ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 938ms

After Hooks.rollbackAddedAuthorities() 151ms

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

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

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

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

And Go to "USERS_TAB" 1s 472ms

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

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

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

Then Save user details 1s 052ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 663ms

After Hooks.rollbackAddedAuthorities() 236ms

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

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

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

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

And Go to "USERS_TAB" 1s 603ms

And Find user "pskza1-carrier@qa.qa-test" 2s 699ms

And Expand "GLUE_FACTORY" notification section 542ms

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

Then Save user details 2s 110ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 042ms

After Hooks.rollbackAddedAuthorities() 248ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@rollbackAddedAuthorities	364	1	5	0	0	370	39	1	40	10m 44s 164ms	Failed

Tag Report