Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.60	15 sie 2021, 05:37

	Steps	Scenarios	Features
@cleanUserDetailsAfterTest	426	3	9	0	0	438	42	3	45	47m 26s 820ms	Failed

View Feature Invitation

@deleteInvitationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if rejected invitation is visible in rejected tab

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 095ms

And Delete invitations with email "automaty31415@test.pl" 015ms

Then Create invitation by JSON file "super-admin-alrec" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 758ms

And Prepare user "piast-admin" details with all notifications and "automaty31415@test.pl" by JSON file 198ms

When Login as "piast-admin" 1s 398ms

Then Go to "INVITATIONS_TAB" 193ms

And Go to invitation details 069ms

Then Reject invitation by button as user 109ms

When If user is login then logout 258ms

Then Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 1s 380ms

And Go to "INVITATIONS_TAB" 193ms

And Go to "REJECTED_TAB" invitation status tab 073ms

Then Invitation is displayed on list "automaty31415@test.pl" 147ms

Hooks

After Hooks.deleteInvitationAfterTest() 019ms

After Hooks.cleanUserDetailsAfterTest() 180ms

View Feature Invitation

@deleteInvitationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it is possible to invite existing user in order to associate him with principal company [A-7315]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-alrec" 094ms

And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "automatyy3333@test.pl" by JSON file 244ms

When Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 944ms

And Go to "INVITATIONS_TAB" 176ms

And Create invitation for "existing" user "SUPPLIER" "SUPPLIER" "automatyy3333@test.pl" "PL" 1s 142ms

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 035ms

Hooks

After Hooks.deleteInvitationAfterTest() 038ms

After Hooks.cleanUserDetailsAfterTest() 226ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after creating advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 061ms

And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 180ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 213ms

And Get inputs from database "ADVICE_CONTAINER" "super-admin-adama" 037ms

And Show all transport types 1s 036ms

And Click button advice in transport table "CONTAINER" 104ms

And Set advice window in schedule 2s 467ms

And Fill advice form 13s 927ms

And Click advice save button and wait for advice form to disappear 30s 699ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!" 5s 868ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

After Hooks.cleanUserDetailsAfterTest() 188ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after creating advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 247ms

And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 149ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 219ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 037ms

And Show all transport types 1s 043ms

And Click button advice in transport table "DELIVERY" 089ms

And Set advice window in schedule 2s 642ms

And Fill advice form 10s 547ms

And Click advice save button and wait for advice form to disappear 30s 709ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!" 5s 824ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

After Hooks.cleanUserDetailsAfterTest() 163ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after creating advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 177ms

And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 247ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 227ms

And Get inputs from database "ADVICE_LOAD" "super-admin-keeeper" 036ms

And Show all transport types 1s 044ms

And Click button advice in transport table "LOAD" 095ms

And Set advice window in schedule 2s 472ms

And Fill advice form 15s 290ms

And Click advice save button and wait for advice form to disappear 30s 740ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Time window has been saved!" 5s 840ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

After Hooks.cleanUserDetailsAfterTest() 226ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after editing advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 492ms

And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 203ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 196ms

And Show all transport types 1s 045ms

And Create advice "ADVICE_CONTAINER" "CONTAINER" "super-admin-adama" 47s 216ms

And Go to "TRANSPORT_TABLE" 203ms

And Go to transport details "CONTAINER" 2s 428ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 036ms

When Go to transport details "CONTAINER" 3s 190ms

And Fill transport form 4s 718ms

And Get inputs from database "EDIT_ADVICE_CONTAINER" "super-admin-adama" 036ms

And Expand advice panel 101ms

And Edit advice in transport details 14s 543ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 128ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 5s 452ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

After Hooks.cleanUserDetailsAfterTest() 165ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after editing advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 622ms

And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 136ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 200ms

And Show all transport types 1s 037ms

And Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast" 43s 958ms

And Go to "TRANSPORT_TABLE" 245ms

And Go to transport details "DELIVERY" 2s 579ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-piast" 039ms

When Go to transport details "DELIVERY" 3s 175ms

And Fill transport form 1m 2s 320ms

And Get inputs from database "EDIT_ADVICE_DELIVERY" "super-admin-piast" 038ms

And Expand advice panel 104ms

And Edit advice in transport details 6s 593ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 112ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 11s 193ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

