Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.59	14 sie 2021, 05:45

	Steps	Scenarios	Features
@cleanUserDetailsAfterTest	426	3	9	0	0	438	42	3	45	47m 55s 310ms	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" 105ms

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

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

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

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

Then Go to "INVITATIONS_TAB" 192ms

And Go to invitation details 070ms

Then Reject invitation by button as user 110ms

When If user is login then logout 310ms

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

And Go to "INVITATIONS_TAB" 178ms

And Go to "REJECTED_TAB" invitation status tab 088ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 020ms

After Hooks.cleanUserDetailsAfterTest() 147ms

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

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

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

And Go to "INVITATIONS_TAB" 167ms

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

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 041ms

Hooks

After Hooks.deleteInvitationAfterTest() 036ms

After Hooks.cleanUserDetailsAfterTest() 222ms

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 002ms

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

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

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

And Show all transport types 1s 045ms

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

And Set advice window in schedule 2s 448ms

And Fill advice form 14s 019ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

After Hooks.cleanUserDetailsAfterTest() 177ms

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 239ms

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

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

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

And Show all transport types 1s 039ms

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

And Set advice window in schedule 2s 621ms

And Fill advice form 10s 511ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

After Hooks.cleanUserDetailsAfterTest() 157ms

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 195ms

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

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

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

And Show all transport types 1s 048ms

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

And Set advice window in schedule 2s 440ms

And Fill advice form 15s 331ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

After Hooks.cleanUserDetailsAfterTest() 229ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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

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

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

And Show all transport types 1s 046ms

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

And Go to "TRANSPORT_TABLE" 216ms

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

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

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

And Fill transport form 4s 717ms

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

And Expand advice panel 118ms

And Edit advice in transport details 14s 558ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

After Hooks.cleanUserDetailsAfterTest() 182ms

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 651ms

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

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

And Show all transport types 1s 039ms

And Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast" 44s 009ms

And Go to "TRANSPORT_TABLE" 208ms

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

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

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

And Fill transport form 1m 2s 321ms

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

And Expand advice panel 108ms

And Edit advice in transport details 6s 609ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 141ms

After Hooks.cleanUserDetailsAfterTest() 157ms

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 711ms

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

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

And Show all transport types 1s 049ms

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

And Go to "TRANSPORT_TABLE" 189ms

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

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

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

And Fill transport form 25s 984ms

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

And Expand advice panel 105ms

And Edit advice in transport details 20s 720ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

After Hooks.cleanUserDetailsAfterTest() 218ms

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

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

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

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

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

Then Check if user got a mail 000ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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) 000ms

Steps

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

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 170ms

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

After Hooks.cleanUserDetailsAfterTest() 242ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 130ms

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 557ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 156ms

After Hooks.cleanUserDetailsAfterTest() 269ms

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 055ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

After Hooks.cleanUserDetailsAfterTest() 246ms

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 532ms

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

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 125ms

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

And Wait till auction end 1m 58s 018ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

After Hooks.cleanUserDetailsAfterTest() 293ms

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 191ms

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

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

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

And Wait till auction end 1m 58s 017ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

After Hooks.cleanUserDetailsAfterTest() 171ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing first place in auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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 116ms

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

After Hooks.cleanUserDetailsAfterTest() 261ms

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 189ms

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

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 115ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

After Hooks.cleanUserDetailsAfterTest() 303ms

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 188ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

After Hooks.cleanUserDetailsAfterTest() 272ms

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 705ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

After Hooks.cleanUserDetailsAfterTest() 243ms

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 418ms

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

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

And Go to "TRANSPORT_TABLE" 139ms

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

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

And Fill transport form 37s 941ms

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

And Fill discrepancy report section 49s 592ms

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

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

And Generate discrepancy report 18s 837ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 151ms

After Hooks.cleanUserDetailsAfterTest() 476ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 310ms

After Hooks.deleteModeOfTransportationAfterTest() 089ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 299ms

After Hooks.deleteModeOfTransportationAfterTest() 060ms

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 445ms

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

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

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

And Go to "WAREHOUSE_TAB" 843ms

And Select warehouse "Serownia" 1s 413ms

And Set week view 1s 098ms

And Show yesterday 1s 055ms

And Move window into the past 296ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

After Hooks.cleanUserDetailsAfterTest() 304ms

After Hooks.rollbackAddedAuthorities() 022ms

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 225ms

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

After Hooks.cleanUserDetailsAfterTest() 288ms

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 884ms

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

After Hooks.cleanUserDetailsAfterTest() 278ms

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 171ms

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

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

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

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() 080ms

After Hooks.cleanUserDetailsAfterTest() 268ms

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 018ms

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

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

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

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() 085ms

After Hooks.cleanUserDetailsAfterTest() 249ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing inquiry

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

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 424ms

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

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

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

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

Then If user is login then logout 329ms

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

