Cucumber-JVM Reports - Tag: @rollbackAddedAuthorities

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.143	03 wrz 2021, 07:47

	Steps	Scenarios	Features
@rollbackAddedAuthorities	366	1	3	0	0	370	39	1	40	12m 309ms	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" 238ms

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

And Clear all cache 2s 674ms

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

And Create company "Firma automaty" 7s 578ms

And Edit company "Firma automaty" 3s 813ms

Then Company is successfully edited 589ms

Hooks

After Hooks.deleteCompanyAfterTest() 104ms

After Hooks.rollbackAddedAuthorities() 166ms

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

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

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

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

And Go to "COMPANIES_TAB" 1s 955ms

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

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

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

Hooks

After Hooks.deleteCompanyAfterTest() 142ms

After Hooks.rollbackAddedAuthorities() 147ms

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

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

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

And Go to "COMPANIES_TAB" 1s 373ms

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

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

And Set existing partnerships 15s 068ms

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

Then Verify that partnership form is visible 108ms

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

When Fill partnership form 1s 663ms

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

When Go to "CARRIER_TAB" 995ms

And Go to details of company in partnership 779ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 952ms

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

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

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

And Go to "COMPANIES_TAB" 1s 712ms

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

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

And Set existing partnerships 15s 104ms

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

Then Verify that partnership form is visible 122ms

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

When Fill partnership form 1s 639ms

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

When Go to "COMPANIES_TAB" 1s 104ms

And Go to details of company in partnership 647ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 18s 020ms

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 "neuca-admin" 144ms

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

And Go to "COMPANIES_TAB" 1s 002ms

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

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

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

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

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

And Go to "COMPANIES_TAB" 1s 055ms

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

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

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

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

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

When Go to "COMPANIES_TAB" 927ms

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

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

And Set existing partnerships 15s 115ms

When Add all partnership 1s 035ms

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

And Set number of partnerships 034ms

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

When Remove partnership 765ms

Then Check that partnership has been deleted 032ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 18s 035ms

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

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

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

When Go to "COMPANIES_TAB" 1s 056ms

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

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

And Set existing partnerships 161ms

When Add all partnership 1s 035ms

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

And Set number of partnerships 031ms

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

When Remove partnership 769ms

Then Check that partnership has been deleted 033ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 3s 128ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 649ms

And Select warehouse "Serownia" 1s 591ms

And Set week view 1s 240ms

And Show yesterday 1s 140ms

And Move window into the past 406ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "spóźnił się na" 1m 4s 512ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 532ms

After Hooks.deleteTransportAfterTest() 821ms

After Hooks.rollbackAddedAuthorities() 142ms

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

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

And Go to "WAREHOUSE_TAB" 1s 118ms

When Check if pallet limit counter is visible 094ms

And Set limit to "888" 972ms

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

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

And Go to "SETTINGS_TAB" 912ms

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

And Click add authority button 207ms

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

And Click save authority button 239ms

And Expand "ANNOUNCEMENT" panel 1s 064ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 179ms

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

And Go to "SETTINGS_TAB" 899ms

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

And Click add authority button 218ms

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

And Click save authority button 248ms

And Expand "ANNOUNCEMENT" panel 1s 359ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 144ms

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

And Go to "SETTINGS_TAB" 787ms

When Go to "SALES_EMPLOYEE" authorities settings 769ms

And Click add authority button 219ms

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

And Click save authority button 244ms

And Expand "ANNOUNCEMENT" panel 717ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 146ms

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

And Go to "SETTINGS_TAB" 731ms

When Go to "ANALYST" authorities settings 650ms

And Click add authority button 211ms

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

And Click save authority button 251ms

And Expand "ANNOUNCEMENT" panel 601ms

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

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

And Go to "SETTINGS_TAB" 778ms

When Go to "BUYER" authorities settings 785ms

And Click add authority button 207ms

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

And Click save authority button 242ms

And Expand "ANNOUNCEMENT" panel 740ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 148ms

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