After Hooks.cleanUserDetailsAfterTest() 145ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after editing advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 664ms

And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 246ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 224ms

And Show all transport types 1s 045ms

And Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 48s 543ms

And Go to "TRANSPORT_TABLE" 196ms

And Go to transport details "LOAD" 2s 387ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 038ms

When Go to transport details "LOAD" 3s 180ms

And Fill transport form 26s 008ms

And Get inputs from database "EDIT_ADVICE_LOAD" "super-admin-keeeper" 037ms

And Expand advice panel 130ms

And Edit advice in transport details 20s 667ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 054ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 5s 937ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

After Hooks.cleanUserDetailsAfterTest() 217ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after status confirmation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-skd" 096ms

And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 188ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 1s 328ms

And Confirm status "ARRIVAL" by Public API "v1" 294ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wjazd na teren zakładu" 5s 553ms

Then Check if user got a mail 000ms

And Confirm status "DEPARTURE" by Public API "v1" 187ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wyjazd" 32s 169ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

After Hooks.cleanUserDetailsAfterTest() 136ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackVerificationEmailSettingAfterTest

Scenario Outline Check if verification mail was sent to transport creator

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-hochland" 093ms

And Prepare company "Dostawca Hochland Automat 1" verification email setting "48h" 031ms

And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 179ms

And Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "dha1-supplier-2@qa.qa-test" 2s 352ms

And Create transport "CREATE_DELIVERY" by JSON file as "dha1-supplier-2@qa.qa-test" 15s 316ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Weryfikacja danych awizacji" 1m 46s 702ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

After Hooks.cleanUserDetailsAfterTest() 213ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 132ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating a new auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 525ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 188ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 217ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 509ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowa aukcja" 10s 625ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

After Hooks.cleanUserDetailsAfterTest() 248ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 083ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 356ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 219ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 148ms

And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 428ms

And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 359ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 10s 675ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

After Hooks.cleanUserDetailsAfterTest() 301ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after bid has been added to auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-producer" and set token of apiUsername "super-admin-skz" 2s 516ms

And Prepare user "swisskrono-producer" details with all notifications and "apolloautomattest@gmail.com" by JSON file 370ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 235ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 108ms

And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 185ms

And Wait till auction end 1m 58s 017ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Dodano nową ofertę" 2m 41s 859ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

After Hooks.cleanUserDetailsAfterTest() 297ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after auction without bids

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 154ms

And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 198ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 215ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 149ms

And Wait till auction end 1m 58s 018ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Aukcja zakończona bez ofert" 5s 457ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

After Hooks.cleanUserDetailsAfterTest() 164ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing first place in auction

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 581ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 319ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 228ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 108ms

And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 189ms

And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 295ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Oferta przelicytowana" 10s 350ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

After Hooks.cleanUserDetailsAfterTest() 270ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after winning an auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 054ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 313ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 216ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 134ms

And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 170ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 2m 4s 623ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

After Hooks.cleanUserDetailsAfterTest() 296ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after accepting minimal price

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 177ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 331ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 244ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 144ms

And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 285ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 5s 179ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

After Hooks.cleanUserDetailsAfterTest() 280ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail two hours before auction ends

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 683ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 354ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 252ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" and finish of auction in "121" minutes 2s 177ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zakończenie aukcji" 36s 285ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

After Hooks.cleanUserDetailsAfterTest() 268ms

View Feature Discrepancy Report Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after discrepancy report generation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 416ms

And Prepare user "hochland-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 626ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 383ms

And Go to "TRANSPORT_TABLE" 136ms

And Go to transport details "DELIVERY" 2s 738ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 038ms

And Fill transport form 37s 910ms

And Open section: "discrepancy-report-panel" 1s 069ms

And Fill discrepancy report section 49s 599ms

And Go to transport details "DELIVERY" 2s 551ms

And Change filled value in details "rodo-acceptance" "checkbox" "true" "0" 1s 290ms

And Generate discrepancy report 18s 300ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Utworzono protokół niezgodności" 5s 866ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

After Hooks.cleanUserDetailsAfterTest() 459ms

View Feature Mode of transportation mail

@deleteModeOfTransportationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent after updating mode of transportation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-bausch" 092ms

And Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file 383ms

When Create default mode of transportation by API with "pba1-carrier" 180ms

Then Update mode of transportation by API with "pba1-carrier": "BBBB0000" "Model2" "Marka2" "CCCC0000" 076ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Środek transportu BBBB0000 został zaktualizowany" 10s 884ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 313ms

