Project Number Date
ApolloFullRunnerReport apollo-test-2.114 12 sie 2021, 06:02

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@cleanUserDetailsAfterTest 420 5 13 0 0 438 40 5 45 53m 31s 551ms Failed
View Feature Invitation
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 230ms
And Delete invitations with email "automaty31415@test.pl" 100ms
Then Create invitation by JSON file "super-admin-alrec" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 420ms
And Prepare user "piast-admin" details with all notifications and "automaty31415@test.pl" by JSON file 1s 381ms
When Login as "piast-admin" 4s 969ms
Then Go to "INVITATIONS_TAB" 633ms
And Go to invitation details 149ms
Then Reject invitation by button as user 327ms
When If user is login then logout 5s 893ms
Then Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 4s 984ms
And Go to "INVITATIONS_TAB" 519ms
And Go to "REJECTED_TAB" invitation status tab 338ms
Then Invitation is displayed on list "automaty31415@test.pl" 475ms
After Hooks.deleteInvitationAfterTest() 178ms
After Hooks.cleanUserDetailsAfterTest() 1s 352ms
View Feature Invitation
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-alrec" 233ms
And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "automatyy3333@test.pl" by JSON file 1s 650ms
When Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 2s 395ms
And Go to "INVITATIONS_TAB" 490ms
And Create invitation for "existing" user "SUPPLIER" "SUPPLIER" "automatyy3333@test.pl" "PL" 2s 733ms
And Wait "3" seconds 3s
Then Create invitation success alert is displayed 119ms
After Hooks.deleteInvitationAfterTest() 197ms
After Hooks.cleanUserDetailsAfterTest() 1s 278ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 438ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 445ms
And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 2s 191ms
And Get inputs from database "ADVICE_CONTAINER" "super-admin-adama" 021ms
And Show all transport types 1s 163ms
And Click button advice in transport table "CONTAINER" 226ms
And Set advice window in schedule 3s 414ms
And Fill advice form 17s 150ms
And Click advice save button and wait for advice form to disappear 33s 820ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!" 5s 633ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 273ms
After Hooks.deleteTransportAfterTest() 824ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 749ms
And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 910ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 087ms
And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 023ms
And Show all transport types 1s 157ms
And Click button advice in transport table "DELIVERY" 262ms
And Set advice window in schedule 3s 442ms
And Fill advice form 13s 016ms
And Click advice save button and wait for advice form to disappear 33s 306ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!" 5s 834ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 066ms
After Hooks.deleteTransportAfterTest() 784ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 606ms
And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 687ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 2s 014ms
And Get inputs from database "ADVICE_LOAD" "super-admin-keeeper" 021ms
And Show all transport types 1s 175ms
And Click button advice in transport table "LOAD" 258ms
And Set advice window in schedule 3s 267ms
And Fill advice form 18s 656ms
And Click advice save button and wait for advice form to disappear 33s 315ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Time window has been saved!" 5s 885ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 467ms
After Hooks.deleteTransportAfterTest() 745ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 047ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 448ms
And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 896ms
And Show all transport types 1s 169ms
And Create advice "ADVICE_CONTAINER" "CONTAINER" "super-admin-adama" 53s 758ms
And Go to "TRANSPORT_TABLE" 488ms
And Go to transport details "CONTAINER" 2s 826ms
And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 020ms
When Go to transport details "CONTAINER" 3s 523ms
And Fill transport form 5s 167ms
And Get inputs from database "EDIT_ADVICE_CONTAINER" "super-admin-adama" 023ms
And Expand advice panel 273ms
And Edit advice in transport details 17s 513ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 260ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 34s 003ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 389ms
After Hooks.deleteTransportAfterTest() 741ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 5s 796ms
And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 219ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 022ms
And Show all transport types 1s 173ms
And Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast" 50s 275ms
And Go to "TRANSPORT_TABLE" 511ms
And Go to transport details "DELIVERY" 2s 875ms
And Get inputs from database "EDIT_DELIVERY" "super-admin-piast" 022ms
When Go to transport details "DELIVERY" 3s 725ms
And Fill transport form 1m 8s 806ms
And Get inputs from database "EDIT_ADVICE_DELIVERY" "super-admin-piast" 021ms
And Expand advice panel 270ms
And Edit advice in transport details 8s 090ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 208ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 33s 391ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 121ms
After Hooks.deleteTransportAfterTest() 921ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 5s 865ms
And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 708ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 977ms
And Show all transport types 1s 162ms
And Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 55s 433ms
And Go to "TRANSPORT_TABLE" 440ms
And Go to transport details "LOAD" 2s 817ms
And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 022ms
When Go to transport details "LOAD" 3s 514ms
And Fill transport form 28s 814ms
And Get inputs from database "EDIT_ADVICE_LOAD" "super-admin-keeeper" 021ms
And Expand advice panel 239ms
And Edit advice in transport details 23s 737ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 277ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 41s 392ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 643ms
After Hooks.deleteTransportAfterTest() 821ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skd" 233ms
And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 245ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 2s 737ms
And Confirm status "ARRIVAL" by Public API "v1" 1s 142ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wjazd na teren zakładu" 22s 309ms
Then Check if user got a mail 000ms
And Confirm status "DEPARTURE" by Public API "v1" 1s 263ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wyjazd" 28s 952ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 960ms
After Hooks.deleteTransportAfterTest() 803ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-hochland" 236ms
And Prepare company "Dostawca Hochland Automat 1" verification email setting "48h" 207ms
And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 119ms
And Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "dha1-supplier-2@qa.qa-test" 8s 957ms
And Create transport "CREATE_DELIVERY" by JSON file as "dha1-supplier-2@qa.qa-test" 16s 886ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Weryfikacja danych awizacji" 1m 20s 727ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 683ms
After Hooks.deleteTransportAfterTest() 724ms
After Hooks.rollbackVerificationEmailSettingAfterTest() 421ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 806ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 221ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 205ms
And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 3s 704ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowa aukcja" 10s 880ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 033ms
After Hooks.deleteTransportAfterTest() 685ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 448ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 265ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 132ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 024ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 433ms
And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 1s 897ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 13s 710ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 125ms
After Hooks.deleteTransportAfterTest() 612ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-producer" and set token of apiUsername "super-admin-skz" 12s 611ms
And Prepare user "swisskrono-producer" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 643ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 128ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 880ms
And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 1s 003ms
And Wait till auction end 1m 57s 016ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Dodano nową ofertę" 3m 7s 109ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 447ms
After Hooks.deleteTransportAfterTest() 640ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 728ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 534ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 112ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 056ms
And Wait till auction end 1m 57s 016ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Aukcja zakończona bez ofert" 5s 500ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 415ms
After Hooks.deleteTransportAfterTest() 626ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 032ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 321ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 153ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 983ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 974ms
And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 1s 805ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Oferta przelicytowana" 25s 462ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 090ms
After Hooks.deleteTransportAfterTest() 575ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 479ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 377ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 090ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 004ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 013ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 1m 54s 209ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 250ms
After Hooks.deleteTransportAfterTest() 568ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 631ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 369ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 102ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 048ms
And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 806ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 11s 266ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 079ms
After Hooks.deleteTransportAfterTest() 635ms
View Feature Auctions Mail
Scenario Outline Check mail two hours before auction ends
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 5s 425ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 513ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 150ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" and finish of auction in "121" minutes 637ms
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.cleanUserDetailsAfterTest() 2s 096ms
After Hooks.deleteTransportAfterTest() 626ms
View Feature Discrepancy Report Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 221ms
And Prepare user "hochland-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 4s 342ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 166ms
And Go to "TRANSPORT_TABLE" 399ms
And Go to transport details "DELIVERY" 2s 962ms
And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 020ms
And Fill transport form 43s 140ms
And Open section: "discrepancy-report-panel" 1s 166ms
And Fill discrepancy report section 52s 456ms
And Go to transport details "DELIVERY" 2s 890ms
And Change filled value in details "rodo-acceptance" "checkbox" "true" "0" 1s 575ms
And Generate discrepancy report 6s 648ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Utworzono protokół niezgodności" 5s 499ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 3s 423ms
After Hooks.deleteTransportAfterTest() 955ms
View Feature Mode of transportation mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-bausch" 250ms
And Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file 3s 055ms
When Create default mode of transportation by API with "pba1-carrier" 696ms
Then Update mode of transportation by API with "pba1-carrier": "BBBB0000" "Model2" "Marka2" "CCCC0000" 373ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Środek transportu BBBB0000 został zaktualizowany" 5s 200ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 599ms
After Hooks.deleteModeOfTransportationAfterTest() 322ms
View Feature Mode of transportation mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-bausch" 224ms
And Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 788ms
When Create default mode of transportation by API with "pba1-carrier" 561ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowy środek transportu" 6s 386ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 557ms
After Hooks.deleteModeOfTransportationAfterTest() 315ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 9s 145ms
And Prepare user "pha2-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 992ms
And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 270ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 210ms
And Go to "WAREHOUSE_TAB" 1s 608ms
And Select warehouse "Serownia" 1s 610ms
And Set week view 1s 234ms
And Show yesterday 1s 165ms
And Move window into the past 439ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "spóźnił się na" 15s 598ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 411ms
After Hooks.deleteTransportAfterTest() 804ms
After Hooks.rollbackAddedAuthorities() 180ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 9s 319ms
And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 516ms
And Wait "60" seconds 1m
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 171ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica import" 32s 111ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 184ms
After Hooks.deleteTransportAfterTest() 551ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 676ms
And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 405ms
And Wait "60" seconds 1m
And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 200ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica eksport" 47s 668ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 364ms
After Hooks.deleteTransportAfterTest() 570ms
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" 2s 655ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 524ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 091ms
And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 4s 875ms
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.cleanUserDetailsAfterTest() 2s 050ms
After Hooks.deleteTransportAfterTest() 587ms
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" 2s 449ms
And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 314ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 076ms
And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 4s 894ms
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.cleanUserDetailsAfterTest() 2s 065ms
After Hooks.deleteTransportAfterTest() 744ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 481ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 275ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 180ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 3s 044ms
And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 1s 047ms
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 199ms
Then If user is login then logout 256ms
And Login as "swisskrono-admin" 2s 751ms
And Go to auction details 1s 814ms
And Pass transport to carrier from auction details 1s 549ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 3m 4s 373ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 3s 232ms
After Hooks.deleteTransportAfterTest() 768ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 820ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 3s 149ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 150ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 3s 002ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowe zapytanie ofertowe" 5s 323ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 730ms
After Hooks.deleteTransportAfterTest() 699ms
View Feature Remind password
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-adama" 246ms
And Prepare user "adama-admin" details with all notifications and "automaty10@o2.pl" by JSON file 1s 499ms
Then Send password remind email "automaty10@o2.pl" and check if status is ok 335ms
After Hooks.cleanUserDetailsAfterTest() 1s 248ms
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 532ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 460ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 019ms
And Add transport by SKApi in "MGW" assigned to "" 019ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 016ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 928ms
When Click button advice in transport table "CONTAINER" 210ms
And Set advice window in schedule 3s 365ms
And Fill advice form 20s 406ms
And Click advice save button and wait for advice form to disappear 33s 253ms
And Go to "TRANSPORT_TABLE" 436ms
And Go to transport details "CONTAINER" 2s 982ms
Then Check are advice values equals 4s 967ms
After Hooks.cleanUserDetailsAfterTest() 2s 293ms
After Hooks.deleteTransportAfterTest() 803ms
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) 002ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 827ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 399ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 016ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 4s 212ms
When Click button advice in transport table "OWN_COLLECTION" 225ms
And Set advice window in schedule 3s 414ms
And Fill advice form 20s 425ms
And Click advice save button and wait for advice form to disappear 33s 292ms
And Go to "TRANSPORT_TABLE" 490ms
And Go to transport details "OWN_COLLECTION" 2s 921ms
Then Check are advice values equals 4s 984ms
After Hooks.cleanUserDetailsAfterTest() 2s 109ms
After Hooks.deleteTransportAfterTest() 779ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 507ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 341ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "" 022ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 018ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 374ms
When Click button advice in transport table "TRANSPORT_ORDER" 231ms
And Set advice window in schedule 3s 432ms
And Fill advice form 20s 568ms
And Click advice save button and wait for advice form to disappear 33s 347ms
And Go to "TRANSPORT_TABLE" 490ms
And Go to transport details "TRANSPORT_ORDER" 2s 868ms
Then Check are advice values equals 4s 983ms
After Hooks.cleanUserDetailsAfterTest() 2s 302ms
After Hooks.deleteTransportAfterTest() 778ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 8s 773ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 474ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 023ms
And Add transport by SKApi in "MGW" assigned to "" 021ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 017ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 845ms
When Click button advice in transport table "TRANSPORT_ORDER" 226ms
And Set advice window in schedule 3s 380ms
And Fill advice form 20s 749ms
And Click advice save button and wait for advice form to disappear 33s 841ms
And Go to "TRANSPORT_TABLE" 451ms
And Go to transport details "TRANSPORT_ORDER" 2s 838ms
Then Check are advice values equals 4s 977ms
After Hooks.cleanUserDetailsAfterTest() 2s 712ms
After Hooks.deleteTransportAfterTest() 809ms
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 618ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 733ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 024ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 022ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 017ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 549ms
When Click button advice in transport table "TRANSPORT_ORDER" 205ms
And Set advice window in schedule 30s 085ms
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.LvIige}, 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: 9ebdc2f1001d94b48960ea9db301ccc5
*** Element info: {Using=xpath, value=//button[@data-button-name='SHIFT_RIGHT_DAY']}
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	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.cleanUserDetailsAfterTest() 1s 775ms
After Hooks.deleteTransportAfterTest() 604ms
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 604ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 366ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 024ms
And Add transport by SKApi in "MGW" assigned to "" 019ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 016ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 199ms
When Click button advice in transport table "OWN_COLLECTION" 199ms
And Set advice window in schedule 3s 398ms
And Fill advice form 20s 514ms
And Click advice save button and wait for advice form to disappear 33s 268ms
And Go to "TRANSPORT_TABLE" 438ms
Then Check advice data in SK API database "OWN_COLLECTION" 408ms
After Hooks.cleanUserDetailsAfterTest() 2s 055ms
After Hooks.deleteTransportAfterTest() 826ms
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 524ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 387ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 018ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 899ms
When Click button advice in transport table "CONTAINER" 211ms
And Set advice window in schedule 3s 352ms
And Fill advice form 20s 489ms
And Click advice save button and wait for advice form to disappear 33s 334ms
And Go to "TRANSPORT_TABLE" 398ms
Then Check advice data in SK API database "CONTAINER" 218ms
After Hooks.cleanUserDetailsAfterTest() 2s 290ms
After Hooks.deleteTransportAfterTest() 787ms
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 537ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 399ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 016ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 015ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 277ms
When Click button advice in transport table "TRANSPORT_ORDER" 218ms
And Set advice window in schedule 3s 399ms
And Fill advice form 20s 467ms
And Click advice save button and wait for advice form to disappear 33s 259ms
And Go to "TRANSPORT_TABLE" 490ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 087ms
After Hooks.cleanUserDetailsAfterTest() 2s 225ms
After Hooks.deleteTransportAfterTest() 799ms
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 615ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 356ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 017ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 016ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 018ms
When Click button advice in transport table "TRANSPORT_ORDER" 234ms
And Set advice window in schedule 3s 378ms
And Fill advice form 20s 396ms
And Click advice save button and wait for advice form to disappear 33s 235ms
And Go to "TRANSPORT_TABLE" 504ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 094ms
After Hooks.cleanUserDetailsAfterTest() 2s 974ms
After Hooks.deleteTransportAfterTest() 824ms
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 632ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 839ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 020ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 017ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 017ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 563ms
When Click button advice in transport table "TRANSPORT_ORDER" 220ms
And Set advice window in schedule 3s 427ms
And Fill advice form 20s 318ms
And Click advice save button and wait for advice form to disappear 33s 816ms
And Go to "TRANSPORT_TABLE" 437ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 274ms
After Hooks.cleanUserDetailsAfterTest() 1s 687ms
After Hooks.deleteTransportAfterTest() 829ms
View Feature Status rejection
Scenario Outline Check if it is possible to reject status by guard in transport table
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 4s 449ms
And Prepare user "lantmannen-guard" details with all notifications and "apolloautomattest@gmail.com" by JSON file 951ms
And Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 019ms
And Add access to the warehouse "Magazyn - Nowa Sól" to the user "lantmannen-guard" by JSON file 773ms
And Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 4s 567ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 909ms
And Check if reject date is not visible 15s 046ms
When Reject status: Book of disinfection 232ms
And Check if reject date is visible 1s 036ms
Then If user is login then logout 296ms
And Login as "lantmannen-admin" 2s 591ms
And Check if note was added to transport after status rejection 1s 688ms
And Check if history note was added to transport after status rejection - "LOAD" 18s 929ms
java.lang.AssertionError: Nie znaleziono wpisu w historii zlecenia o odrzuceniu statusu!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at Pages.Transport.TransportFormPage.checkIfHistoryNoteWasAddedToTransport(TransportFormPage.java:238)
	at CucumberTests.StatusTests.RejectStatuses.checkIfHistoryNoteWasAddedToTransportAfterStatusRejection(RejectStatuses.java:67)
	at ✽.Check if history note was added to transport after status rejection - "LOAD"(file:Features/Atom/Statuses/RejectStatuses.feature:17)
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nieaktualna księga mycia i dezynfekcji" 000ms
And Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 134ms
After Hooks.deleteTransportAfterTest() 722ms
After Hooks.rollbackWarehousesAccess() 767ms
Before Hooks.showScenarioName(Scenario) 000ms
Given Set token of apiUsername "super-admin-skd" 229ms
And Prepare login page 463ms
And Click remind password button 267ms
And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 050ms
And Send remind password form with email "apolloautomattest@gmail.com" 547ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Restart hasła! | Password reset!" 32s 784ms
And Extract password from mailgun mail 4s 259ms
And Reset password from link 1s 620ms
Then Check if alert is displayed "Hasło nie może być takie samo jak aktualne hasło użytkownika." in remind password page 239ms
After Hooks.cleanUserDetailsAfterTest() 934ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-adama" 239ms
And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_USERS_MAIN_DATA" to user "oaa1-receiver-2@qa.qa-test" 352ms
When Login as "oaa1-receiver-2@qa.qa-test" 4s 427ms
And Go to user "oaa1-receiver@qa.qa-test" details edition by prepared link 159ms
And Change user details "email" to "newEmailAddress@newEmail.com" 1s 108ms
And Change user details "phone" to "123456789" 471ms
Then Save user details 1s 047ms
And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 168ms
After Hooks.cleanUserDetailsAfterTest() 664ms
After Hooks.rollbackAddedAuthorities() 288ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 243ms
And Set basic authorities "ROLE_USERS_TAB;EDIT_USERS_NOTIFICATION" to user "pskza1-carrier-2@qa.qa-test" 199ms
When Login as "pskza1-carrier-2@qa.qa-test" 7s 358ms
And Go to user "pskza1-carrier@qa.qa-test" details edition by prepared link 097ms
And Expand "other" notification section 2s 612ms
And Select all notifications in "other" section 272ms
Then Save user details 1s 504ms
After Hooks.cleanUserDetailsAfterTest() 905ms
After Hooks.rollbackAddedAuthorities() 153ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-adama" 240ms
And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;ROLE_EDIT_USERS_MAIN_DATA" to user "adama-buyer@qa.qa-test" 453ms
And Set user details json of user "oaa1-receiver@qa.qa-test" 014ms
When Login as "adama-buyer@qa.qa-test" 5s 245ms
And Go to "USERS_TAB" 2s 967ms
And Find user "oaa1-receiver@qa.qa-test" 2s 773ms
And Change user details "email" to "newEmailAddress@newEmail.com" 826ms
And Change user details "phone" to "123456789" 422ms
Then Save user details 1s 010ms
And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 158ms
After Hooks.cleanUserDetailsAfterTest() 670ms
After Hooks.rollbackAddedAuthorities() 251ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 230ms
And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;EDIT_USERS_NOTIFICATION" to user "swisskrono-tradesman@qa.qa-test" 343ms
And Set user details json of user "pskza1-carrier@qa.qa-test" 010ms
When Login as "swisskrono-tradesman@qa.qa-test" 9s 304ms
And Go to "USERS_TAB" 1s 545ms
And Find user "pskza1-carrier@qa.qa-test" 2s 727ms
And Expand "GLUE_FACTORY" notification section 541ms
And Select all notifications in "GLUE_FACTORY" section 1s 469ms
Then Save user details 1s 893ms
After Hooks.cleanUserDetailsAfterTest() 1s 038ms
After Hooks.rollbackAddedAuthorities() 237ms