Project Number Date
ApolloFullRunnerReport apollo-test-2.128 22 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 52m 27s 044ms Failed
View Feature Invitation
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 223ms
And Delete invitations with email "automaty31415@test.pl" 107ms
Then Create invitation by JSON file "super-admin-alrec" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 490ms
And Prepare user "piast-admin" details with all notifications and "automaty31415@test.pl" by JSON file 1s 395ms
When Login as "piast-admin" 5s 150ms
Then Go to "INVITATIONS_TAB" 704ms
And Go to invitation details 156ms
Then Reject invitation by button as user 290ms
When If user is login then logout 317ms
Then Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 5s 050ms
And Go to "INVITATIONS_TAB" 499ms
And Go to "REJECTED_TAB" invitation status tab 307ms
Then Invitation is displayed on list "automaty31415@test.pl" 435ms
After Hooks.deleteInvitationAfterTest() 144ms
After Hooks.cleanUserDetailsAfterTest() 1s 230ms
View Feature Invitation
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-alrec" 239ms
And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "automatyy3333@test.pl" by JSON file 1s 637ms
When Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 2s 386ms
And Go to "INVITATIONS_TAB" 473ms
And Create invitation for "existing" user "SUPPLIER" "SUPPLIER" "automatyy3333@test.pl" "PL" 2s 661ms
And Wait "3" seconds 3s
Then Create invitation success alert is displayed 117ms
After Hooks.deleteInvitationAfterTest() 199ms
After Hooks.cleanUserDetailsAfterTest() 1s 307ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 464ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 070ms
And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 2s 220ms
And Set "advice" inputs from JSON file "ADVICE_CONTAINER" "super-admin-adama" 002ms
And Show all transport types 1s 154ms
And Click button advice in transport table "CONTAINER" 205ms
And Set advice window in schedule 3s 291ms
And Fill advice form 17s 165ms
And Click advice save button and wait for advice form to disappear 33s 777ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!" 5s 835ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 282ms
After Hooks.deleteTransportAfterTest() 773ms
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" 2s 743ms
And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 963ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 044ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 001ms
And Show all transport types 1s 176ms
And Click button advice in transport table "DELIVERY" 247ms
And Set advice window in schedule 3s 542ms
And Fill advice form 12s 870ms
And Click advice save button and wait for advice form to disappear 10s 744ms
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-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-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/temp/buildTmp/.com.google.Chrome.KxtivS}, 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: 5569bb3f553cb37be0f7d68114832d6a
	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.cleanUserDetailsAfterTest() 1s 073ms