And Go to auction details 1s 225ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 220ms

After Hooks.cleanUserDetailsAfterTest() 379ms

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 304ms

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

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 139ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

After Hooks.cleanUserDetailsAfterTest() 367ms

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 173ms

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 130ms

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

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

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

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

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

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

And Set advice window in schedule 2s 627ms

And Fill advice form 16s 828ms

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

And Go to "TRANSPORT_TABLE" 187ms

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

Then Check are advice values equals 4s 337ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

After Hooks.cleanUserDetailsAfterTest() 315ms

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 935ms

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

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

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

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

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 6s 389ms

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

And Set advice window in schedule 2s 553ms

And Fill advice form 16s 784ms

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

And Go to "TRANSPORT_TABLE" 187ms

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

Then Check are advice values equals 4s 353ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

After Hooks.cleanUserDetailsAfterTest() 309ms

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 945ms

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

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

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

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

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

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

And Set advice window in schedule 2s 589ms

And Fill advice form 16s 821ms

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

And Go to "TRANSPORT_TABLE" 235ms

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

Then Check are advice values equals 4s 342ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

After Hooks.cleanUserDetailsAfterTest() 267ms

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 156ms

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

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

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

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

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

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

And Set advice window in schedule 2s 550ms

And Fill advice form 16s 832ms

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

And Go to "TRANSPORT_TABLE" 215ms

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

Then Check are advice values equals 4s 328ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

After Hooks.cleanUserDetailsAfterTest() 368ms

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) 002ms

Steps

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

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

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

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

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

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

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

And Set advice window in schedule 30s 043ms

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.MMqHmq}, 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: 50ff9f4d299490201cb806b899fcc9ff
*** 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() 063ms

After Hooks.cleanUserDetailsAfterTest() 197ms

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 871ms

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

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

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

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

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

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

And Set advice window in schedule 2s 583ms

And Fill advice form 16s 709ms

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

And Go to "TRANSPORT_TABLE" 203ms

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

Hooks

After Hooks.deleteTransportAfterTest() 102ms

After Hooks.cleanUserDetailsAfterTest() 284ms

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 844ms

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

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

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

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

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

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

And Set advice window in schedule 2s 552ms

And Fill advice form 16s 643ms

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

And Go to "TRANSPORT_TABLE" 213ms

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

Hooks

After Hooks.deleteTransportAfterTest() 108ms

After Hooks.cleanUserDetailsAfterTest() 284ms

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 935ms

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

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

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

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

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

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

And Set advice window in schedule 2s 564ms

And Fill advice form 16s 740ms

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

And Go to "TRANSPORT_TABLE" 222ms

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

Hooks

After Hooks.deleteTransportAfterTest() 092ms

After Hooks.cleanUserDetailsAfterTest() 264ms

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 767ms

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

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

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

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

And Set advice window in schedule 2s 560ms

And Fill advice form 16s 714ms

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

And Go to "TRANSPORT_TABLE" 235ms

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

Hooks

After Hooks.deleteTransportAfterTest() 132ms

After Hooks.cleanUserDetailsAfterTest() 399ms

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 035ms

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

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

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

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

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

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

And Set advice window in schedule 2s 619ms

And Fill advice form 16s 716ms

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

And Go to "TRANSPORT_TABLE" 184ms

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

Hooks

After Hooks.deleteTransportAfterTest() 125ms

After Hooks.cleanUserDetailsAfterTest() 238ms

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) 000ms

Steps

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

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

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

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

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

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

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

When Reject status: Book of disinfection 103ms

And Check if reject date is visible 310ms

Then If user is login then logout 084ms

And Login as "lantmannen-admin" 1s 293ms

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

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

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

And Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

After Hooks.cleanUserDetailsAfterTest() 188ms

After Hooks.rollbackWarehousesAccess() 106ms

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) 001ms

Steps

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

And Prepare login page 198ms

And Click remind password button 089ms

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

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

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

And Extract password from mailgun mail 4s 123ms

And Reset password from link 688ms

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

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

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

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

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

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

Then Save user details 265ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 102ms

After Hooks.rollbackAddedAuthorities() 040ms

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

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

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

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

And Expand "other" notification section 436ms

And Select all notifications in "other" section 108ms

Then Save user details 350ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 182ms

After Hooks.rollbackAddedAuthorities() 032ms

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

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

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

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

And Go to "USERS_TAB" 925ms

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

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

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

Then Save user details 243ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 106ms

After Hooks.rollbackAddedAuthorities() 043ms

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

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

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

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

And Go to "USERS_TAB" 780ms

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

And Expand "GLUE_FACTORY" notification section 259ms

And Select all notifications in "GLUE_FACTORY" section 518ms

Then Save user details 506ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 150ms

After Hooks.rollbackAddedAuthorities() 035ms

	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 55s 310ms	Failed

Tag Report