Cucumber-JVM Reports - Tag: @rollbackAddedAuthorities

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.139	31 sie 2021, 05:52

	Steps	Scenarios	Features
@rollbackAddedAuthorities	307	7	56	0	0	370	32	8	40	10m 8s 267ms	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" 262ms

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

And Clear all cache 2s 889ms

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

And Create company "Firma automaty" 7s 443ms

And Edit company "Firma automaty" 3s 801ms

Then Company is successfully edited 542ms

Hooks

After Hooks.deleteCompanyAfterTest() 227ms

After Hooks.rollbackAddedAuthorities() 164ms

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

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

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

And Go to "COMPANIES_TAB" 1s 881ms

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

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

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

Hooks

After Hooks.deleteCompanyAfterTest() 111ms

After Hooks.rollbackAddedAuthorities() 132ms

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

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

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

And Go to "COMPANIES_TAB" 1s 422ms

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

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

And Set existing partnerships 15s 095ms

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

Then Verify that partnership form is visible 117ms

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

When Fill partnership form 1s 637ms

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

When Go to "CARRIER_TAB" 1s 044ms

And Go to details of company in partnership 902ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 18s 230ms

View Feature Company

@removeAllAddedPartnership @rollbackAddedAuthorities

Scenario Outline Check if admin can manage partnership of supplier with carrier in contractor's details - adding partnership [A-7386]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Go to "COMPANIES_TAB" 1s 743ms

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

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

And Set existing partnerships 15s 062ms

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

Then Verify that partnership form is visible 118ms

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

When Fill partnership form 1s 637ms

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

When Go to "COMPANIES_TAB" 1s 063ms

And Go to details of company in partnership 562ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 882ms

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

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

And Go to "COMPANIES_TAB" 1s 121ms

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

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

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

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

And Login as "super-admin-neuca" 10s 002ms

And Go to "COMPANIES_TAB" 1s 005ms

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

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Company

@removeAllAddedPartnership @rollbackAddedAuthorities

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

When Go to "COMPANIES_TAB" 910ms

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

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

And Set existing partnerships 15s 078ms

When Add all partnership 1s 017ms

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

And Set number of partnerships 036ms

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

When Remove partnership 1s 332ms

Then Check that partnership has been deleted 034ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 895ms

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

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

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

When Go to "COMPANIES_TAB" 1s 189ms

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

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

And Set existing partnerships 124ms

When Add all partnership 976ms

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

And Set number of partnerships 034ms

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

When Remove partnership 796ms

Then Check that partnership has been deleted 036ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 3s 010ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 301ms

And Select warehouse "Serownia" 1s 569ms

And Set week view 1s 241ms

And Show yesterday 1s 170ms

And Move window into the past 455ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 578ms

After Hooks.deleteTransportAfterTest() 774ms

After Hooks.rollbackAddedAuthorities() 198ms

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

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

And Go to "WAREHOUSE_TAB" 1s 158ms

When Check if pallet limit counter is visible 082ms

And Set limit to "888" 921ms

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

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

Steps

Given Login as "super-admin-skz" and set token of apiUsername "super-admin-skz" 9s 455ms

And Go to "SETTINGS_TAB" 859ms

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

And Click add authority button 224ms

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

And Click save authority button 253ms

And Expand "ANNOUNCEMENT" panel 1s 074ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 159ms

View Feature Authorities

@rollbackAddedAuthorities @TmsLink=A-7052

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Go to "SETTINGS_TAB" 897ms

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

And Click add authority button 216ms

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

And Click save authority button 259ms

And Expand "ANNOUNCEMENT" panel 1s 363ms

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

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

And Go to "SETTINGS_TAB" 733ms

When Go to "SALES_EMPLOYEE" authorities settings 732ms

And Click add authority button 222ms

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

And Click save authority button 258ms

And Expand "ANNOUNCEMENT" panel 739ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 178ms

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

And Go to "SETTINGS_TAB" 708ms

When Go to "ANALYST" authorities settings 619ms

And Click add authority button 214ms

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

And Click save authority button 244ms

And Expand "ANNOUNCEMENT" panel 640ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 161ms

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

