Project Number Date
ApolloFullRunnerReport apollo-test-2.127 21 sie 2021, 05:25

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 53m 54s 270ms Failed
View Feature Invitation
Before Hooks.showScenarioName(Scenario) 000ms
Given Set token of apiUsername "super-admin-piast" 229ms
And Delete invitations with email "automaty31415@test.pl" 095ms
Then Create invitation by JSON file "super-admin-alrec" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 364ms
And Prepare user "piast-admin" details with all notifications and "automaty31415@test.pl" by JSON file 1s 422ms
When Login as "piast-admin" 5s 028ms
Then Go to "INVITATIONS_TAB" 738ms
And Go to invitation details 135ms
Then Reject invitation by button as user 312ms
When If user is login then logout 326ms
Then Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 5s 317ms
And Go to "INVITATIONS_TAB" 519ms
And Go to "REJECTED_TAB" invitation status tab 297ms
Then Invitation is displayed on list "automaty31415@test.pl" 454ms
After Hooks.deleteInvitationAfterTest() 152ms
After Hooks.cleanUserDetailsAfterTest() 1s 168ms
View Feature Invitation
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-alrec" 240ms
And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "automatyy3333@test.pl" by JSON file 1s 634ms
When Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 2s 389ms
And Go to "INVITATIONS_TAB" 463ms
And Create invitation for "existing" user "SUPPLIER" "SUPPLIER" "automatyy3333@test.pl" "PL" 2s 754ms
And Wait "3" seconds 3s
Then Create invitation success alert is displayed 119ms
After Hooks.deleteInvitationAfterTest() 191ms
After Hooks.cleanUserDetailsAfterTest() 1s 298ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 475ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 071ms
And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 2s 205ms
And Set "advice" inputs from JSON file "ADVICE_CONTAINER" "super-admin-adama" 002ms
And Show all transport types 1s 158ms
And Click button advice in transport table "CONTAINER" 245ms
And Set advice window in schedule 3s 315ms
And Fill advice form 17s 213ms
And Click advice save button and wait for advice form to disappear 33s 893ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!" 5s 546ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 285ms
After Hooks.deleteTransportAfterTest() 905ms
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 731ms
And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 955ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 017ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 001ms
And Show all transport types 1s 199ms
And Click button advice in transport table "DELIVERY" 246ms
And Set advice window in schedule 3s 429ms
And Fill advice form 12s 857ms
And Click advice save button and wait for advice form to disappear 10s 731ms
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.kdJMZk}, 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: 4d8790a524584ba4b90814192eae0275
	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 063ms