After Hooks.deleteModeOfTransportationAfterTest() 090ms

View Feature Mode of transportation mail

@deleteModeOfTransportationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent after creating mode of transportation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-bausch" 093ms

And Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file 363ms

When Create default mode of transportation by API with "pba1-carrier" 087ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowy środek transportu" 5s 342ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 300ms

After Hooks.deleteModeOfTransportationAfterTest() 061ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackAddedAuthorities

Scenario Outline Check if mail was sent to after transport delay

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 429ms

And Prepare user "pha2-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 348ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 028ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 419ms

And Go to "WAREHOUSE_TAB" 853ms

And Select warehouse "Serownia" 1s 397ms

And Set week view 1s 094ms

And Show yesterday 1s 067ms

And Move window into the past 292ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "spóźnił się na" 48s 067ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

After Hooks.cleanUserDetailsAfterTest() 307ms

After Hooks.rollbackAddedAuthorities() 025ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after transport creation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 191ms

And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 367ms

And Wait "60" seconds 1m

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 314ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica import" 37s 760ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

After Hooks.cleanUserDetailsAfterTest() 305ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after transport creation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 888ms

And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 342ms

And Wait "60" seconds 1m

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 284ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica eksport" 52s 281ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

After Hooks.cleanUserDetailsAfterTest() 285ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @FLAKY-A-7913

Scenario Outline Check if mail was sent to carrier after transport transfer

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 172ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 333ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 206ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 3s 701ms

Error message

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

Hooks

After Hooks.deleteTransportAfterTest() 073ms

After Hooks.cleanUserDetailsAfterTest() 256ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @FLAKY-A-7913

Scenario Outline Check if mail was sent to carrier after transport transfer with no confirmation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 021ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 320ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 201ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 3s 676ms

Error message

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

Hooks

After Hooks.deleteTransportAfterTest() 071ms

After Hooks.cleanUserDetailsAfterTest() 236ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing inquiry

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 793ms

And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 430ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 242ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 189ms

And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 205ms

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" 202ms

Then If user is login then logout 318ms

And Login as "swisskrono-admin" 1s 015ms

And Go to auction details 1s 224ms

And Pass transport to carrier from auction details 1s 257ms

And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 2m 41s 141ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 209ms

After Hooks.cleanUserDetailsAfterTest() 357ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating new inquiry

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 306ms

And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 438ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 250ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 137ms

And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowe zapytanie ofertowe" 10s 352ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

After Hooks.cleanUserDetailsAfterTest() 359ms

View Feature Remind password

@cleanUserDetailsAfterTest

Scenario Outline Check if remind password http status is ok

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 098ms

And Prepare user "adama-admin" details with all notifications and "automaty10@o2.pl" by JSON file 226ms

Then Send password remind email "automaty10@o2.pl" and check if status is ok 181ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 170ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 149ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 379ms

And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 037ms

And Add transport by SKApi in "MGW" assigned to "" 003ms

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 037ms

And Check is transport "CONTAINER" created in transport table and set transport id 3s 283ms

When Click button advice in transport table "CONTAINER" 069ms

And Set advice window in schedule 2s 555ms

And Fill advice form 16s 680ms

And Click advice save button and wait for advice form to disappear 30s 725ms

And Go to "TRANSPORT_TABLE" 253ms

And Go to transport details "CONTAINER" 2s 509ms

Then Check are advice values equals 4s 347ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

After Hooks.cleanUserDetailsAfterTest() 269ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 998ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 344ms

And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 037ms

And Add transport by SKApi in "MGW" assigned to "" 003ms

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 038ms

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 399ms

When Click button advice in transport table "OWN_COLLECTION" 089ms

And Set advice window in schedule 2s 568ms

And Fill advice form 16s 725ms

And Click advice save button and wait for advice form to disappear 30s 715ms

And Go to "TRANSPORT_TABLE" 173ms

And Go to transport details "OWN_COLLECTION" 2s 457ms

Then Check are advice values equals 4s 331ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

After Hooks.cleanUserDetailsAfterTest() 262ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 952ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 343ms

And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 040ms

And Add transport by SKApi in "MGW" assigned to "" 003ms

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 040ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 805ms

When Click button advice in transport table "TRANSPORT_ORDER" 087ms

And Set advice window in schedule 2s 560ms

And Fill advice form 16s 809ms