And Go to "SETTINGS_TAB" 732ms

When Go to "BUYER" authorities settings 767ms

And Click add authority button 205ms

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

And Click save authority button 258ms

And Expand "ANNOUNCEMENT" panel 813ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 181ms

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

Steps

Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 6s 228ms

And Go to "SETTINGS_TAB" 705ms

When Go to "FORWARDING_AGENT" authorities settings 922ms

And Click add authority button 201ms

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

And Click save authority button 264ms

And Expand "ANNOUNCEMENT" panel 902ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 158ms

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

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

When Go to "TRANSPORT_TABLE" 400ms

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

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

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

When Go to "TRANSPORT_TABLE" 364ms

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

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities

Scenario Outline Check if icons change correctly

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

When Go to "TRANSPORT_TABLE" 363ms

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

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

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

When Go to "TRANSPORT_TABLE" 420ms

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

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 482ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 073ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 466ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 094ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 553ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 046ms

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

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

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

When Go to "TRANSPORT_TABLE" 475ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 078ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 501ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 055ms

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania PUT pod adresem /transports/229536188/delete - status odpowiedzi: 500 , komunikat:  [error:org.springframework.orm.hibernate5.HibernateOptimisticLockingFailureException: Object of class [logintegra.process.Transport] with identifier [229536188]: optimistic locking failed; nested exception is org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect) : [logintegra.process.Transport#229536188]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.putResponse(RestUtil.java:317)
	at Utils.RestUtils.RestUtil.putToApolloApi(RestUtil.java:110)
	at CucumberTests.Hooks.deleteTransportsAfterTest(Hooks.java:216)
	at CucumberTests.Hooks.deleteTransportsAfterTest(Hooks.java:203)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at cucumber.runtime.Utils$1.call(Utils.java:26)
	at cucumber.runtime.Timeout.timeout(Timeout.java:16)
	at cucumber.runtime.Utils.invoke(Utils.java:20)
	at cucumber.runtime.java.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	at cucumber.runner.Runner.runPickle(Runner.java:40)
	at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)

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

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

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /transports; status: 422, komunikat: [errors:[[meta:[exceptionType:WINDOWS_OVERLAP_EXCEPTION, initialStart:2021-08-30T18:00:00Z, windowSizeInMinutes:45, rampName:Katowice - R6], detail:Nie możemy zarezerwować okna czasowego o długości 45 minut we wskazanym miejscu, ponieważ magazyn jest już zajęty w tych godzinach. Prosimy o wybranie innej godziny lub rampy., title:WindowsOverlapException, status:[enumType:org.springframework.http.HttpStatus, name:UNPROCESSABLE_ENTITY]]]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Transport.CreateTransport.createByJSONFileAs(CreateTransport.java:87)
	at CucumberTests.Transport.CreateTransport.createByJSONFileAsInDays(CreateTransport.java:79)
	at ✽.Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "0" days(file:Features/Atom/Sorting/Sorting.feature:39)

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 000ms

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

And Login as "neuca-admin" 000ms

When Go to "TRANSPORT_TABLE" 000ms

And Click button "STATUS" "2" times 000ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 000ms

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

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

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

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /transports; status: 422, komunikat: [errors:[[meta:[exceptionType:WINDOWS_OVERLAP_EXCEPTION, initialStart:2021-08-30T18:00:00Z, windowSizeInMinutes:45, rampName:Katowice - R6], detail:Nie możemy zarezerwować okna czasowego o długości 45 minut we wskazanym miejscu, ponieważ magazyn jest już zajęty w tych godzinach. Prosimy o wybranie innej godziny lub rampy., title:WindowsOverlapException, status:[enumType:org.springframework.http.HttpStatus, name:UNPROCESSABLE_ENTITY]]]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Transport.CreateTransport.createByJSONFileAs(CreateTransport.java:87)
	at CucumberTests.Transport.CreateTransport.createByJSONFileAsInDays(CreateTransport.java:79)
	at ✽.Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "0" days(file:Features/Atom/Sorting/Sorting.feature:39)

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 000ms

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

And Login as "neuca-admin" 000ms

When Go to "TRANSPORT_TABLE" 000ms

And Click button "STATUS" "3" times 000ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 000ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports statuses sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /transports; status: 422, komunikat: [errors:[[meta:[exceptionType:WINDOWS_OVERLAP_EXCEPTION, initialStart:2021-08-30T18:00:00Z, windowSizeInMinutes:45, rampName:Katowice - R6], detail:Nie możemy zarezerwować okna czasowego o długości 45 minut we wskazanym miejscu, ponieważ magazyn jest już zajęty w tych godzinach. Prosimy o wybranie innej godziny lub rampy., title:WindowsOverlapException, status:[enumType:org.springframework.http.HttpStatus, name:UNPROCESSABLE_ENTITY]]]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Transport.CreateTransport.createByJSONFileAs(CreateTransport.java:87)
	at CucumberTests.Transport.CreateTransport.createByJSONFileAsInDays(CreateTransport.java:79)
	at ✽.Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "0" days(file:Features/Atom/Sorting/Sorting.feature:39)

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 000ms

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

And Login as "neuca-admin" 000ms

When Go to "TRANSPORT_TABLE" 000ms

And Click button "STATUS" "2" times 000ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 000ms

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

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

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /transports; status: 422, komunikat: [errors:[[meta:[exceptionType:WINDOWS_OVERLAP_EXCEPTION, initialStart:2021-08-30T18:00:00Z, windowSizeInMinutes:45, rampName:Katowice - R6], detail:Nie możemy zarezerwować okna czasowego o długości 45 minut we wskazanym miejscu, ponieważ magazyn jest już zajęty w tych godzinach. Prosimy o wybranie innej godziny lub rampy., title:WindowsOverlapException, status:[enumType:org.springframework.http.HttpStatus, name:UNPROCESSABLE_ENTITY]]]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Transport.CreateTransport.createByJSONFileAs(CreateTransport.java:87)
	at CucumberTests.Transport.CreateTransport.createByJSONFileAsInDays(CreateTransport.java:79)
	at ✽.Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "0" days(file:Features/Atom/Sorting/Sorting.feature:58)

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 000ms

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

And Login as "neuca-admin" 000ms

When Go to "TRANSPORT_TABLE" 000ms

And Click button "STATUS" "1" times 000ms

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

Then Go to "WAREHOUSE_TAB" 000ms

And Go to "TRANSPORT_TABLE" 000ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 000ms

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

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

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

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /transports; status: 422, komunikat: [errors:[[meta:[exceptionType:WINDOWS_OVERLAP_EXCEPTION, initialStart:2021-08-30T18:00:00Z, windowSizeInMinutes:45, rampName:Katowice - R6], detail:Nie możemy zarezerwować okna czasowego o długości 45 minut we wskazanym miejscu, ponieważ magazyn jest już zajęty w tych godzinach. Prosimy o wybranie innej godziny lub rampy., title:WindowsOverlapException, status:[enumType:org.springframework.http.HttpStatus, name:UNPROCESSABLE_ENTITY]]]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Transport.CreateTransport.createByJSONFileAs(CreateTransport.java:87)
	at CucumberTests.Transport.CreateTransport.createByJSONFileAsInDays(CreateTransport.java:79)
	at ✽.Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "0" days(file:Features/Atom/Sorting/Sorting.feature:58)

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 000ms

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

And Login as "neuca-admin" 000ms

When Go to "TRANSPORT_TABLE" 000ms

And Click button "STATUS" "2" times 000ms

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

Then Go to "WAREHOUSE_TAB" 000ms

And Go to "TRANSPORT_TABLE" 000ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 000ms

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

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

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

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /transports; status: 422, komunikat: [errors:[[meta:[exceptionType:WINDOWS_OVERLAP_EXCEPTION, initialStart:2021-08-30T18:00:00Z, windowSizeInMinutes:45, rampName:Katowice - R6], detail:Nie możemy zarezerwować okna czasowego o długości 45 minut we wskazanym miejscu, ponieważ magazyn jest już zajęty w tych godzinach. Prosimy o wybranie innej godziny lub rampy., title:WindowsOverlapException, status:[enumType:org.springframework.http.HttpStatus, name:UNPROCESSABLE_ENTITY]]]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Transport.CreateTransport.createByJSONFileAs(CreateTransport.java:87)
	at CucumberTests.Transport.CreateTransport.createByJSONFileAsInDays(CreateTransport.java:79)
	at ✽.Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "0" days(file:Features/Atom/Sorting/Sorting.feature:77)

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 000ms

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

And Login as "neuca-admin" 000ms

When Go to "TRANSPORT_TABLE" 000ms

And Click button "STATUS" "1" times 000ms

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

Then If user is login then logout 000ms

And Login as "neuca-admin" 000ms

And Go to "TRANSPORT_TABLE" 000ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 000ms

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

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

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

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /transports; status: 422, komunikat: [errors:[[meta:[exceptionType:WINDOWS_OVERLAP_EXCEPTION, initialStart:2021-08-30T18:00:00Z, windowSizeInMinutes:45, rampName:Katowice - R6], detail:Nie możemy zarezerwować okna czasowego o długości 45 minut we wskazanym miejscu, ponieważ magazyn jest już zajęty w tych godzinach. Prosimy o wybranie innej godziny lub rampy., title:WindowsOverlapException, status:[enumType:org.springframework.http.HttpStatus, name:UNPROCESSABLE_ENTITY]]]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Transport.CreateTransport.createByJSONFileAs(CreateTransport.java:87)
	at CucumberTests.Transport.CreateTransport.createByJSONFileAsInDays(CreateTransport.java:79)
	at ✽.Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "0" days(file:Features/Atom/Sorting/Sorting.feature:77)

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 000ms

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

And Login as "neuca-admin" 000ms

When Go to "TRANSPORT_TABLE" 000ms

And Click button "STATUS" "2" times 000ms

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

Then If user is login then logout 000ms

And Login as "neuca-admin" 000ms

And Go to "TRANSPORT_TABLE" 000ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 000ms

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

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

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

When Go to "WAREHOUSE_TAB" 1s 297ms

And Select warehouse "Serownia" 1s 562ms

And Set week view 1s 247ms

And Show yesterday 1s 157ms

And Move window into the past 384ms

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

Hooks

After Hooks.deleteTransportAfterTest() 947ms

After Hooks.rollbackAddedAuthorities() 141ms

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

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

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

When Go to "WAREHOUSE_TAB" 1s 415ms

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

And Set week view 1s 252ms

And Show yesterday 1s 162ms

And Move window into the past 596ms

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

Hooks

After Hooks.deleteTransportAfterTest() 797ms

After Hooks.rollbackAddedAuthorities() 144ms

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

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 985ms

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

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

And Set advice window in schedule 3s 371ms

And Fill advice form 12s 941ms

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

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

And Set week view 2s 310ms

And Show yesterday 1s 233ms

And Move window into the past 892ms

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

Hooks

After Hooks.deleteTransportAfterTest() 860ms

After Hooks.rollbackAddedAuthorities() 141ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if window counter value in schedule changes

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 3s 151ms

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

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

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

And Go to "WAREHOUSE_TAB" 743ms

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

And Go to next day in schedule 1s 180ms

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

And Select view "DAYS_2" 2s 176ms

And Move advice window "2" 1s 492ms

And Select view "DAY" 2s 145ms

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

And Delete created transport by API 813ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 636ms

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

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

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

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

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

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

Then Save user details 1s 008ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 644ms

After Hooks.rollbackAddedAuthorities() 260ms

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

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

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

And Expand "other" notification section 2s 444ms

And Select all notifications in "other" section 269ms

Then Save user details 1s 467ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 141ms

After Hooks.rollbackAddedAuthorities() 181ms

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

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

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

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

And Go to "USERS_TAB" 1s 452ms

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

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

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

Then Save user details 1s 009ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 675ms

After Hooks.rollbackAddedAuthorities() 245ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

And Go to "USERS_TAB" 1s 864ms

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

And Expand "GLUE_FACTORY" notification section 632ms

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

Then Save user details 1s 823ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 007ms

After Hooks.rollbackAddedAuthorities() 215ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@rollbackAddedAuthorities	307	7	56	0	0	370	32	8	40	10m 8s 267ms	Failed

Tag Report