Project Number Date
ApolloFullRunnerReport apollo-test-2.125 20 sie 2021, 05:38

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@cleanUserDetailsAfterTest 417 3 18 0 0 438 42 3 45 52m 45s 184ms Failed
View Feature Invitation
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 219ms
And Delete invitations with email "automaty31415@test.pl" 097ms
Then Create invitation by JSON file "super-admin-alrec" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 426ms
And Prepare user "piast-admin" details with all notifications and "automaty31415@test.pl" by JSON file 1s 393ms
When Login as "piast-admin" 5s 110ms
Then Go to "INVITATIONS_TAB" 728ms
And Go to invitation details 146ms
Then Reject invitation by button as user 304ms
When If user is login then logout 303ms
Then Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 4s 996ms
And Go to "INVITATIONS_TAB" 507ms
And Go to "REJECTED_TAB" invitation status tab 339ms
Then Invitation is displayed on list "automaty31415@test.pl" 441ms
After Hooks.deleteInvitationAfterTest() 186ms
After Hooks.cleanUserDetailsAfterTest() 1s 247ms
View Feature Invitation
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-alrec" 229ms
And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "automatyy3333@test.pl" by JSON file 1s 676ms
When Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 2s 358ms
And Go to "INVITATIONS_TAB" 521ms
And Create invitation for "existing" user "SUPPLIER" "SUPPLIER" "automatyy3333@test.pl" "PL" 2s 753ms
And Wait "3" seconds 3s
Then Create invitation success alert is displayed 112ms
After Hooks.deleteInvitationAfterTest() 195ms
After Hooks.cleanUserDetailsAfterTest() 1s 301ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 416ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 069ms
And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 2s 154ms
And Set "advice" inputs from JSON file "ADVICE_CONTAINER" "super-admin-adama" 002ms
And Show all transport types 1s 154ms
And Click button advice in transport table "CONTAINER" 224ms
And Set advice window in schedule 3s 340ms
And Fill advice form 16s 988ms
And Click advice save button and wait for advice form to disappear 33s 880ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!" 5s 840ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 286ms
After Hooks.deleteTransportAfterTest() 743ms
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 767ms
And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 226ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 997ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 001ms
And Show all transport types 1s 192ms
And Click button advice in transport table "DELIVERY" 247ms
And Set advice window in schedule 3s 447ms
And Fill advice form 13s 047ms
And Click advice save button and wait for advice form to disappear 10s 871ms
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.vEGcDT}, 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: a49ddeab5d6912da551cc3077a4ae0a5
	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 079ms