And Click advice save button and wait for advice form to disappear 30s 687ms

And Go to "TRANSPORT_TABLE" 207ms

And Go to transport details "TRANSPORT_ORDER" 2s 453ms

Then Check are advice values equals 4s 326ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.cleanUserDetailsAfterTest() 287ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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.

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 034ms

And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 500ms

And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 036ms

And Add transport by SKApi in "MGW" assigned to "" 002ms

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 036ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 818ms

When Click button advice in transport table "TRANSPORT_ORDER" 093ms

And Set advice window in schedule 2s 604ms

And Fill advice form 16s 848ms

And Click advice save button and wait for advice form to disappear 30s 750ms

And Go to "TRANSPORT_TABLE" 246ms

And Go to transport details "TRANSPORT_ORDER" 2s 443ms

Then Check are advice values equals 4s 353ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

After Hooks.cleanUserDetailsAfterTest() 366ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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.

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 876ms

And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 248ms

And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 037ms

And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 003ms

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 039ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 910ms

When Click button advice in transport table "TRANSPORT_ORDER" 094ms

And Set advice window in schedule 30s 082ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//button[@data-button-name='SHIFT_RIGHT_DAY']"}
  (Session info: headless chrome=92.0.4515.131)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.DpvncD}, 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: 420359e06159e0ffbead8f6c62b35687
*** 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

Hooks

After Hooks.deleteTransportAfterTest() 079ms

After Hooks.cleanUserDetailsAfterTest() 218ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 888ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 330ms

And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 037ms

And Add transport by SKApi in "MGW" assigned to "" 003ms

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 037ms

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 393ms

When Click button advice in transport table "OWN_COLLECTION" 097ms

And Set advice window in schedule 2s 564ms

And Fill advice form 16s 716ms

And Click advice save button and wait for advice form to disappear 30s 672ms

And Go to "TRANSPORT_TABLE" 206ms

Then Check advice data in SK API database "OWN_COLLECTION" 162ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

After Hooks.cleanUserDetailsAfterTest() 279ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

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.

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 918ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 357ms

And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 037ms

And Add transport by SKApi in "MGW" assigned to "" 003ms

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 036ms

And Check is transport "CONTAINER" created in transport table and set transport id 6s 314ms

When Click button advice in transport table "CONTAINER" 075ms

And Set advice window in schedule 2s 545ms

And Fill advice form 16s 764ms

And Click advice save button and wait for advice form to disappear 30s 699ms

And Go to "TRANSPORT_TABLE" 194ms

Then Check advice data in SK API database "CONTAINER" 086ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

After Hooks.cleanUserDetailsAfterTest() 291ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 908ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 349ms

And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 037ms

And Add transport by SKApi in "MGW" assigned to "" 004ms

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 036ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 797ms

When Click button advice in transport table "TRANSPORT_ORDER" 104ms

And Set advice window in schedule 2s 562ms

And Fill advice form 16s 881ms

And Click advice save button and wait for advice form to disappear 30s 770ms

And Go to "TRANSPORT_TABLE" 220ms

Then Check advice data in SK API database "TRANSPORT_ORDER" 037ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

After Hooks.cleanUserDetailsAfterTest() 266ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 827ms

And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 407ms

And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 038ms

And Add transport by SKApi in "MGW" assigned to "" 003ms

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 037ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 1s 142ms

When Click button advice in transport table "TRANSPORT_ORDER" 101ms

And Set advice window in schedule 2s 584ms

And Fill advice form 16s 815ms

And Click advice save button and wait for advice form to disappear 30s 753ms

And Go to "TRANSPORT_TABLE" 230ms

Then Check advice data in SK API database "TRANSPORT_ORDER" 034ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

After Hooks.cleanUserDetailsAfterTest() 360ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 066ms

And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 250ms

And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 038ms

And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 003ms

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 037ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 2s 952ms

When Click button advice in transport table "TRANSPORT_ORDER" 080ms

And Set advice window in schedule 2s 548ms

And Fill advice form 16s 760ms

And Click advice save button and wait for advice form to disappear 30s 713ms

And Go to "TRANSPORT_TABLE" 194ms

Then Check advice data in SK API database "TRANSPORT_ORDER" 097ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

After Hooks.cleanUserDetailsAfterTest() 245ms

View Feature Status rejection

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackWarehousesAccess

