Project Number Date
ApolloFullRunnerReport apollo-test-2.161 17 wrz 2021, 07:00

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@cleanUserDetailsAfterTest 455 7 10 0 0 472 41 7 48 1h 7m 32s 634ms Failed
View Feature Invitation
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 287ms
And Delete invitations with email "automaty31415@test.pl" 097ms
Then Create invitation by JSON file "super-admin-alrec" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 419ms
And Prepare user "piast-admin" details with all notifications and "automaty31415@test.pl" by JSON file 1s 335ms
When Login as "piast-admin" 5s 079ms
Then Go to "INVITATIONS_TAB" 662ms
And Go to invitation details 155ms
Then Reject invitation by button as user 316ms
When If user is login then logout 686ms
Then Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 4s 719ms
And Go to "INVITATIONS_TAB" 484ms
And Go to "REJECTED_TAB" invitation status tab 246ms
Then Invitation is displayed on list "automaty31415@test.pl" 486ms
After Hooks.deleteInvitationAfterTest() 185ms
After Hooks.cleanUserDetailsAfterTest() 1s 256ms
View Feature Invitation
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-alrec" 275ms
And Prepare user "dha1-supplier-2" details with all notifications and "automatyy3333@test.pl" by JSON file 1s 838ms
When Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 2s 440ms
And Go to "INVITATIONS_TAB" 471ms
And Create invitation for "existing" user "SUPPLIER" "SUPPLIER" "automatyy3333@test.pl" "PL" 2s 969ms
And Wait "3" seconds 3s
Then Create invitation success alert is displayed 111ms
After Hooks.deleteInvitationAfterTest() 184ms
After Hooks.cleanUserDetailsAfterTest() 1s 379ms
View Feature Login feature
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skd" 282ms
And Prepare parameter "NUMBER_OF_FAILED_LOGIN_ATTEMPTS" with value: "1" 102ms
Given Failed login as "swiss-krono-delivery-admin-2" 1s 497ms
Then Verify that login error reason is "auth.invalidLoginOrPassword" 570ms
Given Try login as "swiss-krono-delivery-admin-2" 1s 461ms
Then Verify that login error reason is "auth.accountLocked" 286ms
Given Click remind password button 218ms
And Prepare user "swiss-krono-delivery-admin-2" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 124ms
And Send remind password form with email "apolloautomattest@gmail.com" 539ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Restart hasła! | Password reset!" 36s 930ms
And Extract password reset link from mailgun mail 4s 394ms
And Reset password from link 1s 496ms
Then Login as "swiss-krono-delivery-admin-2" with new password 5s 248ms
And User is successfully logged 082ms
After Hooks.cleanUserDetailsAfterTest() 1s 009ms
After Hooks.clearUserPasswordDataAfterTest() 478ms
After Hooks.rollbackParameters() 097ms
After Hooks.unlockUsers() 101ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 440ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 915ms
And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 2s 251ms
And Set "advice" inputs from JSON file "ADVICE_CONTAINER" "super-admin-adama" 001ms
And Show all transport types 1s 160ms
And Click button advice in transport table "CONTAINER" 244ms
And Set advice window in schedule 3s 296ms
And Fill advice form 17s 273ms
And Click advice save button and wait for advice form to disappear 33s 831ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!" 5s 623ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 346ms
After Hooks.deleteTransportAfterTest() 822ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 666ms
And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 351ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 055ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 000ms
And Show all transport types 1s 146ms
And Click button advice in transport table "DELIVERY" 237ms
And Set advice window in schedule 3s 395ms
And Fill advice form 12s 942ms
And Click advice save button and wait for advice form to disappear 33s 322ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!" 5s 509ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 048ms
After Hooks.deleteTransportAfterTest() 803ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 772ms
And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 860ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 964ms
And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-keeeper" 001ms
And Show all transport types 1s 150ms
And Click button advice in transport table "LOAD" 253ms
And Set advice window in schedule 3s 304ms
And Fill advice form 18s 826ms
And Click advice save button and wait for advice form to disappear 33s 279ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Time window has been saved!" 5s 860ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 489ms
After Hooks.deleteTransportAfterTest() 769ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 018ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 478ms
And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 894ms
And Show all transport types 1s 175ms
And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-adama" 3s 445ms
And Go to "TRANSPORT_TABLE" 409ms
And Go to transport details "CONTAINER" 2s 943ms
And Set "transport" inputs from JSON file "EDIT_CONTAINER" "super-admin-adama" 000ms
When Go to transport details "CONTAINER" 3s 479ms
And Fill transport form 5s 205ms
And Set "advice" inputs from JSON file "EDIT_ADVICE_CONTAINER" "super-admin-adama" 001ms
And Expand advice panel 244ms
And Edit advice in transport details 17s 609ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 187ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 5s 564ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 272ms
After Hooks.deleteTransportAfterTest() 811ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 5s 550ms
And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 169ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 024ms
And Show all transport types 1s 134ms
And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 3s 688ms
And Go to "TRANSPORT_TABLE" 355ms
And Go to transport details "DELIVERY" 3s 015ms
And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-piast" 001ms
When Go to transport details "DELIVERY" 3s 724ms
And Fill transport form 1m 8s 735ms
And Set "advice" inputs from JSON file "EDIT_ADVICE_DELIVERY" "super-admin-piast" 001ms
And Expand advice panel 263ms
And Edit advice in transport details 8s 104ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 235ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 11s 598ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 134ms
After Hooks.deleteTransportAfterTest() 929ms
View Feature Advice Mail
Scenario Outline Check if mail was sent to creator after editing advice
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 5s 889ms
And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 685ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 974ms
And Show all transport types 1s 173ms
And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD" as "super-admin-keeeper" 3s 437ms
And Go to "TRANSPORT_TABLE" 420ms
And Go to transport details "LOAD" 2s 964ms
And Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-keeeper" 001ms
When Go to transport details "LOAD" 3s 493ms
And Fill transport form 28s 624ms
And Set "advice" inputs from JSON file "EDIT_ADVICE_LOAD" "super-admin-keeeper" 001ms
And Expand advice panel 288ms
And Edit advice in transport details 23s 366ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 231ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 2m 57s 248ms
Then Check if user got a mail 000ms
java.lang.AssertionError: Użytkownik nie otrzymał maila. Actual: []
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failEquals(Assert.java:185)
	at org.junit.Assert.assertNotEquals(Assert.java:161)
	at CucumberTests.Mail.MailTest.checkIfUseGotMail(MailTest.java:49)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/AdviceMail.feature:39)
