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

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@cleanUserDetailsAfterTest 414 4 20 0 0 438 41 4 45 49m 9s 695ms Failed
View Feature Invitation
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 236ms
And Delete invitations with email "automaty31415@test.pl" 099ms
Then Create invitation by JSON file "super-admin-alrec" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 436ms
And Prepare user "piast-admin" details with all notifications and "automaty31415@test.pl" by JSON file 1s 423ms
When Login as "piast-admin" 5s 171ms
Then Go to "INVITATIONS_TAB" 732ms
And Go to invitation details 155ms
Then Reject invitation by button as user 315ms
When If user is login then logout 309ms
Then Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 4s 999ms
And Go to "INVITATIONS_TAB" 500ms
And Go to "REJECTED_TAB" invitation status tab 345ms
Then Invitation is displayed on list "automaty31415@test.pl" 464ms
After Hooks.deleteInvitationAfterTest() 191ms
After Hooks.cleanUserDetailsAfterTest() 1s 356ms
View Feature Invitation
Before Hooks.showScenarioName(Scenario) 000ms
Given Set token of apiUsername "super-admin-alrec" 232ms
And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "automatyy3333@test.pl" by JSON file 1s 779ms
When Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 2s 380ms
And Go to "INVITATIONS_TAB" 444ms
And Create invitation for "existing" user "SUPPLIER" "SUPPLIER" "automatyy3333@test.pl" "PL" 2s 567ms
And Wait "3" seconds 3s
Then Create invitation success alert is displayed 107ms
After Hooks.deleteInvitationAfterTest() 192ms
After Hooks.cleanUserDetailsAfterTest() 1s 324ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 404ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 498ms
And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 2s 246ms
And Set "advice" inputs from JSON file "ADVICE_CONTAINER" "super-admin-adama" 001ms
And Show all transport types 1s 171ms
And Click button advice in transport table "CONTAINER" 274ms
And Set advice window in schedule 3s 464ms
And Fill advice form 17s 212ms
And Click advice save button and wait for advice form to disappear 33s 833ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!" 5s 863ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 268ms
After Hooks.deleteTransportAfterTest() 852ms
View Feature Advice Mail
Scenario Outline Check if mail was sent to creator after creating advice
Before Hooks.showScenarioName(Scenario) 000ms
Steps
Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 750ms
And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 209ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 014ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 001ms
And Show all transport types 1s 189ms
And Click button advice in transport table "DELIVERY" 247ms
And Set advice window in schedule 3s 503ms
And Fill advice form 13s 060ms
And Click advice save button and wait for advice form to disappear 10s 709ms
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.8hDyVp}, 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: 06a06e739653df18588b7b7cabd64f20
	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 095ms