Scenario Outline Check if it is possible to reject status by guard in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 371ms

And Prepare user "lantmannen-guard" details with all notifications and "apolloautomattest@gmail.com" by JSON file 202ms

And Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 177ms

And Add access to the warehouse "Magazyn - Nowa Sól" to the user "lantmannen-guard" by JSON file 148ms

And Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 1s 239ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 298ms

And Check if reject date is not visible 15s 056ms

When Reject status: Book of disinfection 094ms

And Check if reject date is visible 316ms

Then If user is login then logout 329ms

And Login as "lantmannen-admin" 854ms

And Check if note was added to transport after status rejection 1s 235ms

And Check if history note was added to transport after status rejection - "LOAD" 6s 611ms

And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nieaktualna księga mycia i dezynfekcji" 2m 46s 406ms

And Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

After Hooks.cleanUserDetailsAfterTest() 181ms

After Hooks.rollbackWarehousesAccess() 118ms

View Feature User

@cleanUserDetailsAfterTest @TmsLink=A-8005.1

Scenario Outline Check if it is not possible to use the previous password when editing it - remind password [A-8005]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-skd" 091ms

And Prepare login page 204ms

And Click remind password button 093ms

And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 161ms

And Send remind password form with email "apolloautomattest@gmail.com" 191ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Restart hasła! | Password reset!" 32s 720ms

And Extract password from mailgun mail 4s 174ms

And Reset password from link 722ms

Then Check if alert is displayed "Hasło nie może być takie samo jak aktualne hasło użytkownika." in remind password page 141ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 170ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7965

Scenario Outline Permission - Edit user main data [A-7965]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 098ms

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_USERS_MAIN_DATA" to user "oaa1-receiver-2@qa.qa-test" 069ms

When Login as "oaa1-receiver-2@qa.qa-test" 1s 320ms

And Go to user "oaa1-receiver@qa.qa-test" details edition by prepared link 018ms

And Change user details "email" to "newEmailAddress@newEmail.com" 265ms

And Change user details "phone" to "123456789" 145ms

Then Save user details 266ms

And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 068ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 106ms

After Hooks.rollbackAddedAuthorities() 038ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

Scenario Outline Permission - Edit user notifications [A-7887]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-skz" 092ms

And Set basic authorities "ROLE_USERS_TAB;EDIT_USERS_NOTIFICATION" to user "pskza1-carrier-2@qa.qa-test" 027ms

When Login as "pskza1-carrier-2@qa.qa-test" 1s 810ms

And Go to user "pskza1-carrier@qa.qa-test" details edition by prepared link 026ms

And Expand "other" notification section 470ms

And Select all notifications in "other" section 109ms

Then Save user details 408ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 132ms

After Hooks.rollbackAddedAuthorities() 022ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

Scenario Outline Permission - Edit user main data from other company [A-7887]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 092ms

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;ROLE_EDIT_USERS_MAIN_DATA" to user "adama-buyer@qa.qa-test" 068ms

And Set user details json of user "oaa1-receiver@qa.qa-test" 001ms

When Login as "adama-buyer@qa.qa-test" 1s 372ms

And Go to "USERS_TAB" 898ms

And Find user "oaa1-receiver@qa.qa-test" 2s 279ms

And Change user details "email" to "newEmailAddress@newEmail.com" 238ms

And Change user details "phone" to "123456789" 146ms

Then Save user details 257ms

And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 050ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 102ms

After Hooks.rollbackAddedAuthorities() 040ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

Scenario Outline Permission - Edit user notifications from other company [A-7887]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-skz" 101ms

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;EDIT_USERS_NOTIFICATION" to user "swisskrono-tradesman@qa.qa-test" 050ms

And Set user details json of user "pskza1-carrier@qa.qa-test" 001ms

When Login as "swisskrono-tradesman@qa.qa-test" 2s 017ms

And Go to "USERS_TAB" 783ms

And Find user "pskza1-carrier@qa.qa-test" 2s 243ms

And Expand "GLUE_FACTORY" notification section 251ms

And Select all notifications in "GLUE_FACTORY" section 500ms

Then Save user details 487ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 154ms

After Hooks.rollbackAddedAuthorities() 039ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@cleanUserDetailsAfterTest	426	3	9	0	0	438	42	3	45	47m 26s 820ms	Failed

Tag Report