Cucumber-JVM Reports - Tag: @rollbackAddedAuthorities

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.129	23 sie 2021, 05:13

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

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

And Clear all cache 2s 865ms

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

And Create company "Firma automaty" 6s 559ms

And Edit company "Firma automaty" 2s 777ms

Then Company is successfully edited 643ms

Hooks

After Hooks.deleteCompanyAfterTest() 135ms

After Hooks.rollbackAddedAuthorities() 190ms

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

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

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

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

And Go to "COMPANIES_TAB" 1s 994ms

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

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

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

Hooks

After Hooks.deleteCompanyAfterTest() 134ms

After Hooks.rollbackAddedAuthorities() 157ms

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

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

And Go to "COMPANIES_TAB" 1s 361ms

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

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

And Set existing partnerships 15s 099ms

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

Then Verify that partnership form is visible 131ms

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

When Fill partnership form 1s 605ms

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

When Go to "CARRIER_TAB" 1s 140ms

And Go to details of company in partnership 895ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 18s 004ms

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

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

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

And Go to "COMPANIES_TAB" 1s 726ms

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

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

And Set existing partnerships 15s 085ms

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

Then Verify that partnership form is visible 113ms

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

When Fill partnership form 1s 665ms

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

When Go to "COMPANIES_TAB" 1s 052ms

And Go to details of company in partnership 555ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 965ms

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

Steps

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

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

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

And Go to "COMPANIES_TAB" 1s 070ms

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

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

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

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

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

And Go to "COMPANIES_TAB" 1s 083ms

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

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

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

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

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

When Go to "COMPANIES_TAB" 907ms

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

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

And Set existing partnerships 15s 113ms

When Add all partnership 1s 080ms

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

And Set number of partnerships 032ms

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

When Remove partnership 780ms

Then Check that partnership has been deleted 034ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 809ms

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

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

When Go to "COMPANIES_TAB" 1s 056ms

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

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

And Set existing partnerships 121ms

When Add all partnership 979ms

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

And Set number of partnerships 033ms

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

When Remove partnership 789ms

Then Check that partnership has been deleted 034ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 3s 028ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 293ms

And Select warehouse "Serownia" 1s 558ms

And Set week view 1s 232ms

And Show yesterday 1s 144ms

And Move window into the past 438ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 311ms

After Hooks.deleteTransportAfterTest() 818ms

After Hooks.rollbackAddedAuthorities() 134ms

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

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

And Go to "WAREHOUSE_TAB" 1s 082ms

When Check if pallet limit counter is visible 098ms

And Set limit to "888" 995ms

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

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

And Go to "SETTINGS_TAB" 917ms

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

And Click add authority button 205ms

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

And Click save authority button 250ms

And Expand "ANNOUNCEMENT" panel 1s 048ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 169ms

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

And Go to "SETTINGS_TAB" 941ms

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

And Click add authority button 220ms

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

And Click save authority button 255ms

And Expand "ANNOUNCEMENT" panel 1s 377ms

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

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

And Go to "SETTINGS_TAB" 790ms

When Go to "SALES_EMPLOYEE" authorities settings 949ms

And Click add authority button 207ms

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

And Click save authority button 245ms

And Expand "ANNOUNCEMENT" panel 666ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 137ms

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

And Go to "SETTINGS_TAB" 726ms

When Go to "ANALYST" authorities settings 649ms

And Click add authority button 218ms

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

And Click save authority button 240ms

And Expand "ANNOUNCEMENT" panel 611ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 137ms

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

And Go to "SETTINGS_TAB" 878ms

When Go to "BUYER" authorities settings 792ms

And Click add authority button 211ms

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

And Click save authority button 244ms

And Expand "ANNOUNCEMENT" panel 706ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 170ms

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

And Go to "SETTINGS_TAB" 748ms

When Go to "FORWARDING_AGENT" authorities settings 921ms

And Click add authority button 215ms

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

And Click save authority button 253ms

And Expand "ANNOUNCEMENT" panel 906ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 149ms

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

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

When Go to "TRANSPORT_TABLE" 407ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 362ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 414ms

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