After Hooks.cleanUserDetailsAfterTest() 1s 678ms
After Hooks.deleteTransportAfterTest() 870ms
View Feature Advice Mail
Scenario Outline Check if mail was sent to creator after status confirmation
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Set token of apiUsername "super-admin-skd" 277ms
And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 078ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 2s 924ms
And Confirm status "REPORTING" by Public API "v1" 560ms
And Confirm status "ARRIVAL" by Public API "v1" 883ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wjazd na teren zakładu" 2m 54s 676ms
Then Check if user got a mail 000ms
java.lang.AssertionError: Użytkownik nie otrzymał maila. Actual: []
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failEquals(Assert.java:185)
	at org.junit.Assert.assertNotEquals(Assert.java:161)
	at CucumberTests.Mail.MailTest.checkIfUseGotMail(MailTest.java:49)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/AdviceMail.feature:54)
And Assign Queue to classification resource: "super-admin-skd" "trociny" "CLASSIFICATION" 000ms
And Assign Place to classification resource: "super-admin-skd" "trociny" "Rozładunek" "UNLOAD" 000ms
And Confirm status "DEPARTURE" by Public API "v1" 000ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wyjazd" 000ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 031ms
After Hooks.deleteTransportAfterTest() 872ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-hochland" 289ms
And Prepare company "Dostawca Hochland Automat 1" verification email setting "48h" 196ms
And Prepare user "dha1-supplier-2" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 092ms
And Login as "dha1-supplier-2" and set token of apiUsername "dha1-supplier-2" 8s 867ms
And Create transport "CREATE_DELIVERY" by JSON file as "dha1-supplier-2" 17s 051ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Weryfikacja danych awizacji" 1m 20s 398ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 677ms
After Hooks.deleteTransportAfterTest() 761ms
After Hooks.rollbackVerificationEmailSettingAfterTest() 442ms
View Feature Advice Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skd" 269ms
And Create transport "CREATE_DELIVERY" by JSON file as "swiss-krono-delivery-producer" 16s 633ms
And Prepare user "swiss-krono-delivery-producer" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 551ms
When Login as "swiss-krono-delivery-producer" 4s 911ms
And Go to "TRANSPORT_TABLE" 526ms
And Show all transport types 15s 061ms
And Check if transport is "visible" in table of transports 103ms
And Disable user "swiss-krono-delivery-producer" 886ms
And Confirm status "ARRIVAL" by Public API "v1" 786ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wjazd na teren zakładu" 2m 47s 468ms
Then Check if user did not get an mail 000ms
After Hooks.cleanUserDetailsAfterTest() 889ms
After Hooks.deleteTransportAfterTest() 858ms
After Hooks.enableDisabledUserAfterTest() 785ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 226ms
And Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 245ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 183ms
And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 3s 586ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowa aukcja" 5s 345ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 107ms
After Hooks.deleteTransportAfterTest() 704ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 551ms
And Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 360ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 063ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 035ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier" for "super-admin-adama" 1s 476ms
And Add a bid "500" to an auction by JSON file as "paa2-carrier" for "super-admin-adama" 2s 039ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 10s 740ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 113ms
After Hooks.deleteTransportAfterTest() 678ms
View Feature Auctions Mail
Scenario Outline Check mail after bid has been added to auction
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login as "swisskrono-producer" and set token of apiUsername "super-admin-skz" 10s 893ms
And Prepare user "swisskrono-producer" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 836ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 160ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 883ms
And Add a bid "1500" to an auction by JSON file as "pskza1-carrier" for "pskza1-carrier" 1s 058ms
And Wait till auction end 1m 57s 023ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Dodano nową ofertę" 2m 46s 175ms
Then Check if user got a mail 000ms
java.lang.AssertionError: Użytkownik nie otrzymał maila. Actual: []
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failEquals(Assert.java:185)
	at org.junit.Assert.assertNotEquals(Assert.java:161)
	at CucumberTests.Mail.MailTest.checkIfUseGotMail(MailTest.java:49)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/AuctionMail.feature:39)
