Cucumber-JVM Reports - Tag: @rollbackAddedAuthorities

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.132	25 sie 2021, 05:54

	Steps	Scenarios	Features
@rollbackAddedAuthorities	369	1	0	0	0	370	39	1	40	11m 43s 897ms	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" 249ms

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

And Clear all cache 2s 920ms

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

And Create company "Firma automaty" 7s 522ms

And Edit company "Firma automaty" 3s 784ms

Then Company is successfully edited 536ms

Hooks

After Hooks.deleteCompanyAfterTest() 128ms

After Hooks.rollbackAddedAuthorities() 184ms

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

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

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

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

And Go to "COMPANIES_TAB" 1s 982ms

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

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

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

Hooks

After Hooks.deleteCompanyAfterTest() 121ms

After Hooks.rollbackAddedAuthorities() 139ms

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

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

And Login as "adama-admin" 6s 143ms

And Go to "COMPANIES_TAB" 1s 412ms

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

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

And Set existing partnerships 15s 080ms

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

Then Verify that partnership form is visible 128ms

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

When Fill partnership form 1s 648ms

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

When Go to "CARRIER_TAB" 1s 138ms

And Go to details of company in partnership 963ms

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

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

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

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

And Go to "COMPANIES_TAB" 1s 684ms

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

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

And Set existing partnerships 15s 066ms

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

Then Verify that partnership form is visible 088ms

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

When Fill partnership form 1s 617ms

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

When Go to "COMPANIES_TAB" 1s 147ms

And Go to details of company in partnership 559ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 18s 284ms

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

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

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

And Go to "COMPANIES_TAB" 1s 030ms

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

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

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

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

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

And Go to "COMPANIES_TAB" 1s 025ms

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

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

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

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

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

When Go to "COMPANIES_TAB" 952ms

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

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

And Set existing partnerships 15s 102ms

When Add all partnership 1s 085ms

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

And Set number of partnerships 035ms

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

When Remove partnership 786ms

Then Check that partnership has been deleted 033ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 893ms

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

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

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

When Go to "COMPANIES_TAB" 1s 056ms

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

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

And Set existing partnerships 121ms

When Add all partnership 965ms

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

And Set number of partnerships 033ms

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

When Remove partnership 800ms

Then Check that partnership has been deleted 032ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 3s 079ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 671ms

And Select warehouse "Serownia" 1s 619ms

And Set week view 1s 234ms

And Show yesterday 1s 158ms

And Move window into the past 397ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 528ms

After Hooks.deleteTransportAfterTest() 796ms

After Hooks.rollbackAddedAuthorities() 140ms

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

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

And Go to "WAREHOUSE_TAB" 1s 113ms

When Check if pallet limit counter is visible 073ms

And Set limit to "888" 886ms

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

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

And Go to "SETTINGS_TAB" 847ms

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

And Click add authority button 208ms

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

And Click save authority button 258ms

And Expand "ANNOUNCEMENT" panel 1s 162ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 156ms

View Feature Authorities

@rollbackAddedAuthorities @TmsLink=A-7052

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Go to "SETTINGS_TAB" 895ms

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

And Click add authority button 213ms

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

And Click save authority button 261ms

And Expand "ANNOUNCEMENT" panel 1s 375ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 139ms

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

And Go to "SETTINGS_TAB" 775ms

When Go to "SALES_EMPLOYEE" authorities settings 780ms

And Click add authority button 222ms

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

And Click save authority button 252ms

And Expand "ANNOUNCEMENT" panel 695ms

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

And Go to "SETTINGS_TAB" 737ms

When Go to "ANALYST" authorities settings 662ms

And Click add authority button 217ms

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

And Click save authority button 252ms

And Expand "ANNOUNCEMENT" panel 863ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 162ms

View Feature Authorities

@rollbackAddedAuthorities @TmsLink=A-7052

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-adama" and set token of apiUsername "super-admin-adama" 5s 441ms

And Go to "SETTINGS_TAB" 810ms

