Cucumber-JVM Reports - Tag: @rollbackAddedAuthorities

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.137	29 sie 2021, 05:53

	Steps	Scenarios	Features
@rollbackAddedAuthorities	321	5	44	0	0	370	34	6	40	10m 34s 769ms	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" 229ms

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

And Clear all cache 2s 682ms

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

And Create company "Firma automaty" 7s 467ms

And Edit company "Firma automaty" 3s 829ms

Then Company is successfully edited 534ms

Hooks

After Hooks.deleteCompanyAfterTest() 115ms

After Hooks.rollbackAddedAuthorities() 152ms

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

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

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

And Go to "COMPANIES_TAB" 1s 998ms

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

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

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

Hooks

After Hooks.deleteCompanyAfterTest() 129ms

After Hooks.rollbackAddedAuthorities() 141ms

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

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

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

And Go to "COMPANIES_TAB" 1s 409ms

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

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

And Set existing partnerships 15s 104ms

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

Then Verify that partnership form is visible 110ms

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

When Fill partnership form 1s 655ms

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

When Go to "CARRIER_TAB" 961ms

And Go to details of company in partnership 841ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 18s 087ms

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

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

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

And Go to "COMPANIES_TAB" 1s 740ms

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

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

And Set existing partnerships 15s 073ms

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

Then Verify that partnership form is visible 120ms

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

When Fill partnership form 1s 639ms

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

When Go to "COMPANIES_TAB" 1s 147ms

And Go to details of company in partnership 679ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 18s 256ms

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

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

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

And Go to "COMPANIES_TAB" 1s 064ms

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

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

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

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

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

And Go to "COMPANIES_TAB" 1s 031ms

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

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

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

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

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

When Go to "COMPANIES_TAB" 902ms

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

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

And Set existing partnerships 15s 048ms

When Add all partnership 1s 061ms

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

And Set number of partnerships 033ms

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

When Remove partnership 764ms

Then Check that partnership has been deleted 032ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 17s 908ms

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

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

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

When Go to "COMPANIES_TAB" 1s 001ms

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

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

And Set existing partnerships 129ms

When Add all partnership 972ms

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

And Set number of partnerships 032ms

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

When Remove partnership 798ms

Then Check that partnership has been deleted 031ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 3s 129ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 620ms

And Select warehouse "Serownia" 1s 604ms

And Set week view 1s 233ms

And Show yesterday 1s 176ms

And Move window into the past 408ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 519ms

After Hooks.deleteTransportAfterTest() 833ms

After Hooks.rollbackAddedAuthorities() 197ms

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

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

And Go to "WAREHOUSE_TAB" 1s 156ms

When Check if pallet limit counter is visible 081ms

And Set limit to "888" 892ms

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

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

And Go to "SETTINGS_TAB" 879ms

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

And Click add authority button 234ms

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

And Click save authority button 260ms

And Expand "ANNOUNCEMENT" panel 1s 060ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 166ms

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

And Go to "SETTINGS_TAB" 882ms

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

And Click add authority button 218ms

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

And Click save authority button 251ms

And Expand "ANNOUNCEMENT" panel 1s 423ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 150ms

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

And Go to "SETTINGS_TAB" 772ms

When Go to "SALES_EMPLOYEE" authorities settings 702ms

And Click add authority button 209ms

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

And Click save authority button 243ms

And Expand "ANNOUNCEMENT" panel 703ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 176ms

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

And Go to "SETTINGS_TAB" 726ms

When Go to "ANALYST" authorities settings 638ms

And Click add authority button 206ms

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

And Click save authority button 252ms

And Expand "ANNOUNCEMENT" panel 644ms

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

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

Steps

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

And Go to "SETTINGS_TAB" 781ms

When Go to "BUYER" authorities settings 741ms

And Click add authority button 213ms

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

And Click save authority button 272ms

And Expand "ANNOUNCEMENT" panel 779ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 153ms

View Feature Authorities

@rollbackAddedAuthorities @TmsLink=A-7052

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Go to "SETTINGS_TAB" 744ms

When Go to "FORWARDING_AGENT" authorities settings 1s 001ms

And Click add authority button 213ms

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

And Click save authority button 247ms

And Expand "ANNOUNCEMENT" panel 918ms

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

Hooks

After Hooks.rollbackAddedAuthorities() 142ms

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

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

When Go to "TRANSPORT_TABLE" 404ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 377ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 394ms

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

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

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

When Go to "TRANSPORT_TABLE" 349ms

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 454ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 084ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 479ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 137ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 371ms

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

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 466ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 086ms

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 496ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 728ms

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

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 522ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 646ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 513ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 400ms

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania PUT pod adresem /transports/229292645/delete - status odpowiedzi: 500 , komunikat:  [error:org.springframework.orm.hibernate5.HibernateOptimisticLockingFailureException: Object of class [logintegra.process.Transport] with identifier [229292645]: 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#229292645]]
	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" 274ms

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

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

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-28T18: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) 001ms

Steps

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

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

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-28T18: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) 000ms

Steps

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

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 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-28T18: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) 001ms

Steps

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

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 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-28T18: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" 147ms

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

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-28T18: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 001ms

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

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

When Go to "WAREHOUSE_TAB" 1s 261ms

And Select warehouse "Serownia" 1s 584ms

And Set week view 1s 239ms

And Show yesterday 1s 154ms

And Move window into the past 429ms

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

Hooks

After Hooks.deleteTransportAfterTest() 862ms

After Hooks.rollbackAddedAuthorities() 143ms

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

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

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

When Go to "WAREHOUSE_TAB" 1s 324ms

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

And Set week view 1s 259ms

And Show yesterday 1s 163ms

And Move window into the past 618ms

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

Hooks

After Hooks.deleteTransportAfterTest() 815ms

After Hooks.rollbackAddedAuthorities() 196ms

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

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

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

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

When Show all transport types 1s 128ms

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

And Set advice window in schedule 3s 306ms

And Fill advice form 12s 984ms

And Click advice save button and wait for advice form to disappear 18s 474ms

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

And Set week view 2s 412ms

And Show yesterday 1s 210ms

And Move window into the past 1s 102ms

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

Hooks

After Hooks.deleteTransportAfterTest() 888ms

After Hooks.rollbackAddedAuthorities() 152ms

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

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 2s 068ms

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

And Go to "WAREHOUSE_TAB" 716ms

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

And Go to next day in schedule 1s 189ms

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

And Select view "DAYS_2" 2s 153ms

And Move advice window "2" 1s 518ms

And Select view "DAY" 2s 151ms

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

And Delete created transport by API 821ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 637ms

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

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

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

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

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

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

Then Save user details 1s 064ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 644ms

After Hooks.rollbackAddedAuthorities() 290ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

Scenario Outline Permission - Edit user notifications [A-7887]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

And Expand "other" notification section 2s 427ms

And Select all notifications in "other" section 295ms

Then Save user details 1s 420ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 887ms

After Hooks.rollbackAddedAuthorities() 150ms

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

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

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

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

And Go to "USERS_TAB" 1s 563ms

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

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

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

Then Save user details 1s 005ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 646ms

After Hooks.rollbackAddedAuthorities() 230ms

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

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

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

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

And Go to "USERS_TAB" 1s 542ms

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

And Expand "GLUE_FACTORY" notification section 628ms

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

Then Save user details 1s 824ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 040ms

After Hooks.rollbackAddedAuthorities() 245ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@rollbackAddedAuthorities	321	5	44	0	0	370	34	6	40	10m 34s 769ms	Failed

Tag Report