After Hooks.cleanUserDetailsAfterTest() 2s 426ms
After Hooks.deleteTransportAfterTest() 673ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 795ms
And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 546ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 113ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 048ms
And Wait till auction end 1m 57s 022ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Aukcja zakończona bez ofert" 5s 850ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 1s 380ms
After Hooks.deleteTransportAfterTest() 627ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 826ms
And Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 331ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 097ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 030ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier" for "super-admin-adama" 1s 036ms
And Add a bid "500" to an auction by JSON file as "paa2-carrier" for "super-admin-adama" 1s 883ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Oferta przelicytowana" 32s 587ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 176ms
After Hooks.deleteTransportAfterTest() 625ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 649ms
And Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 327ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 067ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 008ms
And Add a bid "1500" to an auction by JSON file as "paa1-carrier" for "super-admin-adama" 1s 019ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 1m 47s 082ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 326ms
After Hooks.deleteTransportAfterTest() 594ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 560ms
And Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 340ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 056ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 082ms
And Add a bid "500" to an auction by JSON file as "paa1-carrier" for "super-admin-adama" 1s 787ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 5s 319ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 050ms
After Hooks.deleteTransportAfterTest() 617ms
View Feature Auctions Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "paa1-carrier" and set token of apiUsername "super-admin-adama" 5s 073ms
And Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 697ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 115ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" and finish of auction in "121" minutes 3s 140ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zakończenie aukcji" 1m 25s 672ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 281ms
After Hooks.deleteTransportAfterTest() 631ms
View Feature Discrepancy Report Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 133ms
And Prepare user "hochland-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 3s 242ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 243ms
And Go to "TRANSPORT_TABLE" 366ms
And Go to transport details "DELIVERY" 2s 955ms
And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 001ms
And Fill transport form 43s 122ms
And Open section: "discrepancy-report-panel" 1s 162ms
And Fill discrepancy report section 52s 367ms
And Go to transport details "DELIVERY" 2s 820ms
And Change filled value in details "rodo-acceptance" "checkbox" "true" "0" 1s 528ms
And Generate discrepancy report 22s 210ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Utworzono protokół niezgodności" 5s 943ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 3s 513ms
After Hooks.deleteTransportAfterTest() 948ms
View Feature Mode of transportation mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-bausch" 274ms
And Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file 3s 149ms
When Create default mode of transportation by API with "pba1-carrier" 712ms
Then Update mode of transportation by API with "pba1-carrier": "BBBB0000" "Model2" "Marka2" "CCCC0000" 372ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Środek transportu BBBB0000 został zaktualizowany" 5s 864ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 512ms
After Hooks.deleteModeOfTransportationAfterTest() 376ms
View Feature Mode of transportation mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-bausch" 302ms
And Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 909ms
When Create default mode of transportation by API with "pba1-carrier" 590ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowy środek transportu" 5s 439ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 505ms
After Hooks.deleteModeOfTransportationAfterTest() 311ms
View Feature Transport Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 9s 609ms
And Prepare user "pha2-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 102ms
And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 274ms
And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 225ms
And Go to "WAREHOUSE_TAB" 1s 317ms
And Select warehouse "Serownia" 1s 649ms
And Set week view 1s 246ms
And Show yesterday 1s 152ms
And Move window into the past 407ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "spóźnił się na" 1m 4s 609ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 357ms
After Hooks.deleteTransportAfterTest() 833ms
After Hooks.rollbackAddedAuthorities() 158ms
View Feature Transport Mail
Scenario Outline Check if mail was sent to after transport creation
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 9s 688ms
And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 551ms
And Wait "60" seconds 1m
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 175ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica import" 2m 53s 391ms
Then Check if user got a mail 000ms
java.lang.AssertionError: Użytkownik nie otrzymał maila. Actual: []
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failEquals(Assert.java:185)
	at org.junit.Assert.assertNotEquals(Assert.java:161)
	at CucumberTests.Mail.MailTest.checkIfUseGotMail(MailTest.java:49)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/TransportMail.feature:27)