After Hooks.deleteTransportAfterTest() 548ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 480ms
And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 703ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 2s 006ms
And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-keeeper" 001ms
And Show all transport types 1s 159ms
And Click button advice in transport table "LOAD" 262ms
And Set advice window in schedule 3s 275ms
And Fill advice form 18s 859ms
And Click advice save button and wait for advice form to disappear 33s 268ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Time window has been saved!" 11s 822ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 459ms
After Hooks.deleteTransportAfterTest() 761ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 056ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 459ms
And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 905ms
And Show all transport types 1s 147ms
And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-adama" 3s 294ms
And Go to "TRANSPORT_TABLE" 405ms
And Go to transport details "CONTAINER" 2s 950ms
And Set "transport" inputs from JSON file "EDIT_CONTAINER" "super-admin-adama" 001ms
When Go to transport details "CONTAINER" 3s 534ms
And Fill transport form 5s 245ms
And Set "advice" inputs from JSON file "EDIT_ADVICE_CONTAINER" "super-admin-adama" 002ms
And Expand advice panel 275ms
And Edit advice in transport details 17s 704ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 275ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 5s 510ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 255ms
After Hooks.deleteTransportAfterTest() 753ms
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 445ms
And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 153ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 957ms
And Show all transport types 1s 150ms
And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 1s 735ms
java.lang.AssertionError: Nieoczekiwany błąd podczas żądania PUT pod adresem /transports/228129876 - 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 093ms
After Hooks.deleteTransportAfterTest() 612ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 5s 438ms
And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 747ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 967ms
And Show all transport types 1s 152ms
And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD" as "super-admin-keeeper" 3s 347ms
And Go to "TRANSPORT_TABLE" 367ms
And Go to transport details "LOAD" 2s 957ms
And Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-keeeper" 001ms
When Go to transport details "LOAD" 3s 519ms
And Fill transport form 28s 780ms
And Set "advice" inputs from JSON file "EDIT_ADVICE_LOAD" "super-admin-keeeper" 001ms
And Expand advice panel 242ms
And Edit advice in transport details 23s 494ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 248ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 2m 48s 848ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 696ms
After Hooks.deleteTransportAfterTest() 806ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skd" 227ms
And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 436ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 2s 777ms
And Confirm status "ARRIVAL" by Public API "v1" 1s 298ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wjazd na teren zakładu" 10s 531ms
Then Check if user got a mail 000ms
And Confirm status "DEPARTURE" by Public API "v1" 1s 302ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wyjazd" 36s 359ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 970ms
After Hooks.deleteTransportAfterTest() 794ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-hochland" 244ms
And Prepare company "Dostawca Hochland Automat 1" verification email setting "48h" 201ms
And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 121ms
And Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "dha1-supplier-2@qa.qa-test" 8s 924ms
And Create transport "CREATE_DELIVERY" by JSON file as "dha1-supplier-2@qa.qa-test" 16s 844ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Weryfikacja danych awizacji" 1m 42s 815ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 711ms
After Hooks.deleteTransportAfterTest() 747ms
After Hooks.rollbackVerificationEmailSettingAfterTest() 427ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 942ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 201ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 157ms
And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 3s 495ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowa aukcja" 5s 402ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 069ms
After Hooks.deleteTransportAfterTest() 772ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 465ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 382ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 067ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 008ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 310ms
And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 1s 890ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 5s 352ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 139ms
After Hooks.deleteTransportAfterTest() 621ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-producer" and set token of apiUsername "super-admin-skz" 12s 251ms
And Prepare user "swisskrono-producer" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 514ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 123ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 839ms
And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 994ms
And Wait till auction end 1m 57s 016ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Dodano nową ofertę" 3m 8s 698ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 355ms
After Hooks.deleteTransportAfterTest() 616ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 837ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 540ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 103ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 958ms
And Wait till auction end 1m 58s 016ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Aukcja zakończona bez ofert" 5s 488ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 362ms
After Hooks.deleteTransportAfterTest() 650ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 920ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 344ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 126ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 021ms
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 792ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Oferta przelicytowana" 37s 239ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 098ms
After Hooks.deleteTransportAfterTest() 616ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 483ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 379ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 079ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 997ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 002ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 2m 1s 610ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 281ms
After Hooks.deleteTransportAfterTest() 556ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 538ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 315ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 087ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 991ms
And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 645ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 5s 182ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 046ms
After Hooks.deleteTransportAfterTest() 602ms
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 215ms
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 107ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" and finish of auction in "121" minutes 3s 016ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zakończenie aukcji" 25s 981ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 052ms
After Hooks.deleteTransportAfterTest() 666ms
View Feature Discrepancy Report Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 064ms
And Prepare user "hochland-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 4s 224ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 109ms
And Go to "TRANSPORT_TABLE" 390ms
And Go to transport details "DELIVERY" 2s 957ms
And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 001ms
And Fill transport form 43s 257ms
And Open section: "discrepancy-report-panel" 1s 161ms
And Fill discrepancy report section 52s 661ms
And Go to transport details "DELIVERY" 2s 889ms
And Change filled value in details "rodo-acceptance" "checkbox" "true" "0" 1s 590ms
And Generate discrepancy report 21s 619ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Utworzono protokół niezgodności" 5s 654ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 3s 347ms
After Hooks.deleteTransportAfterTest() 888ms
View Feature Mode of transportation mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-bausch" 242ms
And Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file 3s 188ms
When Create default mode of transportation by API with "pba1-carrier" 714ms
Then Update mode of transportation by API with "pba1-carrier": "BBBB0000" "Model2" "Marka2" "CCCC0000" 355ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Środek transportu BBBB0000 został zaktualizowany" 10s 425ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 491ms
After Hooks.deleteModeOfTransportationAfterTest() 334ms
View Feature Mode of transportation mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-bausch" 239ms
And Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 821ms
When Create default mode of transportation by API with "pba1-carrier" 582ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowy środek transportu" 5s 207ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 464ms
After Hooks.deleteModeOfTransportationAfterTest() 303ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 9s 357ms
And Prepare user "pha2-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 130ms
And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 229ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 154ms
And Go to "WAREHOUSE_TAB" 1s 338ms
And Select warehouse "Serownia" 1s 541ms
And Set week view 1s 239ms
And Show yesterday 1s 163ms
And Move window into the past 422ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "spóźnił się na" 36s 676ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 343ms
After Hooks.deleteTransportAfterTest() 798ms
After Hooks.rollbackAddedAuthorities() 159ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 9s 355ms
And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 454ms
And Wait "60" seconds 1m
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 188ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica import" 44s 411ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 139ms
After Hooks.deleteTransportAfterTest() 556ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 489ms
And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 379ms
And Wait "60" seconds 1m
And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 156ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica eksport" 47s 532ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 160ms
After Hooks.deleteTransportAfterTest() 649ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 617ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 465ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 982ms
And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 34s 754ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zlecenie czeka na akceptację" 5s 491ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 060ms
After Hooks.deleteTransportAfterTest() 800ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 685ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 289ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 096ms
And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 34s 974ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zostało przekazane nowe zlecenie" 5s 502ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 071ms
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 709ms
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 201ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 3s 051ms
And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 1s 068ms
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 156ms
Then If user is login then logout 274ms
And Login as "swisskrono-admin" 2s 805ms
And Go to auction details 1s 859ms
And Pass transport to carrier from auction details 1s 582ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 31s 210ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 771ms
After Hooks.deleteTransportAfterTest() 869ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 761ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 3s 127ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 132ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 966ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowe zapytanie ofertowe" 5s 183ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 732ms
After Hooks.deleteTransportAfterTest() 657ms
View Feature Remind password
Before Hooks.showScenarioName(Scenario) 000ms
Given Set token of apiUsername "super-admin-adama" 220ms
And Prepare user "adama-admin" details with all notifications and "automaty10@o2.pl" by JSON file 1s 549ms
Then Send password remind email "automaty10@o2.pl" and check if status is ok 347ms
After Hooks.cleanUserDetailsAfterTest() 1s 332ms
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 575ms
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 395ms
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 931ms
When Click button advice in transport table "CONTAINER" 240ms
And Set advice window in schedule 3s 413ms
And Fill advice form 20s 489ms
And Click advice save button and wait for advice form to disappear 33s 233ms
And Go to "TRANSPORT_TABLE" 457ms
And Go to transport details "CONTAINER" 2s 944ms
Then Check are advice values equals 4s 995ms
After Hooks.cleanUserDetailsAfterTest() 2s 265ms
After Hooks.deleteTransportAfterTest() 775ms
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 486ms
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 358ms
And Add transport by SKApi in "MGW" assigned to "" 016ms
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 183ms
When Click button advice in transport table "OWN_COLLECTION" 246ms
And Set advice window in schedule 3s 374ms
And Fill advice form 20s 311ms
And Click advice save button and wait for advice form to disappear 33s 260ms
And Go to "TRANSPORT_TABLE" 500ms
And Go to transport details "OWN_COLLECTION" 2s 921ms
Then Check are advice values equals 4s 955ms
After Hooks.cleanUserDetailsAfterTest() 2s 134ms
After Hooks.deleteTransportAfterTest() 774ms
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 400ms
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 372ms
And Add transport by SKApi in "MGW" assigned to "" 022ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 354ms
When Click button advice in transport table "TRANSPORT_ORDER" 216ms
And Set advice window in schedule 3s 482ms
And Fill advice form 20s 491ms
And Click advice save button and wait for advice form to disappear 33s 236ms
And Go to "TRANSPORT_TABLE" 480ms
And Go to transport details "TRANSPORT_ORDER" 2s 946ms
Then Check are advice values equals 4s 956ms
After Hooks.cleanUserDetailsAfterTest() 2s 272ms
After Hooks.deleteTransportAfterTest() 831ms
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 572ms
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 "" 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 742ms
When Click button advice in transport table "TRANSPORT_ORDER" 236ms
And Set advice window in schedule 3s 480ms
And Fill advice form 20s 449ms
And Click advice save button and wait for advice form to disappear 33s 299ms
And Go to "TRANSPORT_TABLE" 535ms
And Go to transport details "TRANSPORT_ORDER" 2s 961ms
Then Check are advice values equals 5s 008ms
After Hooks.cleanUserDetailsAfterTest() 2s 734ms
After Hooks.deleteTransportAfterTest() 767ms
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 386ms
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 710ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 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 586ms
When Click button advice in transport table "TRANSPORT_ORDER" 230ms
And Set advice window in schedule 30s 145ms
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.vEGcDT}, 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: a49ddeab5d6912da551cc3077a4ae0a5
*** 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 740ms
After Hooks.deleteTransportAfterTest() 533ms
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 551ms
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 375ms
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 "OWN_COLLECTION" created in transport table and set transport id 7s 147ms
When Click button advice in transport table "OWN_COLLECTION" 242ms
And Set advice window in schedule 3s 370ms
And Fill advice form 20s 480ms
And Click advice save button and wait for advice form to disappear 33s 186ms
And Go to "TRANSPORT_TABLE" 459ms
Then Check advice data in SK API database "OWN_COLLECTION" 411ms
After Hooks.cleanUserDetailsAfterTest() 2s 067ms
After Hooks.deleteTransportAfterTest() 802ms
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 259ms
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 368ms
And Add transport by SKApi in "MGW" assigned to "" 019ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 950ms
When Click button advice in transport table "CONTAINER" 220ms
And Set advice window in schedule 3s 370ms
And Fill advice form 20s 601ms
And Click advice save button and wait for advice form to disappear 33s 275ms
And Go to "TRANSPORT_TABLE" 450ms
Then Check advice data in SK API database "CONTAINER" 244ms
After Hooks.cleanUserDetailsAfterTest() 2s 298ms
After Hooks.deleteTransportAfterTest() 796ms
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 722ms
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 486ms
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 7s 234ms
When Click button advice in transport table "TRANSPORT_ORDER" 215ms
And Set advice window in schedule 3s 434ms
And Fill advice form 20s 494ms
And Click advice save button and wait for advice form to disappear 33s 298ms
And Go to "TRANSPORT_TABLE" 497ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 100ms
After Hooks.cleanUserDetailsAfterTest() 2s 132ms
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 "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 6s 343ms
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 294ms
And Add transport by SKApi in "MGW" assigned to "" 027ms
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 718ms
When Click button advice in transport table "TRANSPORT_ORDER" 223ms
And Set advice window in schedule 3s 374ms
And Fill advice form 20s 374ms
And Click advice save button and wait for advice form to disappear 33s 349ms
And Go to "TRANSPORT_TABLE" 533ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 095ms
After Hooks.cleanUserDetailsAfterTest() 2s 947ms
After Hooks.deleteTransportAfterTest() 819ms
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 788ms
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 886ms
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 7s 595ms
When Click button advice in transport table "TRANSPORT_ORDER" 220ms
And Set advice window in schedule 3s 408ms
And Fill advice form 20s 336ms
And Click advice save button and wait for advice form to disappear 33s 872ms
And Go to "TRANSPORT_TABLE" 465ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 266ms
After Hooks.cleanUserDetailsAfterTest() 1s 697ms
After Hooks.deleteTransportAfterTest() 800ms
View Feature Status rejection
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 4s 686ms
And Prepare user "lantmannen-guard" details with all notifications and "apolloautomattest@gmail.com" by JSON file 910ms
And Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 048ms
And Add access to the warehouse "Magazyn - Nowa Sól" to the user "lantmannen-guard" by JSON file 728ms
And Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 4s 459ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 861ms
And Check if reject date is not visible 15s 060ms
When Reject status: Book of disinfection 216ms
And Check if reject date is visible 1s 292ms
Then If user is login then logout 625ms
And Login as "lantmannen-admin" 2s 058ms
And Check if note was added to transport after status rejection 1s 720ms
And Check if history note was added to transport after status rejection - "LOAD" 7s 274ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nieaktualna księga mycia i dezynfekcji" 2m 47s 121ms
And Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 226ms
After Hooks.deleteTransportAfterTest() 755ms
After Hooks.rollbackWarehousesAccess() 777ms
Before Hooks.showScenarioName(Scenario) 000ms
Given Set token of apiUsername "super-admin-skd" 228ms
And Prepare login page 463ms
And Click remind password button 278ms
And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 010ms
And Send remind password form with email "apolloautomattest@gmail.com" 565ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Restart hasła! | Password reset!" 38s 112ms
And Extract password from mailgun mail 4s 431ms
And Reset password from link 1s 627ms
Then Check if alert is displayed "Hasło nie może być takie samo jak aktualne hasło użytkownika." in remind password page 225ms
After Hooks.cleanUserDetailsAfterTest() 966ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-adama" 242ms
And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_USERS_MAIN_DATA" to user "oaa1-receiver-2@qa.qa-test" 359ms
When Login as "oaa1-receiver-2@qa.qa-test" 4s 397ms
And Go to user "oaa1-receiver@qa.qa-test" details edition by prepared link 166ms
And Change user details "email" to "newEmailAddress@newEmail.com" 1s 073ms
And Change user details "phone" to "123456789" 425ms
Then Save user details 984ms
And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 171ms
After Hooks.cleanUserDetailsAfterTest() 677ms
After Hooks.rollbackAddedAuthorities() 304ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 232ms
And Set basic authorities "ROLE_USERS_TAB;EDIT_USERS_NOTIFICATION" to user "pskza1-carrier-2@qa.qa-test" 206ms
When Login as "pskza1-carrier-2@qa.qa-test" 7s 219ms
And Go to user "pskza1-carrier@qa.qa-test" details edition by prepared link 099ms
And Expand "other" notification section 2s 600ms
And Select all notifications in "other" section 266ms
Then Save user details 1s 505ms
After Hooks.cleanUserDetailsAfterTest() 938ms
After Hooks.rollbackAddedAuthorities() 151ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-adama" 230ms
And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;ROLE_EDIT_USERS_MAIN_DATA" to user "adama-buyer@qa.qa-test" 431ms
And Set user details json of user "oaa1-receiver@qa.qa-test" 013ms
When Login as "adama-buyer@qa.qa-test" 5s 175ms
And Go to "USERS_TAB" 1s 472ms
And Find user "oaa1-receiver@qa.qa-test" 2s 681ms
And Change user details "email" to "newEmailAddress@newEmail.com" 815ms
And Change user details "phone" to "123456789" 460ms
Then Save user details 1s 052ms
And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 164ms
After Hooks.cleanUserDetailsAfterTest() 663ms
After Hooks.rollbackAddedAuthorities() 236ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 226ms
And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;EDIT_USERS_NOTIFICATION" to user "swisskrono-tradesman@qa.qa-test" 358ms
And Set user details json of user "pskza1-carrier@qa.qa-test" 009ms
When Login as "swisskrono-tradesman@qa.qa-test" 9s 336ms
And Go to "USERS_TAB" 1s 603ms
And Find user "pskza1-carrier@qa.qa-test" 2s 699ms
And Expand "GLUE_FACTORY" notification section 542ms
And Select all notifications in "GLUE_FACTORY" section 1s 426ms
Then Save user details 2s 110ms
After Hooks.cleanUserDetailsAfterTest() 1s 042ms
After Hooks.rollbackAddedAuthorities() 248ms