After Hooks.deleteTransportAfterTest() 471ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 691ms
And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 945ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 996ms
And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-keeeper" 001ms
And Show all transport types 1s 160ms
And Click button advice in transport table "LOAD" 210ms
And Set advice window in schedule 3s 290ms
And Fill advice form 18s 761ms
And Click advice save button and wait for advice form to disappear 33s 311ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Time window has been saved!" 5s 880ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 536ms
After Hooks.deleteTransportAfterTest() 737ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 302ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 450ms
And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 905ms
And Show all transport types 1s 158ms
And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-adama" 3s 344ms
And Go to "TRANSPORT_TABLE" 397ms
And Go to transport details "CONTAINER" 2s 956ms
And Set "transport" inputs from JSON file "EDIT_CONTAINER" "super-admin-adama" 001ms
When Go to transport details "CONTAINER" 3s 567ms
And Fill transport form 5s 196ms
And Set "advice" inputs from JSON file "EDIT_ADVICE_CONTAINER" "super-admin-adama" 002ms
And Expand advice panel 260ms
And Edit advice in transport details 17s 647ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 249ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 31s 742ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 265ms
After Hooks.deleteTransportAfterTest() 723ms
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 618ms
And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 164ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 979ms
And Show all transport types 1s 139ms
And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 1s 705ms
java.lang.AssertionError: Nieoczekiwany błąd podczas żądania PUT pod adresem /transports/228327421 - 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 064ms
After Hooks.deleteTransportAfterTest() 592ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 6s 024ms
And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 710ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 931ms
And Show all transport types 1s 156ms
And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD" as "super-admin-keeeper" 3s 376ms
And Go to "TRANSPORT_TABLE" 387ms
And Go to transport details "LOAD" 2s 931ms
And Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-keeeper" 001ms
When Go to transport details "LOAD" 3s 569ms
And Fill transport form 28s 675ms
And Set "advice" inputs from JSON file "EDIT_ADVICE_LOAD" "super-admin-keeeper" 001ms
And Expand advice panel 271ms
And Edit advice in transport details 23s 498ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 164ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 2m 41s 859ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 716ms
After Hooks.deleteTransportAfterTest() 821ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skd" 247ms
And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 199ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 2s 777ms
And Confirm status "ARRIVAL" by Public API "v1" 1s 206ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wjazd na teren zakładu" 10s 377ms
Then Check if user got a mail 000ms
And Confirm status "DEPARTURE" by Public API "v1" 1s 296ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wyjazd" 31s 239ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 955ms
After Hooks.deleteTransportAfterTest() 780ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-hochland" 245ms
And Prepare company "Dostawca Hochland Automat 1" verification email setting "48h" 190ms
And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 186ms
And Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "dha1-supplier-2@qa.qa-test" 8s 939ms
And Create transport "CREATE_DELIVERY" by JSON file as "dha1-supplier-2@qa.qa-test" 16s 918ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Weryfikacja danych awizacji" 1m 23s 277ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 683ms
After Hooks.deleteTransportAfterTest() 741ms
After Hooks.rollbackVerificationEmailSettingAfterTest() 419ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 964ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 221ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 151ms
And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 3s 654ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowa aukcja" 5s 179ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 042ms
After Hooks.deleteTransportAfterTest() 752ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 601ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 337ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 101ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 014ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 431ms
And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 1s 933ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 10s 433ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 029ms
After Hooks.deleteTransportAfterTest() 601ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-producer" and set token of apiUsername "super-admin-skz" 12s 450ms
And Prepare user "swisskrono-producer" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 533ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 136ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 954ms
And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 1s 006ms
And Wait till auction end 1m 57s 016ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Dodano nową ofertę" 2m 47s 062ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 361ms
After Hooks.deleteTransportAfterTest() 626ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 812ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 502ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 121ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 063ms
And Wait till auction end 1m 57s 016ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Aukcja zakończona bez ofert" 5s 885ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 379ms
After Hooks.deleteTransportAfterTest() 619ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 126ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 431ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 089ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 005ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 977ms
And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 1s 777ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Oferta przelicytowana" 10s 688ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 075ms
After Hooks.deleteTransportAfterTest() 573ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 557ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 360ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 115ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 978ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 044ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 1m 46s 583ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 176ms
After Hooks.deleteTransportAfterTest() 580ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 535ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 370ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 068ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 008ms
And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 654ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 5s 327ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 094ms
After Hooks.deleteTransportAfterTest() 609ms
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 213ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 735ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 095ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" and finish of auction in "121" minutes 3s 090ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zakończenie aukcji" 21s 317ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 053ms
After Hooks.deleteTransportAfterTest() 670ms
View Feature Discrepancy Report Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 921ms
And Prepare user "hochland-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 4s 098ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 202ms
And Go to "TRANSPORT_TABLE" 393ms
And Go to transport details "DELIVERY" 2s 961ms
And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 001ms
And Fill transport form 43s 091ms
And Open section: "discrepancy-report-panel" 1s 162ms
And Fill discrepancy report section 52s 455ms
And Go to transport details "DELIVERY" 2s 927ms
And Change filled value in details "rodo-acceptance" "checkbox" "true" "0" 1s 554ms
And Generate discrepancy report 21s 566ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Utworzono protokół niezgodności" 5s 506ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 3s 459ms
After Hooks.deleteTransportAfterTest() 900ms
View Feature Mode of transportation mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-bausch" 243ms
And Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file 3s 042ms
When Create default mode of transportation by API with "pba1-carrier" 649ms
Then Update mode of transportation by API with "pba1-carrier": "BBBB0000" "Model2" "Marka2" "CCCC0000" 354ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Środek transportu BBBB0000 został zaktualizowany" 10s 387ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 488ms
After Hooks.deleteModeOfTransportationAfterTest() 361ms
View Feature Mode of transportation mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-bausch" 255ms
And Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 749ms
When Create default mode of transportation by API with "pba1-carrier" 571ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowy środek transportu" 5s 191ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 455ms
After Hooks.deleteModeOfTransportationAfterTest() 308ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 9s 553ms
And Prepare user "pha2-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 113ms
And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 241ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 171ms
And Go to "WAREHOUSE_TAB" 1s 293ms
And Select warehouse "Serownia" 1s 558ms
And Set week view 1s 232ms
And Show yesterday 1s 144ms
And Move window into the past 438ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "spóźnił się na" 51s 965ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 311ms
After Hooks.deleteTransportAfterTest() 818ms
After Hooks.rollbackAddedAuthorities() 134ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 9s 444ms
And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 410ms
And Wait "60" seconds 1m
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 171ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica import" 36s 764ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 139ms
After Hooks.deleteTransportAfterTest() 617ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 608ms
And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 471ms
And Wait "60" seconds 1m
And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 209ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica eksport" 48s 796ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 360ms
After Hooks.deleteTransportAfterTest() 556ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 567ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 559ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 064ms
And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 34s 893ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zlecenie czeka na akceptację" 5s 839ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 066ms
After Hooks.deleteTransportAfterTest() 851ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 396ms
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 127ms
And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 34s 992ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zostało przekazane nowe zlecenie" 5s 534ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 068ms
After Hooks.deleteTransportAfterTest() 582ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 704ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 228ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 159ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 3s 097ms
And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 1s 053ms
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 166ms
Then If user is login then logout 261ms
And Login as "swisskrono-admin" 2s 779ms
And Go to auction details 2s 260ms
And Pass transport to carrier from auction details 1s 534ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 36s 437ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 724ms
After Hooks.deleteTransportAfterTest() 848ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 731ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 3s 146ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 080ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 995ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowe zapytanie ofertowe" 10s 379ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 737ms
After Hooks.deleteTransportAfterTest() 658ms
View Feature Remind password
Before Hooks.showScenarioName(Scenario) 000ms
Given Set token of apiUsername "super-admin-adama" 238ms
And Prepare user "adama-admin" details with all notifications and "automaty10@o2.pl" by JSON file 1s 534ms
Then Send password remind email "automaty10@o2.pl" and check if status is ok 329ms
After Hooks.cleanUserDetailsAfterTest() 1s 242ms
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 607ms
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 362ms
And Add transport by SKApi in "MGW" assigned to "" 024ms
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 919ms
When Click button advice in transport table "CONTAINER" 219ms
And Set advice window in schedule 3s 351ms
And Fill advice form 20s 511ms
And Click advice save button and wait for advice form to disappear 33s 261ms
And Go to "TRANSPORT_TABLE" 440ms
And Go to transport details "CONTAINER" 2s 934ms
Then Check are advice values equals 4s 980ms
After Hooks.cleanUserDetailsAfterTest() 2s 258ms
After Hooks.deleteTransportAfterTest() 782ms
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 664ms
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 338ms
And Add transport by SKApi in "MGW" assigned to "" 029ms
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 4s 114ms
When Click button advice in transport table "OWN_COLLECTION" 215ms
And Set advice window in schedule 3s 388ms
And Fill advice form 20s 502ms
And Click advice save button and wait for advice form to disappear 33s 320ms
And Go to "TRANSPORT_TABLE" 470ms
And Go to transport details "OWN_COLLECTION" 2s 966ms
Then Check are advice values equals 5s 003ms
After Hooks.cleanUserDetailsAfterTest() 2s 201ms
After Hooks.deleteTransportAfterTest() 837ms
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 852ms
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 390ms
And Add transport by SKApi in "MGW" assigned to "" 021ms
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 373ms
When Click button advice in transport table "TRANSPORT_ORDER" 212ms
And Set advice window in schedule 3s 389ms
And Fill advice form 20s 403ms
And Click advice save button and wait for advice form to disappear 33s 362ms
And Go to "TRANSPORT_TABLE" 537ms
And Go to transport details "TRANSPORT_ORDER" 2s 897ms
Then Check are advice values equals 5s 006ms
After Hooks.cleanUserDetailsAfterTest() 2s 345ms
After Hooks.deleteTransportAfterTest() 798ms
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" 8s 821ms
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 478ms
And Add transport by SKApi in "MGW" assigned to "" 024ms
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 951ms
When Click button advice in transport table "TRANSPORT_ORDER" 225ms
And Set advice window in schedule 3s 389ms
And Fill advice form 20s 425ms
And Click advice save button and wait for advice form to disappear 33s 275ms
And Go to "TRANSPORT_TABLE" 535ms
And Go to transport details "TRANSPORT_ORDER" 2s 906ms
Then Check are advice values equals 5s 003ms
After Hooks.cleanUserDetailsAfterTest() 2s 723ms
After Hooks.deleteTransportAfterTest() 782ms
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 667ms
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 703ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 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 532ms
When Click button advice in transport table "TRANSPORT_ORDER" 204ms
And Set advice window in schedule 30s 134ms
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.8hDyVp}, 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: 06a06e739653df18588b7b7cabd64f20
*** Element info: {Using=xpath, value=//button[@data-button-name='SHIFT_RIGHT_DAY']}
	at sun.reflect.GeneratedConstructorAccessor216.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 726ms
After Hooks.deleteTransportAfterTest() 528ms
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 681ms
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 317ms
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 "OWN_COLLECTION" created in transport table and set transport id 4s 148ms
When Click button advice in transport table "OWN_COLLECTION" 218ms
And Set advice window in schedule 3s 322ms
And Fill advice form 20s 530ms
And Click advice save button and wait for advice form to disappear 33s 265ms
And Go to "TRANSPORT_TABLE" 446ms
Then Check advice data in SK API database "OWN_COLLECTION" 447ms
After Hooks.cleanUserDetailsAfterTest() 2s 134ms
After Hooks.deleteTransportAfterTest() 794ms
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 568ms
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 396ms
And Add transport by SKApi in "MGW" assigned to "" 017ms
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 903ms
When Click button advice in transport table "CONTAINER" 208ms
And Set advice window in schedule 3s 321ms
And Fill advice form 20s 442ms
And Click advice save button and wait for advice form to disappear 33s 327ms
And Go to "TRANSPORT_TABLE" 461ms
Then Check advice data in SK API database "CONTAINER" 234ms
After Hooks.cleanUserDetailsAfterTest() 2s 222ms
After Hooks.deleteTransportAfterTest() 827ms
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 684ms
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 421ms
And Add transport by SKApi in "MGW" assigned to "" 021ms
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 261ms
When Click button advice in transport table "TRANSPORT_ORDER" 230ms
And Set advice window in schedule 3s 344ms
And Fill advice form 20s 306ms
And Click advice save button and wait for advice form to disappear 33s 258ms
And Go to "TRANSPORT_TABLE" 512ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 092ms
After Hooks.cleanUserDetailsAfterTest() 2s 170ms
After Hooks.deleteTransportAfterTest() 791ms
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 234ms
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 364ms
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 030ms
When Click button advice in transport table "TRANSPORT_ORDER" 288ms
And Set advice window in schedule 3s 399ms
And Fill advice form 20s 569ms
And Click advice save button and wait for advice form to disappear 33s 383ms
And Go to "TRANSPORT_TABLE" 477ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 094ms
After Hooks.cleanUserDetailsAfterTest() 2s 827ms
After Hooks.deleteTransportAfterTest() 792ms
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 735ms
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 855ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 021ms
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 575ms
When Click button advice in transport table "TRANSPORT_ORDER" 213ms
And Set advice window in schedule 3s 400ms
And Fill advice form 20s 466ms
And Click advice save button and wait for advice form to disappear 33s 836ms
And Go to "TRANSPORT_TABLE" 473ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 267ms
After Hooks.cleanUserDetailsAfterTest() 1s 733ms
After Hooks.deleteTransportAfterTest() 791ms
View Feature Status rejection
Scenario Outline Check if it is possible to reject status by guard in transport table
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 4s 747ms
And Prepare user "lantmannen-guard" details with all notifications and "apolloautomattest@gmail.com" by JSON file 917ms
And Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 464ms
And Add access to the warehouse "Magazyn - Nowa Sól" to the user "lantmannen-guard" by JSON file 742ms
And Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 4s 577ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 858ms
And Check if reject date is not visible 15s 048ms
When Reject status: Book of disinfection 234ms
And Check if reject date is visible 1s 102ms
Then If user is login then logout 270ms
And Login as "lantmannen-admin" 2s 605ms
And Check if note was added to transport after status rejection 1s 691ms
And Check if history note was added to transport after status rejection - "LOAD" 22s 025ms
java.lang.AssertionError: Nie znaleziono wpisu w historii zlecenia o odrzuceniu statusu!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at Pages.Transport.TransportFormPage.checkIfHistoryNoteWasAddedToTransport(TransportFormPage.java:238)
	at CucumberTests.StatusTests.RejectStatuses.checkIfHistoryNoteWasAddedToTransportAfterStatusRejection(RejectStatuses.java:67)
	at ✽.Check if history note was added to transport after status rejection - "LOAD"(file:Features/Atom/Statuses/RejectStatuses.feature:17)
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nieaktualna księga mycia i dezynfekcji" 000ms
And Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 114ms
After Hooks.deleteTransportAfterTest() 741ms
After Hooks.rollbackWarehousesAccess() 798ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skd" 220ms
And Prepare login page 464ms
And Click remind password button 258ms
And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 021ms
And Send remind password form with email "apolloautomattest@gmail.com" 584ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Restart hasła! | Password reset!" 36s 667ms
And Extract password from mailgun mail 4s 373ms
And Reset password from link 1s 557ms
Then Check if alert is displayed "Hasło nie może być takie samo jak aktualne hasło użytkownika." in remind password page 217ms
After Hooks.cleanUserDetailsAfterTest() 933ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-adama" 224ms
And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_USERS_MAIN_DATA" to user "oaa1-receiver-2@qa.qa-test" 419ms
When Login as "oaa1-receiver-2@qa.qa-test" 4s 488ms
And Go to user "oaa1-receiver@qa.qa-test" details edition by prepared link 148ms
And Change user details "email" to "newEmailAddress@newEmail.com" 1s 162ms
And Change user details "phone" to "123456789" 472ms
Then Save user details 1s 073ms
And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 175ms
After Hooks.cleanUserDetailsAfterTest() 642ms
After Hooks.rollbackAddedAuthorities() 247ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 250ms
And Set basic authorities "ROLE_USERS_TAB;EDIT_USERS_NOTIFICATION" to user "pskza1-carrier-2@qa.qa-test" 202ms
When Login as "pskza1-carrier-2@qa.qa-test" 7s 131ms
And Go to user "pskza1-carrier@qa.qa-test" details edition by prepared link 109ms
And Expand "other" notification section 2s 387ms
And Select all notifications in "other" section 272ms
Then Save user details 1s 520ms
After Hooks.cleanUserDetailsAfterTest() 887ms
After Hooks.rollbackAddedAuthorities() 158ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 000ms
Given Set token of apiUsername "super-admin-adama" 239ms
And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;ROLE_EDIT_USERS_MAIN_DATA" to user "adama-buyer@qa.qa-test" 465ms
And Set user details json of user "oaa1-receiver@qa.qa-test" 013ms
When Login as "adama-buyer@qa.qa-test" 5s 197ms
And Go to "USERS_TAB" 1s 551ms
And Find user "oaa1-receiver@qa.qa-test" 2s 701ms
And Change user details "email" to "newEmailAddress@newEmail.com" 830ms
And Change user details "phone" to "123456789" 401ms
Then Save user details 1s 021ms
And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 156ms
After Hooks.cleanUserDetailsAfterTest() 637ms
After Hooks.rollbackAddedAuthorities() 240ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 217ms
And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;EDIT_USERS_NOTIFICATION" to user "swisskrono-tradesman@qa.qa-test" 323ms
And Set user details json of user "pskza1-carrier@qa.qa-test" 011ms
When Login as "swisskrono-tradesman@qa.qa-test" 9s 183ms
And Go to "USERS_TAB" 1s 579ms
And Find user "pskza1-carrier@qa.qa-test" 2s 681ms
And Expand "GLUE_FACTORY" notification section 539ms
And Select all notifications in "GLUE_FACTORY" section 1s 318ms
Then Save user details 1s 869ms
After Hooks.cleanUserDetailsAfterTest() 1s 080ms
After Hooks.rollbackAddedAuthorities() 238ms