Project Number Date
ApolloFullRunnerReport 2021.AT1.57 12 sie 2021, 05:48

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@cleanUserDetailsAfterTest 423 4 11 0 0 438 41 4 45 47m 26s 575ms Failed
View Feature Invitation
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 098ms
And Delete invitations with email "automaty31415@test.pl" 016ms
Then Create invitation by JSON file "super-admin-alrec" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 699ms
And Prepare user "piast-admin" details with all notifications and "automaty31415@test.pl" by JSON file 195ms
When Login as "piast-admin" 1s 351ms
Then Go to "INVITATIONS_TAB" 207ms
And Go to invitation details 072ms
Then Reject invitation by button as user 108ms
When If user is login then logout 281ms
Then Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 1s 411ms
And Go to "INVITATIONS_TAB" 180ms
And Go to "REJECTED_TAB" invitation status tab 081ms
Then Invitation is displayed on list "automaty31415@test.pl" 152ms
After Hooks.deleteInvitationAfterTest() 024ms
After Hooks.cleanUserDetailsAfterTest() 168ms
View Feature Invitation
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-alrec" 095ms
And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "automatyy3333@test.pl" by JSON file 220ms
When Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 962ms
And Go to "INVITATIONS_TAB" 170ms
And Create invitation for "existing" user "SUPPLIER" "SUPPLIER" "automatyy3333@test.pl" "PL" 1s 163ms
And Wait "3" seconds 3s
Then Create invitation success alert is displayed 040ms
After Hooks.deleteInvitationAfterTest() 037ms
After Hooks.cleanUserDetailsAfterTest() 225ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 036ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 219ms
And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 219ms
And Get inputs from database "ADVICE_CONTAINER" "super-admin-adama" 037ms
And Show all transport types 1s 042ms
And Click button advice in transport table "CONTAINER" 094ms
And Set advice window in schedule 2s 474ms
And Fill advice form 13s 981ms
And Click advice save button and wait for advice form to disappear 30s 675ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!" 6s 702ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 100ms
After Hooks.cleanUserDetailsAfterTest() 191ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 235ms
And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 144ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 227ms
And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 037ms
And Show all transport types 1s 041ms
And Click button advice in transport table "DELIVERY" 104ms
And Set advice window in schedule 2s 635ms
And Fill advice form 10s 510ms
And Click advice save button and wait for advice form to disappear 30s 671ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!" 22s 828ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 106ms
After Hooks.cleanUserDetailsAfterTest() 163ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 228ms
And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 253ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 209ms
And Get inputs from database "ADVICE_LOAD" "super-admin-keeeper" 038ms
And Show all transport types 1s 044ms
And Click button advice in transport table "LOAD" 103ms
And Set advice window in schedule 2s 475ms
And Fill advice form 15s 364ms
And Click advice save button and wait for advice form to disappear 30s 674ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Time window has been saved!" 6s 086ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 094ms
After Hooks.cleanUserDetailsAfterTest() 206ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 538ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 204ms
And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 208ms
And Show all transport types 1s 038ms
And Create advice "ADVICE_CONTAINER" "CONTAINER" "super-admin-adama" 47s 167ms
And Go to "TRANSPORT_TABLE" 207ms
And Go to transport details "CONTAINER" 2s 448ms
And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 036ms
When Go to transport details "CONTAINER" 3s 186ms
And Fill transport form 4s 731ms
And Get inputs from database "EDIT_ADVICE_CONTAINER" "super-admin-adama" 037ms
And Expand advice panel 102ms
And Edit advice in transport details 14s 484ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 056ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 5s 506ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 100ms
After Hooks.cleanUserDetailsAfterTest() 197ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 600ms
And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 170ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 208ms
And Show all transport types 1s 042ms
And Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast" 43s 966ms
And Go to "TRANSPORT_TABLE" 224ms
And Go to transport details "DELIVERY" 2s 600ms
And Get inputs from database "EDIT_DELIVERY" "super-admin-piast" 038ms
When Go to transport details "DELIVERY" 3s 169ms
And Fill transport form 1m 2s 181ms
And Get inputs from database "EDIT_ADVICE_DELIVERY" "super-admin-piast" 038ms
And Expand advice panel 130ms
And Edit advice in transport details 6s 614ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 082ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 26s 487ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 130ms
After Hooks.cleanUserDetailsAfterTest() 173ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 638ms
And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 248ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 206ms
And Show all transport types 1s 041ms
And Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 48s 662ms
And Go to "TRANSPORT_TABLE" 183ms
And Go to transport details "LOAD" 2s 448ms
And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 041ms
When Go to transport details "LOAD" 3s 190ms
And Fill transport form 25s 983ms
And Get inputs from database "EDIT_ADVICE_LOAD" "super-admin-keeeper" 038ms
And Expand advice panel 120ms
And Edit advice in transport details 20s 629ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 128ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 32s 948ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 151ms
After Hooks.cleanUserDetailsAfterTest() 243ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skd" 095ms
And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 202ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 1s 340ms
And Confirm status "ARRIVAL" by Public API "v1" 302ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wjazd na teren zakładu" 10s 809ms
Then Check if user got a mail 000ms
And Confirm status "DEPARTURE" by Public API "v1" 251ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wyjazd" 37s 645ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 141ms
After Hooks.cleanUserDetailsAfterTest() 162ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-hochland" 094ms
And Prepare company "Dostawca Hochland Automat 1" verification email setting "48h" 036ms
And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 191ms
And Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "dha1-supplier-2@qa.qa-test" 2s 448ms
And Create transport "CREATE_DELIVERY" by JSON file as "dha1-supplier-2@qa.qa-test" 15s 339ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Weryfikacja danych awizacji" 1m 20s 367ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 100ms
After Hooks.cleanUserDetailsAfterTest() 230ms
After Hooks.rollbackVerificationEmailSettingAfterTest() 130ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 513ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 212ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 220ms
And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 539ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowa aukcja" 10s 765ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 114ms
After Hooks.cleanUserDetailsAfterTest() 294ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 152ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 320ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 255ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 140ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 500ms
And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 385ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 5s 480ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 080ms
After Hooks.cleanUserDetailsAfterTest() 262ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-producer" and set token of apiUsername "super-admin-skz" 2s 532ms
And Prepare user "swisskrono-producer" details with all notifications and "apolloautomattest@gmail.com" by JSON file 383ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 244ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 111ms
And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 190ms
And Wait till auction end 1m 58s 018ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Dodano nową ofertę" 2m 55s 256ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 121ms
After Hooks.cleanUserDetailsAfterTest() 354ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 392ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 217ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 253ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 161ms
And Wait till auction end 1m 58s 019ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Aukcja zakończona bez ofert" 5s 826ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 106ms
After Hooks.cleanUserDetailsAfterTest() 200ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 530ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 279ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 233ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 128ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 189ms
And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 319ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Oferta przelicytowana" 33s 110ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 084ms
After Hooks.cleanUserDetailsAfterTest() 283ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 166ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 333ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 233ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 140ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 176ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 1m 48s 881ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 084ms
After Hooks.cleanUserDetailsAfterTest() 295ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 162ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 325ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 225ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 117ms
And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 276ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 5s 320ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 075ms
After Hooks.cleanUserDetailsAfterTest() 267ms
View Feature Auctions Mail
Scenario Outline Check mail two hours before auction ends
Before Hooks.showScenarioName(Scenario) 000ms
Steps
Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 757ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 320ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 228ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" and finish of auction in "121" minutes 300ms
java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /auctions; status: 422, komunikat: [errors:[Termin zakończenia aukcji musi się znajdować w przyszłości]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Transport.AuctionTransport.setTransportOnAuction(AuctionTransport.java:54)
	at CucumberTests.Transport.AuctionTransport.setTransportOnAuctionByApiWith(AuctionTransport.java:71)
	at ✽.Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" and finish of auction in "121" minutes(file:Features/Atom/Mail/AuctionMail.feature:103)
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zakończenie aukcji" 000ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 062ms
After Hooks.cleanUserDetailsAfterTest() 288ms
View Feature Discrepancy Report Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 310ms
And Prepare user "hochland-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 651ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 464ms
And Go to "TRANSPORT_TABLE" 135ms
And Go to transport details "DELIVERY" 2s 775ms
And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 036ms
And Fill transport form 37s 906ms
And Open section: "discrepancy-report-panel" 1s 073ms
And Fill discrepancy report section 49s 520ms
And Go to transport details "DELIVERY" 2s 446ms
And Change filled value in details "rodo-acceptance" "checkbox" "true" "0" 1s 282ms
And Generate discrepancy report 18s 294ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Utworzono protokół niezgodności" 11s 969ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 131ms
After Hooks.cleanUserDetailsAfterTest() 444ms
View Feature Mode of transportation mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-bausch" 093ms
And Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file 428ms
When Create default mode of transportation by API with "pba1-carrier" 185ms
Then Update mode of transportation by API with "pba1-carrier": "BBBB0000" "Model2" "Marka2" "CCCC0000" 097ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Środek transportu BBBB0000 został zaktualizowany" 10s 378ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 330ms
After Hooks.deleteModeOfTransportationAfterTest() 087ms
View Feature Mode of transportation mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-bausch" 091ms
And Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file 341ms
When Create default mode of transportation by API with "pba1-carrier" 094ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowy środek transportu" 5s 521ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 337ms
After Hooks.deleteModeOfTransportationAfterTest() 050ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 508ms
And Prepare user "pha2-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 398ms
And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 028ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 452ms
And Go to "WAREHOUSE_TAB" 832ms
And Select warehouse "Serownia" 1s 409ms
And Set week view 1s 093ms
And Show yesterday 1s 060ms
And Move window into the past 292ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "spóźnił się na" 47s 894ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 121ms
After Hooks.cleanUserDetailsAfterTest() 308ms
After Hooks.rollbackAddedAuthorities() 023ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 221ms
And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 341ms
And Wait "60" seconds 1m
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 290ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica import" 11s 243ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 111ms
After Hooks.cleanUserDetailsAfterTest() 293ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 909ms
And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 355ms
And Wait "60" seconds 1m
And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 312ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica eksport" 38s 017ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 094ms
After Hooks.cleanUserDetailsAfterTest() 318ms
View Feature Transport Transfer Mail
Scenario Outline Check if mail was sent to carrier after transport transfer
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 156ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 354ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 238ms
And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 3s 738ms
java.lang.AssertionError: Formularz nie zniknął! Pojawił się błędy walidacji:
[Podana data nie może być w przeszłości]
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at Pages.Transport.TransportsPage.transferTransportToCarrier(TransportsPage.java:288)
	at CucumberTests.Transport.TransferTransportTest.transferTransportToCarrier(TransferTransportTest.java:37)
	at ✽.Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true"(file:Features/Atom/Mail/TransportTransferMail.feature:8)
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zlecenie czeka na akceptację" 000ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 100ms
After Hooks.cleanUserDetailsAfterTest() 261ms
View Feature Transport Transfer Mail
Scenario Outline Check if mail was sent to carrier after transport transfer with no confirmation
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 011ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 330ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 225ms
And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 3s 682ms
java.lang.AssertionError: Formularz nie zniknął! Pojawił się błędy walidacji:
[Podana data nie może być w przeszłości]
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at Pages.Transport.TransportsPage.transferTransportToCarrier(TransportsPage.java:288)
	at CucumberTests.Transport.TransferTransportTest.transferTransportToCarrier(TransferTransportTest.java:37)
	at ✽.Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false"(file:Features/Atom/Mail/TransportTransferMail.feature:20)
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zostało przekazane nowe zlecenie" 000ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 082ms
After Hooks.cleanUserDetailsAfterTest() 275ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 780ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 454ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 247ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 184ms
And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 214ms
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" 204ms
Then If user is login then logout 093ms
And Login as "swisskrono-admin" 1s 238ms
And Go to auction details 1s 216ms
And Pass transport to carrier from auction details 1s 272ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 2m 46s 701ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 185ms
After Hooks.cleanUserDetailsAfterTest() 343ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 296ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 453ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 248ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 125ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowe zapytanie ofertowe" 8s 061ms
Then Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 077ms
After Hooks.cleanUserDetailsAfterTest() 372ms
View Feature Remind password
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-adama" 095ms
And Prepare user "adama-admin" details with all notifications and "automaty10@o2.pl" by JSON file 205ms
Then Send password remind email "automaty10@o2.pl" and check if status is ok 158ms
After Hooks.cleanUserDetailsAfterTest() 192ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 122ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 381ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 037ms
And Add transport by SKApi in "MGW" assigned to "" 002ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 034ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 310ms
When Click button advice in transport table "CONTAINER" 082ms
And Set advice window in schedule 2s 601ms
And Fill advice form 16s 726ms
And Click advice save button and wait for advice form to disappear 30s 741ms
And Go to "TRANSPORT_TABLE" 220ms
And Go to transport details "CONTAINER" 2s 507ms
Then Check are advice values equals 4s 344ms
After Hooks.deleteTransportAfterTest() 127ms
After Hooks.cleanUserDetailsAfterTest() 282ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 937ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 345ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 038ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 384ms
When Click button advice in transport table "OWN_COLLECTION" 092ms
And Set advice window in schedule 2s 563ms
And Fill advice form 16s 775ms
And Click advice save button and wait for advice form to disappear 30s 705ms
And Go to "TRANSPORT_TABLE" 209ms
And Go to transport details "OWN_COLLECTION" 2s 477ms
Then Check are advice values equals 4s 324ms
After Hooks.deleteTransportAfterTest() 119ms
After Hooks.cleanUserDetailsAfterTest() 287ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 918ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 344ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 046ms
And Add transport by SKApi in "MGW" assigned to "" 004ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 036ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 806ms
When Click button advice in transport table "TRANSPORT_ORDER" 072ms
And Set advice window in schedule 2s 554ms
And Fill advice form 16s 853ms
And Click advice save button and wait for advice form to disappear 30s 765ms
And Go to "TRANSPORT_TABLE" 205ms
And Go to transport details "TRANSPORT_ORDER" 2s 445ms
Then Check are advice values equals 4s 337ms
After Hooks.deleteTransportAfterTest() 114ms
After Hooks.cleanUserDetailsAfterTest() 289ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 174ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 484ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 036ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 034ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 858ms
When Click button advice in transport table "TRANSPORT_ORDER" 097ms
And Set advice window in schedule 2s 589ms
And Fill advice form 16s 792ms
And Click advice save button and wait for advice form to disappear 30s 733ms
And Go to "TRANSPORT_TABLE" 214ms
And Go to transport details "TRANSPORT_ORDER" 2s 409ms
Then Check are advice values equals 4s 351ms
After Hooks.deleteTransportAfterTest() 119ms
After Hooks.cleanUserDetailsAfterTest() 371ms
View Feature SK Api - Advice transport
Scenario Outline Check if it possible to advice transport when transport is created by sk API
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 873ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 273ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 038ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 902ms
When Click button advice in transport table "TRANSPORT_ORDER" 085ms
And Set advice window in schedule 30s 066ms
org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//button[@data-button-name='SHIFT_RIGHT_DAY']"}
  (Session info: headless chrome=92.0.4515.131)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.kB5mLg}, 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: 1337ddc814c7369f7f040b306e3b9bab
