Project Number Date
ApolloFullRunnerReport 2021.AT1.68 21 sie 2021, 05:16

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@cleanUserDetailsAfterTest 417 3 18 0 0 438 42 3 45 43m 10s 555ms Failed
View Feature Invitation
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 105ms
And Delete invitations with email "automaty31415@test.pl" 015ms
Then Create invitation by JSON file "super-admin-alrec" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 755ms
And Prepare user "piast-admin" details with all notifications and "automaty31415@test.pl" by JSON file 229ms
When Login as "piast-admin" 1s 345ms
Then Go to "INVITATIONS_TAB" 171ms
And Go to invitation details 065ms
Then Reject invitation by button as user 108ms
When If user is login then logout 273ms
Then Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 1s 391ms
And Go to "INVITATIONS_TAB" 185ms
And Go to "REJECTED_TAB" invitation status tab 080ms
Then Invitation is displayed on list "automaty31415@test.pl" 148ms
After Hooks.deleteInvitationAfterTest() 021ms
After Hooks.cleanUserDetailsAfterTest() 180ms
View Feature Invitation
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-alrec" 094ms
And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "automatyy3333@test.pl" by JSON file 204ms
When Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 971ms
And Go to "INVITATIONS_TAB" 176ms
And Create invitation for "existing" user "SUPPLIER" "SUPPLIER" "automatyy3333@test.pl" "PL" 1s 154ms
And Wait "3" seconds 3s
Then Create invitation success alert is displayed 035ms
After Hooks.deleteInvitationAfterTest() 027ms
After Hooks.cleanUserDetailsAfterTest() 223ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 030ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 170ms
And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 211ms
And Set "advice" inputs from JSON file "ADVICE_CONTAINER" "super-admin-adama" 001ms
And Show all transport types 1s 038ms
And Click button advice in transport table "CONTAINER" 105ms
And Set advice window in schedule 2s 459ms
And Fill advice form 13s 927ms
And Click advice save button and wait for advice form to disappear 30s 711ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!" 5s 577ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 118ms
After Hooks.cleanUserDetailsAfterTest() 183ms
View Feature Advice Mail
Scenario Outline Check if mail was sent to creator after creating advice
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 254ms
And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 135ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 215ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 001ms
And Show all transport types 1s 037ms
And Click button advice in transport table "DELIVERY" 108ms
And Set advice window in schedule 2s 721ms
And Fill advice form 10s 516ms
And Click advice save button and wait for advice form to disappear 10s 190ms
org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='save'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.2KxY4c}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 27f8686fbbe216e38127d63861020cbd
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:217)
	at Pages.Transport.AdviceFormPage.confirm(AdviceFormPage.java:27)
	at CucumberTests.Transport.AdviceTransport.clickAdviceSaveButtonAndWaitForAdviceFormToDisappear(AdviceTransport.java:179)
	at ✽.Click advice save button and wait for advice form to disappear(file:Features/Atom/Mail/AdviceMail.feature:13)
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!" 000ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 066ms
After Hooks.cleanUserDetailsAfterTest() 151ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 181ms
And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 274ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 207ms
And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-keeeper" 001ms
And Show all transport types 1s 043ms
And Click button advice in transport table "LOAD" 093ms
And Set advice window in schedule 2s 462ms
And Fill advice form 15s 386ms
And Click advice save button and wait for advice form to disappear 30s 739ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Time window has been saved!" 5s 481ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 139ms
After Hooks.cleanUserDetailsAfterTest() 237ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 490ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 233ms
And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 193ms
And Show all transport types 1s 040ms
And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-adama" 560ms
And Go to "TRANSPORT_TABLE" 114ms
And Go to transport details "CONTAINER" 2s 460ms
And Set "transport" inputs from JSON file "EDIT_CONTAINER" "super-admin-adama" 001ms
When Go to transport details "CONTAINER" 3s 168ms
And Fill transport form 4s 700ms
And Set "advice" inputs from JSON file "EDIT_ADVICE_CONTAINER" "super-admin-adama" 001ms
And Expand advice panel 112ms
And Edit advice in transport details 14s 644ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 097ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 5s 460ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 100ms
After Hooks.cleanUserDetailsAfterTest() 168ms
View Feature Advice Mail
Scenario Outline Check if mail was sent to creator after editing advice
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 590ms
And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 161ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 176ms
And Show all transport types 1s 045ms
And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 600ms
java.lang.AssertionError: Nieoczekiwany błąd podczas żądania PUT pod adresem /transports/228270600 - status odpowiedzi: 422 , komunikat:  [errors:[Operacja nie powiodła się. Prosimy spróbować ponownie a, jeśli problem się powtarza, o kontakt z info@logintegra.com.]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.putObjectToApolloApi(RestUtil.java:194)
	at CucumberTests.Transport.AdviceTransport.createAdviceByJSONFile(AdviceTransport.java:345)
	at ✽.Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast"(file:Features/Atom/Mail/AdviceMail.feature:28)
And Go to "TRANSPORT_TABLE" 000ms
And Go to transport details "DELIVERY" 000ms
And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-piast" 000ms
When Go to transport details "DELIVERY" 000ms
And Fill transport form 000ms
And Set "advice" inputs from JSON file "EDIT_ADVICE_DELIVERY" "super-admin-piast" 000ms
And Expand advice panel 000ms
And Edit advice in transport details 000ms
And Click "save-transport-and-close" save button and wait for form to disappear 000ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 000ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 102ms
After Hooks.cleanUserDetailsAfterTest() 169ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 476ms
And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 233ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 191ms
And Show all transport types 1s 044ms
And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD" as "super-admin-keeeper" 589ms
And Go to "TRANSPORT_TABLE" 158ms
And Go to transport details "LOAD" 2s 407ms
And Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-keeeper" 001ms
When Go to transport details "LOAD" 3s 159ms
And Fill transport form 26s 053ms
And Set "advice" inputs from JSON file "EDIT_ADVICE_LOAD" "super-admin-keeeper" 002ms
And Expand advice panel 112ms
And Edit advice in transport details 20s 482ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 121ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 3m 377ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 156ms
After Hooks.cleanUserDetailsAfterTest() 251ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skd" 094ms
And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 232ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 1s 338ms
And Confirm status "ARRIVAL" by Public API "v1" 313ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wjazd na teren zakładu" 5s 269ms
Then Check if user got a mail 000ms
And Confirm status "DEPARTURE" by Public API "v1" 252ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wyjazd" 35s 322ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 154ms
After Hooks.cleanUserDetailsAfterTest() 161ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 000ms
Given Set token of apiUsername "super-admin-hochland" 091ms
And Prepare company "Dostawca Hochland Automat 1" verification email setting "48h" 031ms
And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 196ms
And Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "dha1-supplier-2@qa.qa-test" 2s 418ms
And Create transport "CREATE_DELIVERY" by JSON file as "dha1-supplier-2@qa.qa-test" 15s 285ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Weryfikacja danych awizacji" 58s 180ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 080ms
After Hooks.cleanUserDetailsAfterTest() 213ms
After Hooks.rollbackVerificationEmailSettingAfterTest() 132ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 487ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 233ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 255ms
And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 585ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowa aukcja" 5s 254ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 112ms
After Hooks.cleanUserDetailsAfterTest() 305ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 042ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 346ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 197ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 120ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 511ms
And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 398ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 5s 187ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 074ms
After Hooks.cleanUserDetailsAfterTest() 262ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "swisskrono-producer" and set token of apiUsername "super-admin-skz" 2s 438ms
And Prepare user "swisskrono-producer" details with all notifications and "apolloautomattest@gmail.com" by JSON file 379ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 241ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 113ms
And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 187ms
And Wait till auction end 1m 58s 018ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Dodano nową ofertę" 2m 47s 438ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 112ms
After Hooks.cleanUserDetailsAfterTest() 303ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 258ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 223ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 269ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 137ms
And Wait till auction end 1m 58s 017ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Aukcja zakończona bez ofert" 5s 484ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 094ms
After Hooks.cleanUserDetailsAfterTest() 187ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 540ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 324ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 250ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 137ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 184ms
And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 283ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Oferta przelicytowana" 15s 678ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 099ms
After Hooks.cleanUserDetailsAfterTest() 295ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 163ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 343ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 230ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 112ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 185ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 2m 15s 634ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 089ms
After Hooks.cleanUserDetailsAfterTest() 285ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 190ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 318ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 213ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 120ms
And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 289ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 5s 192ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 080ms
After Hooks.cleanUserDetailsAfterTest() 265ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 002ms
Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 637ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 320ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 194ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" and finish of auction in "121" minutes 2s 174ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zakończenie aukcji" 15s 691ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 094ms
After Hooks.cleanUserDetailsAfterTest() 260ms
View Feature Discrepancy Report Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 464ms
And Prepare user "hochland-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 619ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 412ms
And Go to "TRANSPORT_TABLE" 147ms
And Go to transport details "DELIVERY" 2s 756ms
And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 002ms
And Fill transport form 37s 930ms
And Open section: "discrepancy-report-panel" 1s 069ms
And Fill discrepancy report section 49s 556ms
And Go to transport details "DELIVERY" 2s 471ms
And Change filled value in details "rodo-acceptance" "checkbox" "true" "0" 1s 289ms
And Generate discrepancy report 18s 811ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Utworzono protokół niezgodności" 5s 947ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 126ms
After Hooks.cleanUserDetailsAfterTest() 430ms
View Feature Mode of transportation mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-bausch" 094ms
And Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file 361ms
When Create default mode of transportation by API with "pba1-carrier" 183ms
Then Update mode of transportation by API with "pba1-carrier": "BBBB0000" "Model2" "Marka2" "CCCC0000" 099ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Środek transportu BBBB0000 został zaktualizowany" 11s 662ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 294ms
After Hooks.deleteModeOfTransportationAfterTest() 096ms
View Feature Mode of transportation mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-bausch" 093ms
And Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file 342ms
When Create default mode of transportation by API with "pba1-carrier" 079ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowy środek transportu" 5s 334ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 280ms
After Hooks.deleteModeOfTransportationAfterTest() 050ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 495ms
And Prepare user "pha2-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 380ms
And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 022ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 385ms
And Go to "WAREHOUSE_TAB" 818ms
And Select warehouse "Serownia" 1s 397ms
And Set week view 1s 094ms
And Show yesterday 1s 054ms
And Move window into the past 305ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "spóźnił się na" 53s 407ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 107ms
After Hooks.cleanUserDetailsAfterTest() 326ms
After Hooks.rollbackAddedAuthorities() 018ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 251ms
And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 344ms
And Wait "60" seconds 1m
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 304ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica import" 32s 909ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 106ms
After Hooks.cleanUserDetailsAfterTest() 313ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 910ms
And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 359ms
And Wait "60" seconds 1m
And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 296ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica eksport" 36s 866ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 106ms
After Hooks.cleanUserDetailsAfterTest() 328ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 204ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 368ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 207ms
And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 33s 752ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zlecenie czeka na akceptację" 5s 456ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 089ms
After Hooks.cleanUserDetailsAfterTest() 248ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 163ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 342ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 234ms
And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 33s 835ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zostało przekazane nowe zlecenie" 5s 901ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 083ms
After Hooks.cleanUserDetailsAfterTest() 250ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 951ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 394ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 224ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 164ms
And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 201ms
And Add a bid "500" to an auction by JSON file as "pskza2-carrier-2@qa.qa-test" for "pskza2-carrier-2@qa.qa-test" 210ms
Then If user is login then logout 332ms
And Login as "swisskrono-admin" 1s 005ms
And Go to auction details 1s 215ms
And Pass transport to carrier from auction details 1s 280ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 10s 896ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 101ms
After Hooks.cleanUserDetailsAfterTest() 386ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 211ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 440ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 234ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 130ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowe zapytanie ofertowe" 5s 320ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 077ms
After Hooks.cleanUserDetailsAfterTest() 348ms
View Feature Remind password
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-adama" 092ms
And Prepare user "adama-admin" details with all notifications and "automaty10@o2.pl" by JSON file 190ms
Then Send password remind email "automaty10@o2.pl" and check if status is ok 174ms
After Hooks.cleanUserDetailsAfterTest() 167ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 131ms
And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 001ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 407ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 297ms
When Click button advice in transport table "CONTAINER" 089ms
And Set advice window in schedule 2s 565ms
And Fill advice form 16s 761ms
And Click advice save button and wait for advice form to disappear 30s 716ms
And Go to "TRANSPORT_TABLE" 194ms
And Go to transport details "CONTAINER" 2s 470ms
Then Check are advice values equals 4s 340ms
After Hooks.deleteTransportAfterTest() 108ms
After Hooks.cleanUserDetailsAfterTest() 275ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 925ms
And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 001ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 353ms
And Add transport by SKApi in "MGW" assigned to "" 002ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 6s 372ms
When Click button advice in transport table "OWN_COLLECTION" 088ms
And Set advice window in schedule 2s 549ms
And Fill advice form 16s 800ms
And Click advice save button and wait for advice form to disappear 30s 682ms
And Go to "TRANSPORT_TABLE" 159ms
And Go to transport details "OWN_COLLECTION" 2s 449ms
Then Check are advice values equals 4s 311ms
After Hooks.deleteTransportAfterTest() 125ms
After Hooks.cleanUserDetailsAfterTest() 312ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 866ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 000ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 326ms
And Add transport by SKApi in "MGW" assigned to "" 002ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 790ms
When Click button advice in transport table "TRANSPORT_ORDER" 086ms
And Set advice window in schedule 2s 582ms
And Fill advice form 16s 720ms
And Click advice save button and wait for advice form to disappear 30s 736ms
And Go to "TRANSPORT_TABLE" 223ms
And Go to transport details "TRANSPORT_ORDER" 2s 467ms
Then Check are advice values equals 4s 341ms
After Hooks.deleteTransportAfterTest() 107ms
After Hooks.cleanUserDetailsAfterTest() 270ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 185ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 000ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 479ms
And Add transport by SKApi in "MGW" assigned to "" 002ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 876ms
When Click button advice in transport table "TRANSPORT_ORDER" 088ms
And Set advice window in schedule 2s 549ms
And Fill advice form 16s 733ms
And Click advice save button and wait for advice form to disappear 30s 718ms
And Go to "TRANSPORT_TABLE" 233ms
And Go to transport details "TRANSPORT_ORDER" 2s 443ms
Then Check are advice values equals 4s 327ms
After Hooks.deleteTransportAfterTest() 136ms
After Hooks.cleanUserDetailsAfterTest() 381ms
View Feature SK Api - Advice transport
Scenario Outline Check if it possible to advice transport when transport is created by sk API
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 844ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 230ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 002ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 807ms
When Click button advice in transport table "TRANSPORT_ORDER" 075ms
And Set advice window in schedule 30s 110ms
org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//button[@data-button-name='SHIFT_RIGHT_DAY']"}
  (Session info: headless chrome=92.0.4515.131)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.2KxY4c}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 27f8686fbbe216e38127d63861020cbd