After Hooks.deleteTransportAfterTest() 581ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 645ms
And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 930ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 2s 020ms
And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-keeeper" 001ms
And Show all transport types 1s 147ms
And Click button advice in transport table "LOAD" 268ms
And Set advice window in schedule 3s 243ms
And Fill advice form 18s 772ms
And Click advice save button and wait for advice form to disappear 33s 312ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Time window has been saved!" 6s 001ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 613ms
After Hooks.deleteTransportAfterTest() 763ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 012ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 430ms
And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 914ms
And Show all transport types 1s 230ms
And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-adama" 3s 390ms
And Go to "TRANSPORT_TABLE" 394ms
And Go to transport details "CONTAINER" 2s 952ms
And Set "transport" inputs from JSON file "EDIT_CONTAINER" "super-admin-adama" 001ms
When Go to transport details "CONTAINER" 3s 542ms
And Fill transport form 5s 214ms
And Set "advice" inputs from JSON file "EDIT_ADVICE_CONTAINER" "super-admin-adama" 001ms
And Expand advice panel 266ms
And Edit advice in transport details 17s 599ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 237ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 49s 391ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 407ms
After Hooks.deleteTransportAfterTest() 734ms
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 764ms
And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 169ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 972ms
And Show all transport types 1s 170ms
And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 1s 616ms
java.lang.AssertionError: Nieoczekiwany błąd podczas żądania PUT pod adresem /transports/228271141 - 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 120ms
After Hooks.deleteTransportAfterTest() 589ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 5s 649ms
And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 751ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 933ms
And Show all transport types 1s 156ms
And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD" as "super-admin-keeeper" 3s 245ms
And Go to "TRANSPORT_TABLE" 375ms
And Go to transport details "LOAD" 2s 964ms
And Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-keeeper" 001ms
When Go to transport details "LOAD" 3s 533ms
And Fill transport form 28s 818ms
And Set "advice" inputs from JSON file "EDIT_ADVICE_LOAD" "super-admin-keeeper" 001ms
And Expand advice panel 260ms
And Edit advice in transport details 23s 455ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 256ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 2m 57s 281ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 709ms
After Hooks.deleteTransportAfterTest() 831ms
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 167ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 2s 862ms
And Confirm status "ARRIVAL" by Public API "v1" 1s 195ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wjazd na teren zakładu" 10s 445ms
Then Check if user got a mail 000ms
And Confirm status "DEPARTURE" by Public API "v1" 1s 300ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wyjazd" 31s 755ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 948ms
After Hooks.deleteTransportAfterTest() 793ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 000ms
Given Set token of apiUsername "super-admin-hochland" 271ms
And Prepare company "Dostawca Hochland Automat 1" verification email setting "48h" 232ms
And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 148ms
And Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "dha1-supplier-2@qa.qa-test" 9s 266ms
And Create transport "CREATE_DELIVERY" by JSON file as "dha1-supplier-2@qa.qa-test" 16s 923ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Weryfikacja danych awizacji" 1m 21s 655ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 677ms
After Hooks.deleteTransportAfterTest() 742ms
After Hooks.rollbackVerificationEmailSettingAfterTest() 420ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 954ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 216ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 152ms
And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 3s 603ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowa aukcja" 5s 380ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 058ms
After Hooks.deleteTransportAfterTest() 791ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 629ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 462ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 075ms
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 408ms
And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 1s 963ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 10s 699ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 097ms
After Hooks.deleteTransportAfterTest() 591ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-producer" and set token of apiUsername "super-admin-skz" 12s 583ms
And Prepare user "swisskrono-producer" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 631ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 158ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 835ms
And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 987ms
And Wait till auction end 1m 57s 016ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Dodano nową ofertę" 2m 44s 103ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 560ms
After Hooks.deleteTransportAfterTest() 645ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 584ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 570ms
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" 3s 089ms
And Wait till auction end 1m 57s 015ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Aukcja zakończona bez ofert" 21s 863ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 368ms
After Hooks.deleteTransportAfterTest() 718ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 250ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 409ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 123ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 032ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 973ms
And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 1s 870ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Oferta przelicytowana" 32s 316ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 109ms
After Hooks.deleteTransportAfterTest() 581ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 591ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 342ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 105ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 998ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 992ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 1m 53s 976ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 267ms
After Hooks.deleteTransportAfterTest() 571ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 481ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 369ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 075ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 996ms
And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 694ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 5s 330ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 064ms
After Hooks.deleteTransportAfterTest() 601ms
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 180ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 467ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 205ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" and finish of auction in "121" minutes 3s 129ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zakończenie aukcji" 1m 25s 858ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 300ms
After Hooks.deleteTransportAfterTest() 671ms
View Feature Discrepancy Report Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 091ms
And Prepare user "hochland-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 4s 405ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 205ms
And Go to "TRANSPORT_TABLE" 392ms
And Go to transport details "DELIVERY" 3s 378ms
And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 001ms
And Fill transport form 43s 290ms
And Open section: "discrepancy-report-panel" 1s 166ms
And Fill discrepancy report section 52s 465ms
And Go to transport details "DELIVERY" 2s 954ms
And Change filled value in details "rodo-acceptance" "checkbox" "true" "0" 1s 605ms
And Generate discrepancy report 22s 287ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Utworzono protokół niezgodności" 5s 854ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 3s 424ms
After Hooks.deleteTransportAfterTest() 967ms
View Feature Mode of transportation mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-bausch" 272ms
And Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file 3s 336ms
When Create default mode of transportation by API with "pba1-carrier" 798ms
Then Update mode of transportation by API with "pba1-carrier": "BBBB0000" "Model2" "Marka2" "CCCC0000" 402ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Środek transportu BBBB0000 został zaktualizowany" 10s 668ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 579ms
After Hooks.deleteModeOfTransportationAfterTest() 342ms
View Feature Mode of transportation mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-bausch" 241ms
And Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 975ms
When Create default mode of transportation by API with "pba1-carrier" 579ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowy środek transportu" 5s 352ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 534ms
After Hooks.deleteModeOfTransportationAfterTest() 311ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 9s 448ms
And Prepare user "pha2-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 136ms
And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 255ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 198ms
And Go to "WAREHOUSE_TAB" 1s 404ms
And Select warehouse "Serownia" 1s 649ms
And Set week view 1s 252ms
And Show yesterday 1s 176ms
And Move window into the past 401ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "spóźnił się na" 1m 454ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 343ms
After Hooks.deleteTransportAfterTest() 821ms
After Hooks.rollbackAddedAuthorities() 206ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 9s 947ms
And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 405ms
And Wait "60" seconds 1m
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 196ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica import" 38s 052ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 362ms
After Hooks.deleteTransportAfterTest() 600ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 588ms
And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 626ms
And Wait "60" seconds 1m
And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 207ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica eksport" 41s 804ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 151ms
After Hooks.deleteTransportAfterTest() 568ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 652ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 602ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 084ms
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ę" 6s 231ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 169ms
After Hooks.deleteTransportAfterTest() 761ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 670ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 334ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 085ms
And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 34s 847ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zostało przekazane nowe zlecenie" 5s 909ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 074ms
After Hooks.deleteTransportAfterTest() 530ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 542ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 268ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 167ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 3s 071ms
And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 1s 076ms
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 143ms
Then If user is login then logout 265ms
And Login as "swisskrono-admin" 2s 829ms
And Go to auction details 1s 864ms
And Pass transport to carrier from auction details 1s 584ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 26s 826ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 809ms
After Hooks.deleteTransportAfterTest() 836ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 886ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 3s 200ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 191ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 3s 024ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowe zapytanie ofertowe" 5s 354ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 764ms
After Hooks.deleteTransportAfterTest() 671ms
View Feature Remind password
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-adama" 219ms
And Prepare user "adama-admin" details with all notifications and "automaty10@o2.pl" by JSON file 1s 517ms
Then Send password remind email "automaty10@o2.pl" and check if status is ok 374ms
After Hooks.cleanUserDetailsAfterTest() 1s 380ms
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 671ms
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 465ms
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 "CONTAINER" created in transport table and set transport id 6s 940ms
When Click button advice in transport table "CONTAINER" 230ms
And Set advice window in schedule 3s 443ms
And Fill advice form 20s 273ms
And Click advice save button and wait for advice form to disappear 33s 253ms
And Go to "TRANSPORT_TABLE" 431ms
And Go to transport details "CONTAINER" 2s 925ms
Then Check are advice values equals 5s 017ms
After Hooks.cleanUserDetailsAfterTest() 2s 279ms
After Hooks.deleteTransportAfterTest() 779ms
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 777ms
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 369ms
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 "OWN_COLLECTION" created in transport table and set transport id 4s 125ms
When Click button advice in transport table "OWN_COLLECTION" 230ms
And Set advice window in schedule 3s 424ms
And Fill advice form 20s 445ms
And Click advice save button and wait for advice form to disappear 33s 313ms
And Go to "TRANSPORT_TABLE" 462ms
And Go to transport details "OWN_COLLECTION" 2s 947ms
Then Check are advice values equals 4s 981ms
After Hooks.cleanUserDetailsAfterTest() 2s 104ms
After Hooks.deleteTransportAfterTest() 805ms
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 340ms
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 391ms
And Add transport by SKApi in "MGW" assigned to "" 025ms
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 489ms
When Click button advice in transport table "TRANSPORT_ORDER" 237ms
And Set advice window in schedule 3s 402ms
And Fill advice form 20s 464ms
And Click advice save button and wait for advice form to disappear 33s 353ms
And Go to "TRANSPORT_TABLE" 511ms
And Go to transport details "TRANSPORT_ORDER" 2s 961ms
Then Check are advice values equals 4s 968ms
After Hooks.cleanUserDetailsAfterTest() 2s 285ms
After Hooks.deleteTransportAfterTest() 771ms
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 790ms
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 437ms
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 3s 979ms
When Click button advice in transport table "TRANSPORT_ORDER" 224ms
And Set advice window in schedule 3s 409ms
And Fill advice form 20s 335ms
And Click advice save button and wait for advice form to disappear 33s 240ms
And Go to "TRANSPORT_TABLE" 508ms
And Go to transport details "TRANSPORT_ORDER" 2s 866ms
Then Check are advice values equals 4s 960ms
After Hooks.cleanUserDetailsAfterTest() 2s 590ms
After Hooks.deleteTransportAfterTest() 833ms
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 699ms
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 575ms
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 5s 221ms
When Click button advice in transport table "TRANSPORT_ORDER" 268ms
And Set advice window in schedule 30s 160ms
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.kdJMZk}, 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: 4d8790a524584ba4b90814192eae0275
*** Element info: {Using=xpath, value=//button[@data-button-name='SHIFT_RIGHT_DAY']}
	at sun.reflect.GeneratedConstructorAccessor215.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:356)
	at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:458)
	at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
	at Pages.BasePage.getWebElementByXpath(BasePage.java:325)
	at CucumberTests.Transport.AdviceTransport.setAdviceWindowInSchedule(AdviceTransport.java:91)
	at ✽.Set advice window in schedule(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:13)
