Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.61	16 sie 2021, 05:45

	Steps	Scenarios	Features
@cleanUserDetailsAfterTest	426	3	9	0	0	438	42	3	45	46m 58s 183ms	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" 097ms

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

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

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

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

Then Go to "INVITATIONS_TAB" 204ms

And Go to invitation details 059ms

Then Reject invitation by button as user 109ms

When If user is login then logout 085ms

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

And Go to "INVITATIONS_TAB" 190ms

And Go to "REJECTED_TAB" invitation status tab 087ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 021ms

After Hooks.cleanUserDetailsAfterTest() 169ms

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

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

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

And Go to "INVITATIONS_TAB" 162ms

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

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 038ms

Hooks

After Hooks.deleteInvitationAfterTest() 036ms

After Hooks.cleanUserDetailsAfterTest() 224ms

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

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

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

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

And Show all transport types 1s 042ms

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

And Set advice window in schedule 2s 477ms

And Fill advice form 13s 967ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.cleanUserDetailsAfterTest() 151ms

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

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

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

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

And Set advice window in schedule 2s 630ms

And Fill advice form 10s 585ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

After Hooks.cleanUserDetailsAfterTest() 170ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

And Show all transport types 1s 039ms

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

And Set advice window in schedule 2s 465ms

And Fill advice form 15s 352ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

After Hooks.cleanUserDetailsAfterTest() 228ms

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

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

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

And Show all transport types 1s 045ms

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

And Go to "TRANSPORT_TABLE" 221ms

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

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

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

And Fill transport form 4s 721ms

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

And Expand advice panel 120ms

And Edit advice in transport details 14s 552ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

After Hooks.cleanUserDetailsAfterTest() 169ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

And Show all transport types 1s 046ms

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

And Go to "TRANSPORT_TABLE" 245ms

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

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

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

And Fill transport form 1m 2s 286ms

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

And Expand advice panel 126ms

And Edit advice in transport details 6s 584ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 134ms

After Hooks.cleanUserDetailsAfterTest() 144ms

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

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

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

And Show all transport types 1s 042ms

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

And Go to "TRANSPORT_TABLE" 214ms

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

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

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

And Fill transport form 26s 065ms

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

And Expand advice panel 114ms

And Edit advice in transport details 20s 729ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

After Hooks.cleanUserDetailsAfterTest() 205ms

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

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

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

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

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

Then Check if user got a mail 000ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

After Hooks.cleanUserDetailsAfterTest() 155ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

After Hooks.cleanUserDetailsAfterTest() 255ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 136ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 150ms

After Hooks.cleanUserDetailsAfterTest() 282ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

After Hooks.cleanUserDetailsAfterTest() 290ms

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

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

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

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

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

And Wait till auction end 1m 58s 018ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

After Hooks.cleanUserDetailsAfterTest() 292ms

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

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

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

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

And Wait till auction end 1m 58s 017ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

After Hooks.cleanUserDetailsAfterTest() 192ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

After Hooks.cleanUserDetailsAfterTest() 271ms

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

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 1m 57s 348ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

After Hooks.cleanUserDetailsAfterTest() 312ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

After Hooks.cleanUserDetailsAfterTest() 240ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

After Hooks.cleanUserDetailsAfterTest() 261ms

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

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

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

And Go to "TRANSPORT_TABLE" 143ms

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

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

And Fill transport form 37s 936ms

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

And Fill discrepancy report section 49s 583ms

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

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

And Generate discrepancy report 18s 260ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 142ms

After Hooks.cleanUserDetailsAfterTest() 435ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 300ms

After Hooks.deleteModeOfTransportationAfterTest() 097ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 304ms

After Hooks.deleteModeOfTransportationAfterTest() 066ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 839ms

And Select warehouse "Serownia" 1s 402ms

And Set week view 1s 100ms

And Show yesterday 1s 057ms

And Move window into the past 300ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

After Hooks.cleanUserDetailsAfterTest() 304ms

After Hooks.rollbackAddedAuthorities() 021ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after transport creation

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 078ms

After Hooks.cleanUserDetailsAfterTest() 296ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

After Hooks.cleanUserDetailsAfterTest() 325ms

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

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

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

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

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

After Hooks.cleanUserDetailsAfterTest() 291ms

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

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

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

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

After Hooks.cleanUserDetailsAfterTest() 241ms

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

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

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

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

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

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

Then If user is login then logout 297ms

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

And Go to auction details 1s 224ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 232ms

After Hooks.cleanUserDetailsAfterTest() 356ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