After Hooks.cleanUserDetailsAfterTest() 2s 472ms
After Hooks.deleteTransportAfterTest() 599ms
View Feature Transport Mail
Scenario Outline Check if mail was sent to after transport creation
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 795ms
And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 407ms
And Wait "60" seconds 1m
And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 202ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica eksport" 2m 45s 853ms
Then Check if user got a mail 000ms
java.lang.AssertionError: Użytkownik nie otrzymał maila. Actual: []
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failEquals(Assert.java:185)
	at org.junit.Assert.assertNotEquals(Assert.java:161)
	at CucumberTests.Mail.MailTest.checkIfUseGotMail(MailTest.java:49)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/TransportMail.feature:27)
After Hooks.cleanUserDetailsAfterTest() 2s 511ms
After Hooks.deleteTransportAfterTest() 577ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 884ms
And Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 631ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 118ms
And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 34s 830ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zlecenie czeka na akceptację" 5s 842ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 079ms
After Hooks.deleteTransportAfterTest() 775ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 547ms
And Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 363ms
And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 081ms
And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 34s 826ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zostało przekazane nowe zlecenie" 5s 492ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 288ms
After Hooks.deleteTransportAfterTest() 582ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 716ms
And Prepare user "pskza1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 305ms
And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 144ms
And Transfer transport to carrier "Przewoźnik SKZ Automat 1" 34s 710ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zlecenie czeka na akceptację" 5s 883ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 934ms
After Hooks.deleteTransportAfterTest() 786ms
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" details with all notifications and "apolloautomattest@gmail.com" by JSON file 3s 216ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 148ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 3s 039ms
And Add a bid "1500" to an auction by JSON file as "pskza1-carrier" for "pskza1-carrier" 1s 129ms
And Add a bid "500" to an auction by JSON file as "pskza2-carrier-2" for "pskza2-carrier-2" 1s 197ms
Then If user is login then logout 267ms
And Login as "swisskrono-admin" 2s 610ms
And Go to auction details 1s 820ms
And Pass transport to carrier from auction details 1s 578ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 32s 108ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 763ms
After Hooks.deleteTransportAfterTest() 851ms
View Feature Transport Transfer Mail
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 887ms
And Prepare user "pskza1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 3s 107ms
And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 284ms
And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 951ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowe zapytanie ofertowe" 5s 336ms
Then Check if user got a mail 000ms
After Hooks.cleanUserDetailsAfterTest() 2s 891ms
After Hooks.deleteTransportAfterTest() 672ms
View Feature Remind password
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-adama" 298ms
And Prepare user "adama-admin" details with all notifications and "automaty10@o2.pl" by JSON file 1s 792ms
Then Send password remind email "automaty10@o2.pl" and check if status is ok 276ms
After Hooks.cleanUserDetailsAfterTest() 1s 309ms
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 655ms
And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 001ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 432ms
And Add transport by SKApi in "MGW" assigned to "" 029ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms
And Check is transport "CONTAINER" created in transport table and set transport id 13s 109ms
When Click button advice in transport table "CONTAINER" 267ms
And Set advice window in schedule 3s 418ms
And Fill advice form 20s 392ms
And Click advice save button and wait for advice form to disappear 33s 213ms
And Go to "TRANSPORT_TABLE" 426ms
And Go to transport details "CONTAINER" 2s 841ms
Then Check are advice values equals 4s 919ms
After Hooks.cleanUserDetailsAfterTest() 2s 425ms
After Hooks.deleteTransportAfterTest() 863ms
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 634ms
And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 001ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 479ms
And Add transport by SKApi in "MGW" assigned to "" 019ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 4s 098ms
When Click button advice in transport table "OWN_COLLECTION" 220ms
And Set advice window in schedule 3s 277ms
And Fill advice form 20s 590ms
And Click advice save button and wait for advice form to disappear 33s 363ms
And Go to "TRANSPORT_TABLE" 467ms
And Go to transport details "OWN_COLLECTION" 2s 846ms
Then Check are advice values equals 5s
After Hooks.cleanUserDetailsAfterTest() 2s 104ms
After Hooks.deleteTransportAfterTest() 837ms
View Feature SK Api - Advice transport
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 305ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 379ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 410ms
When Click button advice in transport table "TRANSPORT_ORDER" 212ms
And Set advice window in schedule 3s 360ms
And Fill advice form 20s 408ms
And Click advice save button and wait for advice form to disappear 33s 758ms
And Go to "TRANSPORT_TABLE" 468ms
And Go to transport details "TRANSPORT_ORDER" 2s 937ms
Then Check are advice values equals 4s 924ms
After Hooks.cleanUserDetailsAfterTest() 2s 314ms
After Hooks.deleteTransportAfterTest() 859ms
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" and set token of apiUsername "super-admin-skz" 8s 451ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms
And Prepare user "pskza1-carrier" details with all notifications and "" by JSON file 3s 803ms
And Add transport by SKApi in "MGW" assigned to "" 021ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 748ms
When Click button advice in transport table "TRANSPORT_ORDER" 212ms
And Set advice window in schedule 3s 296ms
And Fill advice form 20s 517ms
And Click advice save button and wait for advice form to disappear 33s 948ms
And Go to "TRANSPORT_TABLE" 463ms
And Go to transport details "TRANSPORT_ORDER" 2s 861ms
Then Check are advice values equals 4s 972ms
After Hooks.cleanUserDetailsAfterTest() 2s 761ms
After Hooks.deleteTransportAfterTest() 848ms
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" and set token of apiUsername "super-admin-skz" 7s 402ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms
And Prepare user "swisskrono-tradesman" details with all notifications and "automaty@test.pl" by JSON file 1s 726ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 021ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 563ms
When Click button advice in transport table "TRANSPORT_ORDER" 222ms
And Set advice window in schedule 30s 135ms
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=93.0.4577.63)
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=93.0.4577.63 (ff5c0da2ec0adeaed5550e6c7e98417dac77d98a-refs/branch-heads/4577@{#1135}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.y4uQ3Z}, 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=93.0.4577.63, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: fff6f85508e056c6680aae6c5effae26
*** 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:325)
	at CucumberTests.Transport.AdviceTransport.setAdviceWindowInSchedule(AdviceTransport.java:83)
	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 833ms
After Hooks.deleteTransportAfterTest() 567ms
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 479ms
And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 001ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 387ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 162ms
When Click button advice in transport table "OWN_COLLECTION" 218ms
And Set advice window in schedule 3s 334ms
And Fill advice form 20s 371ms
And Click advice save button and wait for advice form to disappear 33s 297ms
And Go to "TRANSPORT_TABLE" 449ms
Then Check advice data in SK API database "OWN_COLLECTION" 419ms
After Hooks.cleanUserDetailsAfterTest() 2s 109ms
After Hooks.deleteTransportAfterTest() 822ms
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 327ms
And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 001ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 387ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 923ms
When Click button advice in transport table "CONTAINER" 235ms
And Set advice window in schedule 3s 302ms
And Fill advice form 20s 554ms
And Click advice save button and wait for advice form to disappear 33s 344ms
And Go to "TRANSPORT_TABLE" 454ms
Then Check advice data in SK API database "CONTAINER" 181ms
After Hooks.cleanUserDetailsAfterTest() 2s 365ms
After Hooks.deleteTransportAfterTest() 848ms
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 610ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 000ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 395ms
And Add transport by SKApi in "MGW" assigned to "" 019ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 330ms
When Click button advice in transport table "TRANSPORT_ORDER" 225ms
And Set advice window in schedule 3s 370ms
And Fill advice form 20s 433ms
And Click advice save button and wait for advice form to disappear 33s 293ms
And Go to "TRANSPORT_TABLE" 492ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 095ms
After Hooks.cleanUserDetailsAfterTest() 2s 231ms
After Hooks.deleteTransportAfterTest() 879ms
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" and set token of apiUsername "super-admin-skz" 6s 490ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms
And Prepare user "pskza1-carrier" details with all notifications and "" by JSON file 3s 831ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 6s 741ms
When Click button advice in transport table "TRANSPORT_ORDER" 244ms
And Set advice window in schedule 3s 390ms
And Fill advice form 20s 299ms
And Click advice save button and wait for advice form to disappear 33s 327ms
And Go to "TRANSPORT_TABLE" 510ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 087ms
After Hooks.cleanUserDetailsAfterTest() 2s 953ms
After Hooks.deleteTransportAfterTest() 866ms
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" and set token of apiUsername "super-admin-skz" 8s 577ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms
And Prepare user "swisskrono-tradesman" details with all notifications and "automaty@test.pl" by JSON file 1s 975ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 021ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 572ms
When Click button advice in transport table "TRANSPORT_ORDER" 209ms
And Set advice window in schedule 3s 356ms
And Fill advice form 20s 464ms
And Click advice save button and wait for advice form to disappear 33s 867ms
And Go to "TRANSPORT_TABLE" 464ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 268ms
After Hooks.cleanUserDetailsAfterTest() 1s 678ms
After Hooks.deleteTransportAfterTest() 808ms
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 567ms
And Prepare user "lantmannen-guard" details with all notifications and "apolloautomattest@gmail.com" by JSON file 926ms
And Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 088ms
And Add access to the warehouse "Magazyn - Nowa Sól" to the user "lantmannen-guard" by JSON file 705ms
And Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 4s 412ms
And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 818ms
And Check if reject date is not visible 15s 052ms
When Reject status: Book of disinfection 228ms
And Check if reject date is visible 882ms
Then If user is login then logout 522ms
And Login as "lantmannen-admin" 2s 207ms
And Check if note was added to transport after status rejection 1s 707ms
And Check if history note was added to transport after status rejection - "LOAD" 7s 253ms
And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nieaktualna księga mycia i dezynfekcji" 2m 59s 787ms
And Check if user got a mail 000ms
java.lang.AssertionError: Użytkownik nie otrzymał maila. Actual: []
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failEquals(Assert.java:185)
	at org.junit.Assert.assertNotEquals(Assert.java:161)
	at CucumberTests.Mail.MailTest.checkIfUseGotMail(MailTest.java:49)
	at ✽.Check if user got a mail(file:Features/Atom/Statuses/RejectStatuses.feature:19)
After Hooks.cleanUserDetailsAfterTest() 1s 249ms
After Hooks.deleteTransportAfterTest() 778ms
After Hooks.rollbackWarehousesAccess() 760ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skd" 270ms
And Prepare login page 449ms
And Click remind password button 254ms
And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 017ms
And Send remind password form with email "apolloautomattest@gmail.com" 502ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Restart hasła! | Password reset!" 27s 938ms
And Extract password reset link from mailgun mail 4s 310ms
And Reset password from link with the same password 1s 559ms
Then Check if alert is displayed "Hasło nie może być takie samo jak aktualne hasło użytkownika." in remind password page 226ms
After Hooks.cleanUserDetailsAfterTest() 1s 066ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-adama" 281ms
And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_USERS_MAIN_DATA" to user "oaa1-receiver-2" 415ms
When Login as "oaa1-receiver-2" 4s 157ms
And Go to user "oaa1-receiver" details edition by prepared link 122ms
And Change user details "email" to "newEmailAddress@newEmail.com" 1s
And Change user details "phone" to "123456789" 581ms
Then Save user details 1s 029ms
And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 167ms
After Hooks.cleanUserDetailsAfterTest() 664ms
After Hooks.rollbackAddedAuthorities() 286ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 282ms
And Set basic authorities "ROLE_USERS_TAB;EDIT_USERS_NOTIFICATION" to user "pskza1-carrier-2" 210ms
When Login as "pskza1-carrier-2" 7s 125ms
And Go to user "pskza1-carrier" details edition by prepared link 094ms
And Expand "other" notification section 2s 398ms
And Select all notifications in "other" section 293ms
Then Save user details 1s 419ms
After Hooks.cleanUserDetailsAfterTest() 889ms
After Hooks.rollbackAddedAuthorities() 168ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-adama" 266ms
And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;ROLE_EDIT_USERS_MAIN_DATA" to user "adama-buyer" 513ms
And Set user details json of user "oaa1-receiver" 016ms
When Login as "adama-buyer" 4s 891ms
And Go to "USERS_TAB" 1s 449ms
And Find user "oaa1-receiver" 3s 598ms
And Change user details "email" to "newEmailAddress@newEmail.com" 812ms
And Change user details "phone" to "123456789" 419ms
Then Save user details 967ms
And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 156ms
After Hooks.cleanUserDetailsAfterTest() 637ms
After Hooks.rollbackAddedAuthorities() 247ms
View Feature UserAuthority
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 264ms
And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;EDIT_USERS_NOTIFICATION" to user "swisskrono-tradesman" 396ms
And Set user details json of user "pskza1-carrier" 010ms
When Login as "swisskrono-tradesman" 9s 041ms
And Go to "USERS_TAB" 1s 586ms
And Find user "pskza1-carrier" 3s 547ms
And Expand "GLUE_FACTORY" notification section 555ms
And Select all notifications in "GLUE_FACTORY" section 1s 423ms
Then Save user details 1s 780ms
After Hooks.cleanUserDetailsAfterTest() 1s 064ms
After Hooks.rollbackAddedAuthorities() 246ms