And Go to "SETTINGS_TAB" 746ms

When Go to "FORWARDING_AGENT" authorities settings 905ms

And Click add authority button 204ms

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

And Click save authority button 261ms

And Expand "ANNOUNCEMENT" panel 886ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 141ms

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

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

When Go to "TRANSPORT_TABLE" 361ms

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

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

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

When Go to "TRANSPORT_TABLE" 370ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 348ms

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

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

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

When Go to "TRANSPORT_TABLE" 394ms

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

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

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

Steps

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 491ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 086ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 470ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 100ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 491ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 083ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports time window dates sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

When Go to "TRANSPORT_TABLE" 518ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 032ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports statuses sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 475ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 639ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 523ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 613ms

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 499ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 576ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 496ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 613ms

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

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

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

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

And Login as "neuca-admin" 1s 986ms

When Go to "TRANSPORT_TABLE" 467ms

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

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

Then Go to "WAREHOUSE_TAB" 936ms

And Go to "TRANSPORT_TABLE" 429ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 580ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports are correctly sorted after switching tabs

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 498ms

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

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

Then Go to "WAREHOUSE_TAB" 955ms

And Go to "TRANSPORT_TABLE" 451ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 562ms

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

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 2s 984ms

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

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

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

When Go to "TRANSPORT_TABLE" 484ms

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

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

Then If user is login then logout 256ms

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

And Go to "TRANSPORT_TABLE" 476ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 560ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 521ms

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

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

Then If user is login then logout 242ms

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

And Go to "TRANSPORT_TABLE" 483ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 613ms

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

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

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

When Go to "WAREHOUSE_TAB" 1s 360ms

And Select warehouse "Serownia" 1s 575ms

And Set week view 1s 258ms

And Show yesterday 1s 167ms

And Move window into the past 420ms

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

Hooks

After Hooks.deleteTransportAfterTest() 817ms

After Hooks.rollbackAddedAuthorities() 129ms

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

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

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

When Go to "WAREHOUSE_TAB" 1s 514ms

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

And Set week view 1s 276ms

And Show yesterday 1s 171ms

And Move window into the past 597ms

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

Hooks

After Hooks.deleteTransportAfterTest() 860ms

After Hooks.rollbackAddedAuthorities() 134ms

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

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

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

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

When Show all transport types 1s 142ms

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

And Set advice window in schedule 3s 361ms

And Fill advice form 13s 003ms

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

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

And Set week view 16s 199ms

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.setWeekView(ScheduleTest.java:45)
	at ✽.Set week view(file:Features/Atom/TimeWindow/TransportWindow.feature:32)

And Show yesterday 000ms

And Move window into the past 000ms

Then Check if window is "red" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 777ms

After Hooks.rollbackAddedAuthorities() 148ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 782ms

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

And Go to next day in schedule 1s 219ms

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

And Select view "DAYS_2" 2s 168ms

And Move advice window "2" 1s 480ms

And Select view "DAY" 2s 151ms

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

And Delete created transport by API 799ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 704ms

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

Steps

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

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

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

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

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

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

Then Save user details 1s 032ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 646ms

After Hooks.rollbackAddedAuthorities() 239ms

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

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

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

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

And Expand "other" notification section 2s 490ms

And Select all notifications in "other" section 279ms

Then Save user details 1s 533ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 859ms

After Hooks.rollbackAddedAuthorities() 154ms

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

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

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

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

And Go to "USERS_TAB" 1s 584ms

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

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

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

Then Save user details 1s 051ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 657ms

After Hooks.rollbackAddedAuthorities() 228ms

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

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

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

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

And Go to "USERS_TAB" 1s 550ms

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

And Expand "GLUE_FACTORY" notification section 593ms

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

Then Save user details 1s 809ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 067ms

After Hooks.rollbackAddedAuthorities() 247ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@rollbackAddedAuthorities	366	1	3	0	0	370	39	1	40	12m 309ms	Failed

Tag Report