When Go to "BUYER" authorities settings 777ms

And Click add authority button 240ms

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

And Click save authority button 253ms

And Expand "ANNOUNCEMENT" panel 738ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 153ms

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

And Go to "SETTINGS_TAB" 750ms

When Go to "FORWARDING_AGENT" authorities settings 922ms

And Click add authority button 230ms

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

And Click save authority button 240ms

And Expand "ANNOUNCEMENT" panel 917ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 145ms

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

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

When Go to "TRANSPORT_TABLE" 414ms

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

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

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

When Go to "TRANSPORT_TABLE" 384ms

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

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

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

When Go to "TRANSPORT_TABLE" 351ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 330ms

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

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports time window dates sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 506ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 106ms

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

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 1s 932ms

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

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

When Go to "TRANSPORT_TABLE" 521ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 066ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 506ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 062ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 505ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 037ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 595ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 549ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 489ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 738ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 511ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 632ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 495ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 704ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 533ms

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

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

Then Go to "WAREHOUSE_TAB" 1s 007ms

And Go to "TRANSPORT_TABLE" 442ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 510ms

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 502ms

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

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

Then Go to "WAREHOUSE_TAB" 944ms

And Go to "TRANSPORT_TABLE" 464ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 605ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 520ms

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

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

Then If user is login then logout 256ms

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

And Go to "TRANSPORT_TABLE" 467ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 619ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 488ms

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

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

Then If user is login then logout 242ms

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

And Go to "TRANSPORT_TABLE" 481ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 623ms

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

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

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

When Go to "WAREHOUSE_TAB" 1s 305ms

And Select warehouse "Serownia" 1s 582ms

And Set week view 1s 242ms

And Show yesterday 1s 129ms

And Move window into the past 402ms

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

Hooks

After Hooks.deleteTransportAfterTest() 840ms

After Hooks.rollbackAddedAuthorities() 195ms

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

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

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

When Go to "WAREHOUSE_TAB" 1s 331ms

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

And Set week view 1s 306ms

And Show yesterday 1s 179ms

And Move window into the past 653ms

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

Hooks

After Hooks.deleteTransportAfterTest() 880ms

After Hooks.rollbackAddedAuthorities() 143ms

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

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

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

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

And Set advice window in schedule 3s 445ms

And Fill advice form 13s 065ms

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

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

And Set week view 2s 443ms

And Show yesterday 1s 276ms

And Move window into the past 1s 064ms

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

Error message

java.lang.AssertionError
	at org.junit.Assert.fail(Assert.java:86)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at org.junit.Assert.assertTrue(Assert.java:52)
	at CucumberTests.Schedule.ScheduleTest.checkIfWindowIs(ScheduleTest.java:58)
	at ✽.Check if window is "red"(file:Features/Atom/TimeWindow/TransportWindow.feature:35)

Hooks

After Hooks.deleteTransportAfterTest() 777ms

After Hooks.rollbackAddedAuthorities() 144ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 747ms

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

And Go to next day in schedule 1s 203ms

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

And Select view "DAYS_2" 2s 179ms

And Move advice window "2" 1s 521ms

And Select view "DAY" 2s 159ms

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

And Delete created transport by API 790ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 661ms

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

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

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

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

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

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

Then Save user details 1s 059ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 653ms

After Hooks.rollbackAddedAuthorities() 243ms

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

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

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

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

And Expand "other" notification section 2s 388ms

And Select all notifications in "other" section 274ms

Then Save user details 1s 480ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s

After Hooks.rollbackAddedAuthorities() 163ms

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

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

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

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

And Go to "USERS_TAB" 1s 557ms

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

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

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

Then Save user details 1s 031ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 671ms

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

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

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

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

And Go to "USERS_TAB" 1s 547ms

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

And Expand "GLUE_FACTORY" notification section 529ms

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

Then Save user details 1s 852ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 030ms

After Hooks.rollbackAddedAuthorities() 234ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@rollbackAddedAuthorities	369	1	0	0	0	370	39	1	40	11m 43s 897ms	Failed

Tag Report