*** Element info: {Using=xpath, value=//button[@data-button-name='SHIFT_RIGHT_DAY']}
	at sun.reflect.GeneratedConstructorAccessor215.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:356)
	at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:458)
	at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
	at Pages.BasePage.getWebElementByXpath(BasePage.java:325)
	at CucumberTests.Transport.AdviceTransport.setAdviceWindowInSchedule(AdviceTransport.java:91)
	at ✽.Set advice window in schedule(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:13)
And Fill advice form 000ms
And Click advice save button and wait for advice form to disappear 000ms
And Go to "TRANSPORT_TABLE" 000ms
And Go to transport details "TRANSPORT_ORDER" 000ms
Then Check are advice values equals 000ms
After Hooks.deleteTransportAfterTest() 071ms
After Hooks.cleanUserDetailsAfterTest() 229ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 902ms
And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 001ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 352ms
And Add transport by SKApi in "MGW" assigned to "" 002ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 389ms
When Click button advice in transport table "OWN_COLLECTION" 094ms
And Set advice window in schedule 2s 547ms
And Fill advice form 16s 741ms
And Click advice save button and wait for advice form to disappear 30s 729ms
And Go to "TRANSPORT_TABLE" 196ms
Then Check advice data in SK API database "OWN_COLLECTION" 128ms
After Hooks.deleteTransportAfterTest() 100ms
After Hooks.cleanUserDetailsAfterTest() 268ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 923ms
And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 000ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 343ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 323ms
When Click button advice in transport table "CONTAINER" 072ms
And Set advice window in schedule 2s 562ms
And Fill advice form 16s 780ms
And Click advice save button and wait for advice form to disappear 30s 658ms
And Go to "TRANSPORT_TABLE" 207ms
Then Check advice data in SK API database "CONTAINER" 086ms
After Hooks.deleteTransportAfterTest() 111ms
After Hooks.cleanUserDetailsAfterTest() 289ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Before Hooks.showScenarioName(Scenario) 002ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 851ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 331ms
And Add transport by SKApi in "MGW" assigned to "" 004ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 002ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 916ms
When Click button advice in transport table "TRANSPORT_ORDER" 088ms
And Set advice window in schedule 2s 569ms
And Fill advice form 16s 822ms
And Click advice save button and wait for advice form to disappear 30s 781ms
And Go to "TRANSPORT_TABLE" 225ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 029ms
After Hooks.deleteTransportAfterTest() 094ms
After Hooks.cleanUserDetailsAfterTest() 289ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 792ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 479ms
And Add transport by SKApi in "MGW" assigned to "" 002ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 869ms
When Click button advice in transport table "TRANSPORT_ORDER" 090ms
And Set advice window in schedule 2s 549ms
And Fill advice form 16s 814ms
And Click advice save button and wait for advice form to disappear 30s 703ms
And Go to "TRANSPORT_TABLE" 228ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 035ms
After Hooks.deleteTransportAfterTest() 113ms
After Hooks.cleanUserDetailsAfterTest() 345ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 030ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 000ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 292ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 003ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 2s 934ms
When Click button advice in transport table "TRANSPORT_ORDER" 082ms
And Set advice window in schedule 2s 595ms
And Fill advice form 16s 677ms
And Click advice save button and wait for advice form to disappear 30s 718ms
And Go to "TRANSPORT_TABLE" 207ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 094ms
After Hooks.deleteTransportAfterTest() 095ms
After Hooks.cleanUserDetailsAfterTest() 205ms
View Feature Status rejection
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 299ms
And Prepare user "lantmannen-guard" details with all notifications and "apolloautomattest@gmail.com" by JSON file 222ms
And Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 185ms
And Add access to the warehouse "Magazyn - Nowa Sól" to the user "lantmannen-guard" by JSON file 129ms
And Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 1s 233ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 270ms
And Check if reject date is not visible 15s 023ms
When Reject status: Book of disinfection 096ms
And Check if reject date is visible 261ms
Then If user is login then logout 279ms
And Login as "lantmannen-admin" 843ms
And Check if note was added to transport after status rejection 1s 242ms
And Check if history note was added to transport after status rejection - "LOAD" 6s 588ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nieaktualna księga mycia i dezynfekcji" 2m 46s 695ms
And Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 098ms
After Hooks.cleanUserDetailsAfterTest() 184ms
After Hooks.rollbackWarehousesAccess() 134ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skd" 097ms
And Prepare login page 209ms
And Click remind password button 098ms
And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 162ms
And Send remind password form with email "apolloautomattest@gmail.com" 175ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Restart hasła! | Password reset!" 31s 673ms
And Extract password from mailgun mail 3s 727ms
And Reset password from link 730ms
Then Check if alert is displayed "Hasło nie może być takie samo jak aktualne hasło użytkownika." in remind password page 143ms
After Hooks.cleanUserDetailsAfterTest() 161ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-adama" 096ms
And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_USERS_MAIN_DATA" to user "oaa1-receiver-2@qa.qa-test" 093ms
When Login as "oaa1-receiver-2@qa.qa-test" 1s 313ms
And Go to user "oaa1-receiver@qa.qa-test" details edition by prepared link 023ms
And Change user details "email" to "newEmailAddress@newEmail.com" 256ms
And Change user details "phone" to "123456789" 131ms
Then Save user details 236ms
And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 054ms
After Hooks.cleanUserDetailsAfterTest() 095ms
After Hooks.rollbackAddedAuthorities() 045ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 096ms
And Set basic authorities "ROLE_USERS_TAB;EDIT_USERS_NOTIFICATION" to user "pskza1-carrier-2@qa.qa-test" 027ms
When Login as "pskza1-carrier-2@qa.qa-test" 1s 963ms
And Go to user "pskza1-carrier@qa.qa-test" details edition by prepared link 018ms
And Expand "other" notification section 574ms
And Select all notifications in "other" section 101ms
Then Save user details 377ms
After Hooks.cleanUserDetailsAfterTest() 147ms
After Hooks.rollbackAddedAuthorities() 024ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-adama" 095ms
And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;ROLE_EDIT_USERS_MAIN_DATA" to user "adama-buyer@qa.qa-test" 069ms
And Set user details json of user "oaa1-receiver@qa.qa-test" 001ms
When Login as "adama-buyer@qa.qa-test" 1s 394ms
And Go to "USERS_TAB" 742ms
And Find user "oaa1-receiver@qa.qa-test" 2s 262ms
And Change user details "email" to "newEmailAddress@newEmail.com" 245ms
And Change user details "phone" to "123456789" 157ms
Then Save user details 240ms
And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 063ms
After Hooks.cleanUserDetailsAfterTest() 104ms
After Hooks.rollbackAddedAuthorities() 041ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-skz" 096ms
And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;EDIT_USERS_NOTIFICATION" to user "swisskrono-tradesman@qa.qa-test" 053ms
And Set user details json of user "pskza1-carrier@qa.qa-test" 000ms
When Login as "swisskrono-tradesman@qa.qa-test" 1s 913ms
And Go to "USERS_TAB" 817ms
And Find user "pskza1-carrier@qa.qa-test" 2s 235ms
And Expand "GLUE_FACTORY" notification section 233ms
And Select all notifications in "GLUE_FACTORY" section 482ms
Then Save user details 459ms
After Hooks.cleanUserDetailsAfterTest() 147ms
After Hooks.rollbackAddedAuthorities() 041ms