And Fill advice form 000ms
And Click advice save button and wait for advice form to disappear 000ms
And Go to "TRANSPORT_TABLE" 000ms
And Go to transport details "TRANSPORT_ORDER" 000ms
Then Check are advice values equals 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 766ms
After Hooks.deleteTransportAfterTest() 548ms
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 831ms
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 480ms
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 221ms
When Click button advice in transport table "OWN_COLLECTION" 224ms
And Set advice window in schedule 3s 550ms
And Fill advice form 20s 322ms
And Click advice save button and wait for advice form to disappear 33s 279ms
And Go to "TRANSPORT_TABLE" 449ms
Then Check advice data in SK API database "OWN_COLLECTION" 462ms
After Hooks.cleanUserDetailsAfterTest() 2s 102ms
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 488ms
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 392ms
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 "CONTAINER" created in transport table and set transport id 3s 912ms
When Click button advice in transport table "CONTAINER" 209ms
And Set advice window in schedule 3s 438ms
And Fill advice form 20s 440ms
And Click advice save button and wait for advice form to disappear 33s 376ms
And Go to "TRANSPORT_TABLE" 471ms
Then Check advice data in SK API database "CONTAINER" 242ms
After Hooks.cleanUserDetailsAfterTest() 2s 269ms
After Hooks.deleteTransportAfterTest() 849ms
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 673ms
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 380ms
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 "TRANSPORT_ORDER" created in transport table and set transport id 4s 322ms
When Click button advice in transport table "TRANSPORT_ORDER" 221ms
And Set advice window in schedule 3s 388ms
And Fill advice form 20s 470ms
And Click advice save button and wait for advice form to disappear 33s 242ms
And Go to "TRANSPORT_TABLE" 494ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 104ms
After Hooks.cleanUserDetailsAfterTest() 2s 198ms
After Hooks.deleteTransportAfterTest() 788ms
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 499ms
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 288ms
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 "TRANSPORT_ORDER" created in transport table and set transport id 4s 054ms
When Click button advice in transport table "TRANSPORT_ORDER" 227ms
And Set advice window in schedule 3s 443ms
And Fill advice form 20s 344ms
And Click advice save button and wait for advice form to disappear 33s 773ms
And Go to "TRANSPORT_TABLE" 532ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 093ms
After Hooks.cleanUserDetailsAfterTest() 2s 951ms
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 "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 8s 923ms
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 877ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 017ms
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 616ms
When Click button advice in transport table "TRANSPORT_ORDER" 211ms
And Set advice window in schedule 3s 416ms
And Fill advice form 20s 366ms
And Click advice save button and wait for advice form to disappear 33s 796ms
And Go to "TRANSPORT_TABLE" 502ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 262ms
After Hooks.cleanUserDetailsAfterTest() 1s 718ms
After Hooks.deleteTransportAfterTest() 773ms
View Feature Status rejection
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 4s 669ms
And Prepare user "lantmannen-guard" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 017ms
And Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 085ms
And Add access to the warehouse "Magazyn - Nowa Sól" to the user "lantmannen-guard" by JSON file 776ms
And Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 4s 626ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 860ms
And Check if reject date is not visible 15s 057ms
When Reject status: Book of disinfection 221ms
And Check if reject date is visible 998ms
Then If user is login then logout 259ms
And Login as "lantmannen-admin" 2s 590ms
And Check if note was added to transport after status rejection 1s 704ms
And Check if history note was added to transport after status rejection - "LOAD" 7s 361ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nieaktualna księga mycia i dezynfekcji" 2m 46s 773ms
And Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 286ms
After Hooks.deleteTransportAfterTest() 772ms
After Hooks.rollbackWarehousesAccess() 709ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skd" 226ms
And Prepare login page 476ms
And Click remind password button 270ms
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" 561ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Restart hasła! | Password reset!" 33s 245ms
And Extract password from mailgun mail 3s 960ms
And Reset password from link 1s 565ms
Then Check if alert is displayed "Hasło nie może być takie samo jak aktualne hasło użytkownika." in remind password page 227ms
After Hooks.cleanUserDetailsAfterTest() 957ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-adama" 249ms
And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_USERS_MAIN_DATA" to user "oaa1-receiver-2@qa.qa-test" 374ms
When Login as "oaa1-receiver-2@qa.qa-test" 4s 451ms
And Go to user "oaa1-receiver@qa.qa-test" details edition by prepared link 124ms
And Change user details "email" to "newEmailAddress@newEmail.com" 1s 158ms
And Change user details "phone" to "123456789" 478ms
Then Save user details 1s 014ms
And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 151ms
After Hooks.cleanUserDetailsAfterTest() 632ms
After Hooks.rollbackAddedAuthorities() 245ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 236ms
And Set basic authorities "ROLE_USERS_TAB;EDIT_USERS_NOTIFICATION" to user "pskza1-carrier-2@qa.qa-test" 213ms
When Login as "pskza1-carrier-2@qa.qa-test" 7s 379ms
And Go to user "pskza1-carrier@qa.qa-test" details edition by prepared link 094ms
And Expand "other" notification section 2s 463ms
And Select all notifications in "other" section 278ms
Then Save user details 1s 521ms
After Hooks.cleanUserDetailsAfterTest() 899ms
After Hooks.rollbackAddedAuthorities() 160ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
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" 460ms
And Set user details json of user "oaa1-receiver@qa.qa-test" 013ms
When Login as "adama-buyer@qa.qa-test" 5s 483ms
And Go to "USERS_TAB" 1s 562ms
And Find user "oaa1-receiver@qa.qa-test" 2s 758ms
And Change user details "email" to "newEmailAddress@newEmail.com" 992ms
And Change user details "phone" to "123456789" 432ms
Then Save user details 1s 034ms
And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 167ms
After Hooks.cleanUserDetailsAfterTest() 657ms
After Hooks.rollbackAddedAuthorities() 248ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 233ms
And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;EDIT_USERS_NOTIFICATION" to user "swisskrono-tradesman@qa.qa-test" 354ms
And Set user details json of user "pskza1-carrier@qa.qa-test" 009ms
When Login as "swisskrono-tradesman@qa.qa-test" 9s 349ms
And Go to "USERS_TAB" 1s 583ms
And Find user "pskza1-carrier@qa.qa-test" 2s 716ms
And Expand "GLUE_FACTORY" notification section 527ms
And Select all notifications in "GLUE_FACTORY" section 1s 385ms
Then Save user details 1s 788ms
After Hooks.cleanUserDetailsAfterTest() 1s 050ms
After Hooks.rollbackAddedAuthorities() 234ms