Cucumber-JVM Reports - Tag: @rollbackAddedAuthorities

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.146	05 wrz 2021, 06:14

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

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

And Clear all cache 2s 732ms

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

And Create company "Firma automaty" 7s 566ms

And Edit company "Firma automaty" 3s 721ms

Then Company is successfully edited 536ms

Hooks

After Hooks.deleteCompanyAfterTest() 266ms

After Hooks.rollbackAddedAuthorities() 160ms

View Feature Company

@deleteCompanyAfterTest @rollbackAddedAuthorities

Scenario Outline Check if it possible to add company patron in company details

Hooks

Before Hooks.showScenarioName(Scenario) 003ms

Steps

Given Set token of apiUsername "super-admin-pgf" 280ms

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

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

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

And Go to "COMPANIES_TAB" 1s 934ms

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

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

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

Hooks

After Hooks.deleteCompanyAfterTest() 130ms

After Hooks.rollbackAddedAuthorities() 143ms

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

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

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

And Go to "COMPANIES_TAB" 1s 417ms

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

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

And Set existing partnerships 15s 068ms

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

Then Verify that partnership form is visible 097ms

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

When Fill partnership form 1s 639ms

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

When Go to "CARRIER_TAB" 1s 038ms

And Go to details of company in partnership 810ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 831ms

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

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

And Go to "COMPANIES_TAB" 1s 690ms

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

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

And Set existing partnerships 15s 088ms

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

Then Verify that partnership form is visible 122ms

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

When Fill partnership form 1s 636ms

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

When Go to "COMPANIES_TAB" 1s 028ms

And Go to details of company in partnership 555ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 898ms

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

Steps

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

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

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

And Go to "COMPANIES_TAB" 1s 049ms

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

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

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

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

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

And Go to "COMPANIES_TAB" 1s 025ms

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

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

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

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

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

When Go to "COMPANIES_TAB" 952ms

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

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

And Set existing partnerships 15s 067ms

When Add all partnership 1s 049ms

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

And Set number of partnerships 033ms

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

When Remove partnership 779ms

Then Check that partnership has been deleted 031ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 812ms

View Feature Company

@removeAllAddedPartnership @rollbackAddedAuthorities

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

When Go to "COMPANIES_TAB" 987ms

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

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

And Set existing partnerships 130ms

When Add all partnership 959ms

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

And Set number of partnerships 038ms

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

When Remove partnership 777ms

Then Check that partnership has been deleted 034ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 3s 078ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 424ms

And Select warehouse "Serownia" 1s 651ms

And Set week view 1s 258ms

And Show yesterday 1s 148ms

And Move window into the past 413ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 386ms

After Hooks.deleteTransportAfterTest() 768ms

After Hooks.rollbackAddedAuthorities() 216ms

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

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

And Go to "WAREHOUSE_TAB" 1s 154ms

When Check if pallet limit counter is visible 089ms

And Set limit to "888" 951ms

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

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

And Go to "SETTINGS_TAB" 940ms

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

And Click add authority button 232ms

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

And Click save authority button 259ms

And Expand "ANNOUNCEMENT" panel 1s 077ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 159ms

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

And Go to "SETTINGS_TAB" 883ms

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

And Click add authority button 208ms

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

And Click save authority button 248ms

And Expand "ANNOUNCEMENT" panel 1s 349ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 141ms

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

And Go to "SETTINGS_TAB" 836ms

When Go to "SALES_EMPLOYEE" authorities settings 740ms

And Click add authority button 218ms

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

And Click save authority button 282ms

And Expand "ANNOUNCEMENT" panel 755ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 168ms

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

And Go to "SETTINGS_TAB" 735ms

When Go to "ANALYST" authorities settings 664ms

And Click add authority button 217ms

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

And Click save authority button 231ms

And Expand "ANNOUNCEMENT" panel 636ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 140ms

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

And Go to "SETTINGS_TAB" 780ms

When Go to "BUYER" authorities settings 776ms

And Click add authority button 207ms

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

And Click save authority button 241ms

And Expand "ANNOUNCEMENT" panel 724ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 155ms

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

And Go to "SETTINGS_TAB" 774ms

When Go to "FORWARDING_AGENT" authorities settings 902ms

And Click add authority button 210ms

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

And Click save authority button 255ms

And Expand "ANNOUNCEMENT" panel 869ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 146ms

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

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

When Go to "TRANSPORT_TABLE" 420ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 401ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 351ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 360ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 478ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 090ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports time window dates sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 004ms

Steps

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 454ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 199ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 479ms

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

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 507ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 960ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 500ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 648ms

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 515ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 642ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 476ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 645ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports statuses sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 519ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 577ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 460ms

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

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

Then Go to "WAREHOUSE_TAB" 1s 037ms

And Go to "TRANSPORT_TABLE" 426ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 602ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 509ms

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

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

Then Go to "WAREHOUSE_TAB" 936ms

And Go to "TRANSPORT_TABLE" 434ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 537ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 474ms

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

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

Then If user is login then logout 228ms

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

And Go to "TRANSPORT_TABLE" 470ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 607ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 493ms

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

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

Then If user is login then logout 235ms

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

And Go to "TRANSPORT_TABLE" 482ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 602ms

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

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

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

When Go to "WAREHOUSE_TAB" 1s 427ms

And Select warehouse "Serownia" 1s 585ms

And Set week view 1s 218ms

And Show yesterday 1s 129ms

And Move window into the past 432ms

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.JodGHj}, 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: 5b4be4f0d4e5e9c51e0c52affa36e4e5
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:279)
	at org.openqa.selenium.remote.RemoteWebElement.getAttribute(RemoteWebElement.java:128)
	at Utils.TestUtil.elementHasColor(TestUtil.java:30)
	at CucumberTests.Schedule.ScheduleTest.checkIfWindowIs(ScheduleTest.java:58)
	at ✽.Check if window is "red"(file:Features/Atom/TimeWindow/TransportWindow.feature:14)

Hooks

After Hooks.deleteTransportAfterTest() 858ms

After Hooks.rollbackAddedAuthorities() 155ms

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

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

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

When Go to "WAREHOUSE_TAB" 1s 330ms

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

And Set week view 1s 297ms

And Show yesterday 1s 187ms

And Move window into the past 629ms

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

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.JodGHj}, 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: 5b4be4f0d4e5e9c51e0c52affa36e4e5
	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() 726ms

After Hooks.rollbackAddedAuthorities() 115ms

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" 2s 993ms

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

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

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

And Go to "WAREHOUSE_TAB" 750ms

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

And Go to next day in schedule 1s 218ms

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

And Select view "DAYS_2" 2s 186ms

And Move advice window "2" 1s 520ms

And Select view "DAY" 2s 159ms

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

And Delete created transport by API 785ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 640ms

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

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

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

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

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

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

Then Save user details 1s 083ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 657ms

After Hooks.rollbackAddedAuthorities() 233ms

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

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

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

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

And Expand "other" notification section 2s 392ms

And Select all notifications in "other" section 290ms

Then Save user details 1s 447ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 887ms

After Hooks.rollbackAddedAuthorities() 156ms

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

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

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

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

And Go to "USERS_TAB" 1s 476ms

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

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

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

Then Save user details 1s 008ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 650ms

After Hooks.rollbackAddedAuthorities() 255ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

Scenario Outline Permission - Edit user notifications from other company [A-7887]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

And Go to "USERS_TAB" 1s 588ms

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

And Expand "GLUE_FACTORY" notification section 521ms

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

Then Save user details 1s 839ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 081ms

After Hooks.rollbackAddedAuthorities() 231ms

	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 27s 244ms	Failed

Tag Report