Then Verify that "UNLOAD_TIME_WINDOW" icon is "fa-sort-down" 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 333ms

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

When Go to "TRANSPORT_TABLE" 423ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 494ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 190ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 504ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 238ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 519ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 021ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 492ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 074ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports statuses sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 513ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 655ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports statuses sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 488ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 624ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports statuses sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 529ms

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

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

Error message

java.lang.NullPointerException
	at java.lang.Integer.compareTo(Integer.java:1216)
	at java.lang.Integer.compareTo(Integer.java:52)
	at java.util.Comparator.lambda$comparing$77a9974f$1(Comparator.java:469)
	at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355)
	at java.util.TimSort.sort(TimSort.java:220)
	at java.util.Arrays.sort(Arrays.java:1512)
	at java.util.ArrayList.sort(ArrayList.java:1464)
	at java.util.Collections.sort(Collections.java:177)
	at CucumberTests.Sorting.SortingTest.verifyThatValuesInAreSortedIn(SortingTest.java:73)
	at ✽.Verify that values in "STATUS" are sorted "asc" in "neuca" "DELIVERY"(file:Features/Atom/Sorting/Sorting.feature:45)

Hooks

After Hooks.deleteTransportsAfterTest() 1s 523ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports statuses sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 497ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 686ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports are correctly sorted after switching tabs

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 505ms

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

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

Then Go to "WAREHOUSE_TAB" 991ms

And Go to "TRANSPORT_TABLE" 451ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 600ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 544ms

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

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

Then Go to "WAREHOUSE_TAB" 948ms

And Go to "TRANSPORT_TABLE" 444ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 600ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 513ms

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

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

Then If user is login then logout 261ms

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

And Go to "TRANSPORT_TABLE" 491ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 508ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 470ms

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

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

Then If user is login then logout 500ms

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

And Go to "TRANSPORT_TABLE" 510ms

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

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

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

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

When Go to "WAREHOUSE_TAB" 1s 501ms

And Select warehouse "Serownia" 1s 646ms

And Set week view 1s 272ms

And Show yesterday 1s 157ms

And Move window into the past 405ms

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

Hooks

After Hooks.deleteTransportAfterTest() 837ms

After Hooks.rollbackAddedAuthorities() 190ms

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

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

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

When Go to "WAREHOUSE_TAB" 1s 431ms

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

And Set week view 1s 297ms

And Show yesterday 1s 187ms

And Move window into the past 618ms

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

Hooks

After Hooks.deleteTransportAfterTest() 796ms

After Hooks.rollbackAddedAuthorities() 124ms

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

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

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

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

When Show all transport types 1s 150ms

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

And Set advice window in schedule 3s 601ms

And Fill advice form 13s 031ms

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

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

And Set week view 2s 714ms

And Show yesterday 1s 372ms

And Move window into the past 1s 143ms

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

Hooks

After Hooks.deleteTransportAfterTest() 808ms

After Hooks.rollbackAddedAuthorities() 179ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 710ms

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

And Go to next day in schedule 1s 198ms

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

And Select view "DAYS_2" 2s 183ms

And Move advice window "2" 1s 512ms

And Select view "DAY" 2s 144ms

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

And Delete created transport by API 770ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 653ms

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

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

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

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

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

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

Then Save user details 1s 073ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 642ms

After Hooks.rollbackAddedAuthorities() 247ms

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

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

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

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

And Expand "other" notification section 2s 387ms

And Select all notifications in "other" section 272ms

Then Save user details 1s 520ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 887ms

After Hooks.rollbackAddedAuthorities() 158ms

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

Steps

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

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

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

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

And Go to "USERS_TAB" 1s 551ms

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

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

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

Then Save user details 1s 021ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 637ms

After Hooks.rollbackAddedAuthorities() 240ms

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

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

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

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

And Go to "USERS_TAB" 1s 579ms

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

And Expand "GLUE_FACTORY" notification section 539ms

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

Then Save user details 1s 869ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 080ms

After Hooks.rollbackAddedAuthorities() 238ms

	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 34s 985ms	Failed

Tag Report