After Hooks.deleteTransportAfterTest() 498ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 682ms
And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 791ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 2s 025ms
And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-keeeper" 001ms
And Show all transport types 1s 173ms
And Click button advice in transport table "LOAD" 215ms
And Set advice window in schedule 3s 301ms
And Fill advice form 18s 855ms
And Click advice save button and wait for advice form to disappear 33s 335ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Time window has been saved!" 7s 784ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 495ms
After Hooks.deleteTransportAfterTest() 715ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 175ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 431ms
And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 907ms
And Show all transport types 1s 148ms
And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-adama" 3s 340ms
And Go to "TRANSPORT_TABLE" 403ms
And Go to transport details "CONTAINER" 2s 884ms
And Set "transport" inputs from JSON file "EDIT_CONTAINER" "super-admin-adama" 001ms
When Go to transport details "CONTAINER" 3s 521ms
And Fill transport form 5s 238ms
And Set "advice" inputs from JSON file "EDIT_ADVICE_CONTAINER" "super-admin-adama" 001ms
And Expand advice panel 258ms
And Edit advice in transport details 17s 617ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 272ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 5s 725ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 295ms
After Hooks.deleteTransportAfterTest() 798ms
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" 5s 444ms
And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 170ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 967ms
And Show all transport types 1s 159ms
And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 1s 759ms
java.lang.AssertionError: Nieoczekiwany błąd podczas żądania PUT pod adresem /transports/228301976 - 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.cleanUserDetailsAfterTest() 1s 071ms
After Hooks.deleteTransportAfterTest() 673ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 5s 729ms
And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 699ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 963ms
And Show all transport types 1s 139ms
And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD" as "super-admin-keeeper" 3s 428ms
And Go to "TRANSPORT_TABLE" 363ms
And Go to transport details "LOAD" 2s 921ms
And Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-keeeper" 001ms
When Go to transport details "LOAD" 3s 550ms
And Fill transport form 28s 750ms
And Set "advice" inputs from JSON file "EDIT_ADVICE_LOAD" "super-admin-keeeper" 001ms
And Expand advice panel 256ms
And Edit advice in transport details 23s 468ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 252ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 2m 42s 957ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 754ms
After Hooks.deleteTransportAfterTest() 805ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skd" 232ms
And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 179ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 2s 792ms
And Confirm status "ARRIVAL" by Public API "v1" 1s 183ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wjazd na teren zakładu" 5s 188ms
Then Check if user got a mail 000ms
And Confirm status "DEPARTURE" by Public API "v1" 1s 216ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wyjazd" 36s 302ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 945ms
After Hooks.deleteTransportAfterTest() 840ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-hochland" 266ms
And Prepare company "Dostawca Hochland Automat 1" verification email setting "48h" 220ms
And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 170ms
And Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "dha1-supplier-2@qa.qa-test" 9s 168ms
And Create transport "CREATE_DELIVERY" by JSON file as "dha1-supplier-2@qa.qa-test" 17s 092ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Weryfikacja danych awizacji" 1m 45s 362ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 717ms
After Hooks.deleteTransportAfterTest() 736ms
After Hooks.rollbackVerificationEmailSettingAfterTest() 440ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 182ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 202ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 328ms
And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 3s 595ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowa aukcja" 5s 177ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 078ms
After Hooks.deleteTransportAfterTest() 709ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 573ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 374ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 147ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 006ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 376ms
And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 1s 975ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 10s 359ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 072ms
After Hooks.deleteTransportAfterTest() 595ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-producer" and set token of apiUsername "super-admin-skz" 12s 437ms
And Prepare user "swisskrono-producer" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 586ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 164ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 945ms
And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 1s 008ms
And Wait till auction end 1m 57s 015ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Dodano nową ofertę" 2m 40s 971ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 378ms
After Hooks.deleteTransportAfterTest() 628ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 708ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 542ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 064ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 133ms
And Wait till auction end 1m 57s 018ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Aukcja zakończona bez ofert" 5s 842ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 377ms
After Hooks.deleteTransportAfterTest() 599ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 881ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 392ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 104ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 051ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 013ms
And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 1s 884ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Oferta przelicytowana" 15s 992ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 226ms
After Hooks.deleteTransportAfterTest() 609ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 586ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 378ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 093ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 081ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 002ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 2m 2s 698ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 235ms
After Hooks.deleteTransportAfterTest() 552ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 558ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 393ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 066ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 002ms
And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 766ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 5s 329ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 052ms
After Hooks.deleteTransportAfterTest() 569ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 5s 204ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 805ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 084ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" and finish of auction in "121" minutes 3s 035ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zakończenie aukcji" 1m 4s 303ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 112ms
After Hooks.deleteTransportAfterTest() 685ms
View Feature Discrepancy Report Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 286ms
And Prepare user "hochland-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 4s 287ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 174ms
And Go to "TRANSPORT_TABLE" 395ms
And Go to transport details "DELIVERY" 2s 946ms
And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 001ms
And Fill transport form 43s 082ms
And Open section: "discrepancy-report-panel" 1s 154ms
And Fill discrepancy report section 52s 458ms
And Go to transport details "DELIVERY" 2s 869ms
And Change filled value in details "rodo-acceptance" "checkbox" "true" "0" 1s 558ms
And Generate discrepancy report 6s 095ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Utworzono protokół niezgodności" 5s 488ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 3s 353ms
After Hooks.deleteTransportAfterTest() 1s 021ms
View Feature Mode of transportation mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-bausch" 252ms
And Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file 3s 079ms
When Create default mode of transportation by API with "pba1-carrier" 768ms
Then Update mode of transportation by API with "pba1-carrier": "BBBB0000" "Model2" "Marka2" "CCCC0000" 420ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Środek transportu BBBB0000 został zaktualizowany" 10s 426ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 622ms
After Hooks.deleteModeOfTransportationAfterTest() 346ms
View Feature Mode of transportation mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-bausch" 235ms
And Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 762ms
When Create default mode of transportation by API with "pba1-carrier" 595ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowy środek transportu" 5s 176ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 458ms
After Hooks.deleteModeOfTransportationAfterTest() 292ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 9s 511ms
And Prepare user "pha2-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 172ms
And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 260ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 211ms
And Go to "WAREHOUSE_TAB" 1s 351ms
And Select warehouse "Serownia" 1s 578ms
And Set week view 1s 253ms
And Show yesterday 1s 135ms
And Move window into the past 415ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "spóźnił się na" 1m 2s 447ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 347ms
After Hooks.deleteTransportAfterTest() 817ms
After Hooks.rollbackAddedAuthorities() 187ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 9s 506ms
And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 460ms
And Wait "60" seconds 1m
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 160ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica import" 31s 429ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 222ms
After Hooks.deleteTransportAfterTest() 576ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 509ms
And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 495ms
And Wait "60" seconds 1m
And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 203ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica eksport" 47s 240ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 422ms
After Hooks.deleteTransportAfterTest() 551ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 619ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 635ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 096ms
And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 34s 754ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zlecenie czeka na akceptację" 5s 572ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 209ms
After Hooks.deleteTransportAfterTest() 797ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 551ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 596ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 091ms
And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 34s 896ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zostało przekazane nowe zlecenie" 5s 477ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 060ms
After Hooks.deleteTransportAfterTest() 585ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 643ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 269ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 154ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 3s 194ms
And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 1s 091ms
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" 1s 139ms
Then If user is login then logout 264ms
And Login as "swisskrono-admin" 2s 951ms
And Go to auction details 2s 262ms
And Pass transport to carrier from auction details 1s 575ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 36s 268ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 689ms
After Hooks.deleteTransportAfterTest() 814ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 856ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 3s 219ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 152ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 976ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowe zapytanie ofertowe" 10s 356ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 693ms
After Hooks.deleteTransportAfterTest() 668ms
View Feature Remind password
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-adama" 239ms
And Prepare user "adama-admin" details with all notifications and "automaty10@o2.pl" by JSON file 1s 521ms
Then Send password remind email "automaty10@o2.pl" and check if status is ok 327ms
After Hooks.cleanUserDetailsAfterTest() 1s 287ms
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" 2s 637ms
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 2s 378ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
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 7s 001ms
When Click button advice in transport table "CONTAINER" 278ms
And Set advice window in schedule 3s 633ms
And Fill advice form 20s 431ms
And Click advice save button and wait for advice form to disappear 33s 271ms
And Go to "TRANSPORT_TABLE" 471ms
And Go to transport details "CONTAINER" 3s 046ms
Then Check are advice values equals 4s 938ms
After Hooks.cleanUserDetailsAfterTest() 2s 311ms
After Hooks.deleteTransportAfterTest() 778ms
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" 7s 604ms
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 2s 372ms
And Add transport by SKApi in "MGW" assigned to "" 018ms
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 7s 210ms
When Click button advice in transport table "OWN_COLLECTION" 239ms
And Set advice window in schedule 3s 387ms
And Fill advice form 20s 479ms
And Click advice save button and wait for advice form to disappear 33s 264ms
And Go to "TRANSPORT_TABLE" 420ms
And Go to transport details "OWN_COLLECTION" 2s 871ms
Then Check are advice values equals 4s 970ms
After Hooks.cleanUserDetailsAfterTest() 2s 155ms
After Hooks.deleteTransportAfterTest() 811ms
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" 7s 538ms
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 2s 402ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
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 4s 316ms
When Click button advice in transport table "TRANSPORT_ORDER" 224ms
And Set advice window in schedule 3s 359ms
And Fill advice form 20s 422ms
And Click advice save button and wait for advice form to disappear 33s 273ms
And Go to "TRANSPORT_TABLE" 481ms
And Go to transport details "TRANSPORT_ORDER" 2s 864ms
Then Check are advice values equals 4s 985ms
After Hooks.cleanUserDetailsAfterTest() 2s 265ms
After Hooks.deleteTransportAfterTest() 806ms
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) 000ms
Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 8s 863ms
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 3s 531ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
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 3s 854ms
When Click button advice in transport table "TRANSPORT_ORDER" 239ms
And Set advice window in schedule 3s 578ms
And Fill advice form 20s 478ms
And Click advice save button and wait for advice form to disappear 33s 270ms
And Go to "TRANSPORT_TABLE" 487ms
And Go to transport details "TRANSPORT_ORDER" 2s 869ms
Then Check are advice values equals 4s 979ms
After Hooks.cleanUserDetailsAfterTest() 2s 822ms
After Hooks.deleteTransportAfterTest() 793ms
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" 7s 479ms
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 1s 824ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 022ms
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 7s 600ms
When Click button advice in transport table "TRANSPORT_ORDER" 253ms
And Set advice window in schedule 30s 167ms
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-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-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/temp/buildTmp/.com.google.Chrome.KxtivS}, 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: 5569bb3f553cb37be0f7d68114832d6a
*** Element info: {Using=xpath, value=//button[@data-button-name='SHIFT_RIGHT_DAY']}
	at sun.reflect.GeneratedConstructorAccessor217.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.cleanUserDetailsAfterTest() 1s 727ms
After Hooks.deleteTransportAfterTest() 573ms
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" 7s 668ms
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 2s 376ms
And Add transport by SKApi in "MGW" assigned to "" 018ms
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 7s 155ms
When Click button advice in transport table "OWN_COLLECTION" 224ms
And Set advice window in schedule 3s 348ms
And Fill advice form 20s 512ms
And Click advice save button and wait for advice form to disappear 33s 275ms
And Go to "TRANSPORT_TABLE" 431ms
Then Check advice data in SK API database "OWN_COLLECTION" 407ms
After Hooks.cleanUserDetailsAfterTest() 2s 155ms
After Hooks.deleteTransportAfterTest() 901ms
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" 7s 499ms
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 2s 371ms
And Add transport by SKApi in "MGW" assigned to "" 019ms
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 982ms
When Click button advice in transport table "CONTAINER" 230ms
And Set advice window in schedule 3s 404ms
And Fill advice form 20s 561ms
And Click advice save button and wait for advice form to disappear 33s 279ms
And Go to "TRANSPORT_TABLE" 471ms
Then Check advice data in SK API database "CONTAINER" 234ms
After Hooks.cleanUserDetailsAfterTest() 2s 331ms
After Hooks.deleteTransportAfterTest() 820ms
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" 7s 785ms
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 2s 407ms
And Add transport by SKApi in "MGW" assigned to "" 022ms
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 4s 271ms
When Click button advice in transport table "TRANSPORT_ORDER" 234ms
And Set advice window in schedule 3s 385ms
And Fill advice form 20s 489ms
And Click advice save button and wait for advice form to disappear 33s 248ms
And Go to "TRANSPORT_TABLE" 486ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 090ms
After Hooks.cleanUserDetailsAfterTest() 2s 308ms
After Hooks.deleteTransportAfterTest() 795ms
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" 6s 433ms
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 3s 538ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
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 3s 952ms
When Click button advice in transport table "TRANSPORT_ORDER" 203ms
And Set advice window in schedule 3s 407ms
And Fill advice form 20s 318ms
And Click advice save button and wait for advice form to disappear 33s 310ms
And Go to "TRANSPORT_TABLE" 511ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 098ms
After Hooks.cleanUserDetailsAfterTest() 2s 892ms
After Hooks.deleteTransportAfterTest() 843ms
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-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 8s 881ms
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 1s 893ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 018ms
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 7s 665ms
When Click button advice in transport table "TRANSPORT_ORDER" 296ms
And Set advice window in schedule 3s 464ms
And Fill advice form 20s 431ms
And Click advice save button and wait for advice form to disappear 33s 770ms
And Go to "TRANSPORT_TABLE" 441ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 263ms
After Hooks.cleanUserDetailsAfterTest() 1s 754ms
After Hooks.deleteTransportAfterTest() 869ms
View Feature Status rejection
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 4s 586ms
And Prepare user "lantmannen-guard" details with all notifications and "apolloautomattest@gmail.com" by JSON file 895ms
And Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 052ms
And Add access to the warehouse "Magazyn - Nowa Sól" to the user "lantmannen-guard" by JSON file 743ms
And Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 4s 619ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 819ms
And Check if reject date is not visible 15s 076ms
When Reject status: Book of disinfection 210ms
And Check if reject date is visible 929ms
Then If user is login then logout 268ms
And Login as "lantmannen-admin" 2s 544ms
And Check if note was added to transport after status rejection 1s 676ms
And Check if history note was added to transport after status rejection - "LOAD" 7s 258ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nieaktualna księga mycia i dezynfekcji" 2m 41s 357ms
And Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 246ms
After Hooks.deleteTransportAfterTest() 871ms
After Hooks.rollbackWarehousesAccess() 722ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skd" 232ms
And Prepare login page 438ms
And Click remind password button 271ms
And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 049ms
And Send remind password form with email "apolloautomattest@gmail.com" 572ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Restart hasła! | Password reset!" 31s 506ms
And Extract password from mailgun mail 4s 748ms
And Reset password from link 1s 639ms
Then Check if alert is displayed "Hasło nie może być takie samo jak aktualne hasło użytkownika." in remind password page 229ms
After Hooks.cleanUserDetailsAfterTest() 948ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-adama" 251ms
And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_USERS_MAIN_DATA" to user "oaa1-receiver-2@qa.qa-test" 385ms
When Login as "oaa1-receiver-2@qa.qa-test" 4s 449ms
And Go to user "oaa1-receiver@qa.qa-test" details edition by prepared link 133ms
And Change user details "email" to "newEmailAddress@newEmail.com" 1s 120ms
And Change user details "phone" to "123456789" 476ms
Then Save user details 1s 027ms
And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 168ms
After Hooks.cleanUserDetailsAfterTest() 631ms
After Hooks.rollbackAddedAuthorities() 253ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 243ms
And Set basic authorities "ROLE_USERS_TAB;EDIT_USERS_NOTIFICATION" to user "pskza1-carrier-2@qa.qa-test" 201ms
When Login as "pskza1-carrier-2@qa.qa-test" 7s 348ms
And Go to user "pskza1-carrier@qa.qa-test" details edition by prepared link 098ms
And Expand "other" notification section 2s 416ms
And Select all notifications in "other" section 294ms
Then Save user details 1s 476ms
After Hooks.cleanUserDetailsAfterTest() 1s 232ms
After Hooks.rollbackAddedAuthorities() 184ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-adama" 244ms
And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;ROLE_EDIT_USERS_MAIN_DATA" to user "adama-buyer@qa.qa-test" 553ms
And Set user details json of user "oaa1-receiver@qa.qa-test" 014ms
When Login as "adama-buyer@qa.qa-test" 5s 911ms
And Go to "USERS_TAB" 1s 394ms
And Find user "oaa1-receiver@qa.qa-test" 2s 673ms
And Change user details "email" to "newEmailAddress@newEmail.com" 914ms
And Change user details "phone" to "123456789" 447ms
Then Save user details 1s 058ms
And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 163ms
After Hooks.cleanUserDetailsAfterTest() 652ms
After Hooks.rollbackAddedAuthorities() 236ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 248ms
And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;EDIT_USERS_NOTIFICATION" to user "swisskrono-tradesman@qa.qa-test" 366ms
And Set user details json of user "pskza1-carrier@qa.qa-test" 009ms
When Login as "swisskrono-tradesman@qa.qa-test" 9s 342ms
And Go to "USERS_TAB" 1s 506ms
And Find user "pskza1-carrier@qa.qa-test" 2s 711ms
And Expand "GLUE_FACTORY" notification section 551ms
And Select all notifications in "GLUE_FACTORY" section 1s 444ms
Then Save user details 1s 752ms
After Hooks.cleanUserDetailsAfterTest() 1s 050ms
After Hooks.rollbackAddedAuthorities() 235ms