After Hooks.cleanUserDetailsAfterTest() 340ms

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 168ms

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

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

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

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 "CONTAINER" created in transport table and set transport id 3s 333ms

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

And Set advice window in schedule 2s 576ms

And Fill advice form 16s 780ms

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

And Go to "TRANSPORT_TABLE" 198ms

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

Then Check are advice values equals 4s 330ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

After Hooks.cleanUserDetailsAfterTest() 297ms

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

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

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

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

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

And Set advice window in schedule 2s 580ms

And Fill advice form 16s 784ms

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

And Go to "TRANSPORT_TABLE" 169ms

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

Then Check are advice values equals 4s 349ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

After Hooks.cleanUserDetailsAfterTest() 296ms

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

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

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

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

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

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

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

And Set advice window in schedule 2s 569ms

And Fill advice form 16s 825ms

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

And Go to "TRANSPORT_TABLE" 209ms

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

Then Check are advice values equals 4s 348ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

After Hooks.cleanUserDetailsAfterTest() 297ms

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 "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 318ms

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

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 2s 864ms

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

And Set advice window in schedule 2s 545ms

And Fill advice form 16s 719ms

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

And Go to "TRANSPORT_TABLE" 266ms

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

Then Check are advice values equals 4s 323ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

After Hooks.cleanUserDetailsAfterTest() 359ms

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-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 841ms

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

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

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

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

And Set advice window in schedule 30s 085ms

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.kvqJxu}, 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: 4173b0ad7ec9fb2f65894ed44dba0448
*** 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() 099ms

After Hooks.cleanUserDetailsAfterTest() 223ms

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

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

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

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

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

And Set advice window in schedule 2s 538ms

And Fill advice form 16s 830ms

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

And Go to "TRANSPORT_TABLE" 184ms

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

Hooks

After Hooks.deleteTransportAfterTest() 103ms

After Hooks.cleanUserDetailsAfterTest() 276ms

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

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

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

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

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

And Set advice window in schedule 2s 579ms

And Fill advice form 16s 740ms

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

And Go to "TRANSPORT_TABLE" 184ms

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

Hooks

After Hooks.deleteTransportAfterTest() 103ms

After Hooks.cleanUserDetailsAfterTest() 296ms

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

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

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 5s 791ms

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

And Set advice window in schedule 2s 553ms

And Fill advice form 16s 698ms

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

And Go to "TRANSPORT_TABLE" 221ms

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

Hooks

After Hooks.deleteTransportAfterTest() 099ms

After Hooks.cleanUserDetailsAfterTest() 290ms

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

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

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

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

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

And Set advice window in schedule 2s 557ms

And Fill advice form 16s 792ms

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

And Go to "TRANSPORT_TABLE" 251ms

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

Hooks

After Hooks.deleteTransportAfterTest() 126ms

After Hooks.cleanUserDetailsAfterTest() 375ms

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

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

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

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

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

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

And Set advice window in schedule 2s 570ms

And Fill advice form 16s 795ms

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

And Go to "TRANSPORT_TABLE" 179ms

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

Hooks

After Hooks.deleteTransportAfterTest() 114ms

After Hooks.cleanUserDetailsAfterTest() 235ms

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

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

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

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

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

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

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

When Reject status: Book of disinfection 087ms

And Check if reject date is visible 266ms

Then If user is login then logout 286ms

And Login as "lantmannen-admin" 869ms

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

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

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

And Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

After Hooks.cleanUserDetailsAfterTest() 186ms

After Hooks.rollbackWarehousesAccess() 114ms

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

And Prepare login page 194ms

And Click remind password button 086ms

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

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

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

And Extract password from mailgun mail 4s 042ms

And Reset password from link 723ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 150ms

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

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

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

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

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

Then Save user details 258ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 107ms

After Hooks.rollbackAddedAuthorities() 044ms

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

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

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

And Expand "other" notification section 434ms

And Select all notifications in "other" section 097ms

Then Save user details 389ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 148ms

After Hooks.rollbackAddedAuthorities() 021ms

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

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

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

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

And Go to "USERS_TAB" 901ms

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

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

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

Then Save user details 248ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 098ms

After Hooks.rollbackAddedAuthorities() 034ms

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

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

When Login as "swisskrono-tradesman@qa.qa-test" 1s 911ms

And Go to "USERS_TAB" 742ms

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

And Expand "GLUE_FACTORY" notification section 250ms

And Select all notifications in "GLUE_FACTORY" section 542ms

Then Save user details 513ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 149ms

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	46m 58s 183ms	Failed

Tag Report