*** 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:323)
	at CucumberTests.Transport.AdviceTransport.setAdviceWindowInSchedule(AdviceTransport.java:91)
	at ✽.Set advice window in schedule(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:13)
And Fill advice form 000ms
And Click advice save button and wait for advice form to disappear 000ms
And Go to "TRANSPORT_TABLE" 000ms
And Go to transport details "TRANSPORT_ORDER" 000ms
Then Check are advice values equals 000ms
After Hooks.deleteTransportAfterTest() 058ms
After Hooks.cleanUserDetailsAfterTest() 240ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 892ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 358ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 038ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 379ms
When Click button advice in transport table "OWN_COLLECTION" 081ms
And Set advice window in schedule 2s 579ms
And Fill advice form 16s 739ms
And Click advice save button and wait for advice form to disappear 30s 712ms
And Go to "TRANSPORT_TABLE" 198ms
Then Check advice data in SK API database "OWN_COLLECTION" 138ms
After Hooks.deleteTransportAfterTest() 108ms
After Hooks.cleanUserDetailsAfterTest() 283ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 869ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 323ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 038ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 036ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 360ms
When Click button advice in transport table "CONTAINER" 097ms
And Set advice window in schedule 2s 544ms
And Fill advice form 16s 709ms
And Click advice save button and wait for advice form to disappear 30s 682ms
And Go to "TRANSPORT_TABLE" 208ms
Then Check advice data in SK API database "CONTAINER" 094ms
After Hooks.deleteTransportAfterTest() 119ms
After Hooks.cleanUserDetailsAfterTest() 287ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 827ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 328ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 038ms
And Add transport by SKApi in "MGW" assigned to "" 002ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 814ms
When Click button advice in transport table "TRANSPORT_ORDER" 088ms
And Set advice window in schedule 2s 557ms
And Fill advice form 16s 803ms
And Click advice save button and wait for advice form to disappear 30s 786ms
And Go to "TRANSPORT_TABLE" 217ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 039ms
After Hooks.deleteTransportAfterTest() 089ms
After Hooks.cleanUserDetailsAfterTest() 284ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 731ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 449ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 038ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 034ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 1s 131ms
When Click button advice in transport table "TRANSPORT_ORDER" 099ms
And Set advice window in schedule 2s 594ms
And Fill advice form 16s 717ms
And Click advice save button and wait for advice form to disappear 30s 724ms
And Go to "TRANSPORT_TABLE" 252ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 035ms
After Hooks.deleteTransportAfterTest() 130ms
After Hooks.cleanUserDetailsAfterTest() 357ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Before Hooks.showScenarioName(Scenario) 002ms
Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 038ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 274ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 036ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 034ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 2s 934ms
When Click button advice in transport table "TRANSPORT_ORDER" 076ms
And Set advice window in schedule 2s 559ms
And Fill advice form 16s 839ms
And Click advice save button and wait for advice form to disappear 30s 719ms
And Go to "TRANSPORT_TABLE" 192ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 094ms
After Hooks.deleteTransportAfterTest() 098ms
After Hooks.cleanUserDetailsAfterTest() 219ms
View Feature Status rejection
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 310ms
And Prepare user "lantmannen-guard" details with all notifications and "apolloautomattest@gmail.com" by JSON file 261ms
And Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 176ms
And Add access to the warehouse "Magazyn - Nowa Sól" to the user "lantmannen-guard" by JSON file 135ms
And Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 1s 227ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 321ms
And Check if reject date is not visible 15s 010ms
When Reject status: Book of disinfection 088ms
And Check if reject date is visible 306ms
Then If user is login then logout 318ms
And Login as "lantmannen-admin" 862ms
And Check if note was added to transport after status rejection 1s 249ms
And Check if history note was added to transport after status rejection - "LOAD" 3s 569ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nieaktualna księga mycia i dezynfekcji" 2m 59s 659ms
And Check if user got a mail 000ms
After Hooks.deleteTransportAfterTest() 114ms
After Hooks.cleanUserDetailsAfterTest() 183ms
After Hooks.rollbackWarehousesAccess() 122ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skd" 093ms
And Prepare login page 198ms
And Click remind password button 085ms
And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 160ms
And Send remind password form with email "apolloautomattest@gmail.com" 176ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Restart hasła! | Password reset!" 31s 495ms
And Extract password from mailgun mail 3s 749ms
And Reset password from link 674ms
Then Check if alert is displayed "Hasło nie może być takie samo jak aktualne hasło użytkownika." in remind password page 145ms
After Hooks.cleanUserDetailsAfterTest() 161ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-adama" 096ms
And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_USERS_MAIN_DATA" to user "oaa1-receiver-2@qa.qa-test" 071ms
When Login as "oaa1-receiver-2@qa.qa-test" 1s 256ms
And Go to user "oaa1-receiver@qa.qa-test" details edition by prepared link 019ms
And Change user details "email" to "newEmailAddress@newEmail.com" 262ms
And Change user details "phone" to "123456789" 148ms
Then Save user details 256ms
And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 055ms
After Hooks.cleanUserDetailsAfterTest() 100ms
After Hooks.rollbackAddedAuthorities() 042ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 096ms
And Set basic authorities "ROLE_USERS_TAB;EDIT_USERS_NOTIFICATION" to user "pskza1-carrier-2@qa.qa-test" 025ms
When Login as "pskza1-carrier-2@qa.qa-test" 1s 792ms
And Go to user "pskza1-carrier@qa.qa-test" details edition by prepared link 031ms
And Expand "other" notification section 432ms
And Select all notifications in "other" section 092ms
Then Save user details 406ms
After Hooks.cleanUserDetailsAfterTest() 136ms
After Hooks.rollbackAddedAuthorities() 022ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-adama" 095ms
And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;ROLE_EDIT_USERS_MAIN_DATA" to user "adama-buyer@qa.qa-test" 065ms
And Set user details json of user "oaa1-receiver@qa.qa-test" 000ms
When Login as "adama-buyer@qa.qa-test" 1s 375ms
And Go to "USERS_TAB" 919ms
And Find user "oaa1-receiver@qa.qa-test" 2s 278ms
And Change user details "email" to "newEmailAddress@newEmail.com" 243ms
And Change user details "phone" to "123456789" 139ms
Then Save user details 249ms
And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 050ms
After Hooks.cleanUserDetailsAfterTest() 114ms
After Hooks.rollbackAddedAuthorities() 036ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 093ms
And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;EDIT_USERS_NOTIFICATION" to user "swisskrono-tradesman@qa.qa-test" 048ms
And Set user details json of user "pskza1-carrier@qa.qa-test" 000ms
When Login as "swisskrono-tradesman@qa.qa-test" 1s 987ms
And Go to "USERS_TAB" 737ms
And Find user "pskza1-carrier@qa.qa-test" 2s 242ms
And Expand "GLUE_FACTORY" notification section 264ms
And Select all notifications in "GLUE_FACTORY" section 511ms
Then Save user details 543ms
After Hooks.cleanUserDetailsAfterTest() 151ms
After Hooks.rollbackAddedAuthorities() 037ms