Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.134	26 sie 2021, 07:47

	Steps	Scenarios	Features
@cleanUserDetailsAfterTest	426	2	10	0	0	438	43	2	45	56m 8s 820ms	Failed

View Feature Invitation

@deleteInvitationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if rejected invitation is visible in rejected tab

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

When Login as "piast-admin" 5s 019ms

Then Go to "INVITATIONS_TAB" 645ms

And Go to invitation details 147ms

Then Reject invitation by button as user 299ms

When If user is login then logout 259ms

Then Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 4s 893ms

And Go to "INVITATIONS_TAB" 506ms

And Go to "REJECTED_TAB" invitation status tab 328ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 146ms

After Hooks.cleanUserDetailsAfterTest() 1s 247ms

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

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

When Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 2s 338ms

And Go to "INVITATIONS_TAB" 417ms

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

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 096ms

Hooks

After Hooks.deleteInvitationAfterTest() 193ms

After Hooks.cleanUserDetailsAfterTest() 1s 261ms

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" 2s 466ms

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

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 2s 246ms

And Set "advice" inputs from JSON file "ADVICE_CONTAINER" "super-admin-adama" 001ms

And Show all transport types 1s 173ms

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

And Set advice window in schedule 3s 324ms

And Fill advice form 17s 226ms

And Click advice save button and wait for advice form to disappear 33s 862ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 258ms

After Hooks.deleteTransportAfterTest() 755ms

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" 2s 667ms

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

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

And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 001ms

And Show all transport types 1s 220ms

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

And Set advice window in schedule 3s 462ms

And Fill advice form 12s 936ms

And Click advice save button and wait for advice form to disappear 33s 276ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 036ms

After Hooks.deleteTransportAfterTest() 809ms

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" 2s 734ms

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

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

And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-keeeper" 001ms

And Show all transport types 1s 122ms

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

And Set advice window in schedule 3s 270ms

And Fill advice form 18s 765ms

And Click advice save button and wait for advice form to disappear 33s 275ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 496ms

After Hooks.deleteTransportAfterTest() 723ms

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" 4s 885ms

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

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

And Show all transport types 1s 135ms

And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-adama" 3s 285ms

And Go to "TRANSPORT_TABLE" 372ms

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

And Set "transport" inputs from JSON file "EDIT_CONTAINER" "super-admin-adama" 001ms

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

And Fill transport form 5s 184ms

And Set "advice" inputs from JSON file "EDIT_ADVICE_CONTAINER" "super-admin-adama" 001ms

And Expand advice panel 281ms

And Edit advice in transport details 17s 629ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 252ms

After Hooks.deleteTransportAfterTest() 716ms

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" 5s 520ms

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

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 032ms

And Show all transport types 1s 156ms

And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 3s 458ms

And Go to "TRANSPORT_TABLE" 427ms

And Go to transport details "DELIVERY" 3s 055ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-piast" 001ms

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

And Fill transport form 1m 8s 829ms

And Set "advice" inputs from JSON file "EDIT_ADVICE_DELIVERY" "super-admin-piast" 001ms

And Expand advice panel 249ms

And Edit advice in transport details 8s 187ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 124ms

After Hooks.deleteTransportAfterTest() 948ms

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" 5s 695ms

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

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

And Show all transport types 1s 167ms

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD" as "super-admin-keeeper" 3s 280ms

And Go to "TRANSPORT_TABLE" 381ms

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

And Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-keeeper" 000ms

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

And Fill transport form 28s 677ms

And Set "advice" inputs from JSON file "EDIT_ADVICE_LOAD" "super-admin-keeeper" 001ms

And Expand advice panel 277ms

And Edit advice in transport details 23s 481ms

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 2m 47s 350ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 615ms

After Hooks.deleteTransportAfterTest() 799ms

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

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 2s 755ms

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

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania PUT pod adresem /transports/228881130/confirm/ARRIVAL - status odpowiedzi: 422 , komunikat:  [errors:[Status nie może być potwierdzony poza kolejnością.]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.putObjectToPublicApi(RestUtil.java:162)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusByAPI(ConfirmStatuses.java:102)
	at ✽.Confirm status "ARRIVAL" by Public API "v1"(file:Features/Atom/Mail/AdviceMail.feature:51)

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

Then Check if user got a mail 000ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 957ms

After Hooks.deleteTransportAfterTest() 860ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 692ms

After Hooks.deleteTransportAfterTest() 751ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 419ms

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" 4s 761ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 099ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 124ms

After Hooks.deleteTransportAfterTest() 686ms

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" 2s 573ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 124ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 055ms

After Hooks.deleteTransportAfterTest() 573ms

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" 12s 382ms

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 156ms

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

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

And Wait till auction end 1m 57s 017ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Dodano nową ofertę" 3m 24s 472ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 371ms

After Hooks.deleteTransportAfterTest() 602ms

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" 2s 667ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 104ms

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

And Wait till auction end 1m 57s 016ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 404ms

After Hooks.deleteTransportAfterTest() 612ms

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" 4s 932ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 049ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 834ms

After Hooks.deleteTransportAfterTest() 536ms

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" 2s 575ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 049ms

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 302ms

After Hooks.deleteTransportAfterTest() 584ms

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" 2s 562ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 059ms

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 040ms

After Hooks.deleteTransportAfterTest() 563ms

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" 5s 129ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 079ms

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zakończenie aukcji" 1m 2s 703ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 053ms

After Hooks.deleteTransportAfterTest() 667ms

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" 3s 204ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 062ms

And Go to "TRANSPORT_TABLE" 413ms

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

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Fill transport form 43s 033ms

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

And Fill discrepancy report section 52s 547ms

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

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

And Generate discrepancy report 21s 598ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 405ms

After Hooks.deleteTransportAfterTest() 915ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 481ms

After Hooks.deleteModeOfTransportationAfterTest() 377ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 473ms

After Hooks.deleteModeOfTransportationAfterTest() 297ms

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" 8s 984ms

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

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 133ms

And Go to "WAREHOUSE_TAB" 1s 358ms

And Select warehouse "Serownia" 1s 807ms

And Set week view 1s 228ms

And Show yesterday 1s 160ms

And Move window into the past 439ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "spóźnił się na" 1m 4s 699ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 372ms

After Hooks.deleteTransportAfterTest() 802ms

After Hooks.rollbackAddedAuthorities() 170ms

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" 9s 399ms

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

And Wait "60" seconds 1m

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 171ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 146ms

After Hooks.deleteTransportAfterTest() 560ms

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" 7s 646ms

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

And Wait "60" seconds 1m

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 222ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica eksport" 1m 5s 839ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 367ms

After Hooks.deleteTransportAfterTest() 554ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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" 2s 496ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 080ms

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zlecenie czeka na akceptację" 5s 879ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 047ms

After Hooks.deleteTransportAfterTest() 791ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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" 2s 524ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 075ms

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zostało przekazane nowe zlecenie" 5s 837ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 024ms

After Hooks.deleteTransportAfterTest() 546ms

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" 7s 490ms

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 130ms

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

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

And Add a bid "500" to an auction by JSON file as "pskza2-carrier-2@qa.qa-test" for "pskza2-carrier-2@qa.qa-test" 1s 216ms

Then If user is login then logout 260ms

And Login as "swisskrono-admin" 2s 825ms

And Go to auction details 2s 196ms

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

And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 36s 816ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 716ms

After Hooks.deleteTransportAfterTest() 847ms

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" 2s 687ms

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 149ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 768ms

After Hooks.deleteTransportAfterTest() 628ms

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 247ms

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" 2s 618ms

And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 001ms

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

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

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms

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

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

And Set advice window in schedule 3s 371ms

And Fill advice form 20s 466ms

And Click advice save button and wait for advice form to disappear 33s 296ms

And Go to "TRANSPORT_TABLE" 456ms

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

Then Check are advice values equals 5s 003ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 292ms

After Hooks.deleteTransportAfterTest() 786ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it possible to advice transport when transport is created by sk API

The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 001ms

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

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

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 146ms

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

And Set advice window in schedule 3s 372ms

And Fill advice form 20s 452ms

And Click advice save button and wait for advice form to disappear 33s 299ms

And Go to "TRANSPORT_TABLE" 407ms

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

Then Check are advice values equals 4s 984ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 099ms

After Hooks.deleteTransportAfterTest() 766ms

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" 7s 335ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

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

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

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 382ms

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

And Set advice window in schedule 3s 372ms

And Fill advice form 20s 231ms

And Click advice save button and wait for advice form to disappear 33s 239ms

And Go to "TRANSPORT_TABLE" 545ms

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

Then Check are advice values equals 4s 982ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 267ms

After Hooks.deleteTransportAfterTest() 800ms

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

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

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

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

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 6s 942ms

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

And Set advice window in schedule 3s 398ms

And Fill advice form 20s 438ms

And Click advice save button and wait for advice form to disappear 33s 289ms

And Go to "TRANSPORT_TABLE" 518ms

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

Then Check are advice values equals 4s 911ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 704ms

After Hooks.deleteTransportAfterTest() 784ms

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" 7s 400ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

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

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

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 611ms

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

And Set advice window in schedule 30s 128ms

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-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.rNCjAh}, 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: 017e07f8d4913bdd7b848b708fa6e3cd
*** Element info: {Using=xpath, value=//button[@data-button-name='SHIFT_RIGHT_DAY']}
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:356)
	at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:458)
	at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
	at Pages.BasePage.getWebElementByXpath(BasePage.java:325)
	at CucumberTests.Transport.AdviceTransport.setAdviceWindowInSchedule(AdviceTransport.java:82)
	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.cleanUserDetailsAfterTest() 1s 770ms

After Hooks.deleteTransportAfterTest() 544ms

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

And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 001ms

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

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

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 215ms

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

And Set advice window in schedule 3s 321ms

And Fill advice form 20s 491ms

And Click advice save button and wait for advice form to disappear 33s 280ms

And Go to "TRANSPORT_TABLE" 463ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 184ms

After Hooks.deleteTransportAfterTest() 802ms

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" 7s 459ms

And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 001ms

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

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

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms

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

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

And Set advice window in schedule 3s 351ms

And Fill advice form 20s 424ms

And Click advice save button and wait for advice form to disappear 33s 295ms

And Go to "TRANSPORT_TABLE" 419ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 282ms

After Hooks.deleteTransportAfterTest() 790ms

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" 7s 374ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

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

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

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 373ms

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

And Set advice window in schedule 3s 357ms

And Fill advice form 20s 597ms

And Click advice save button and wait for advice form to disappear 33s 244ms

And Go to "TRANSPORT_TABLE" 449ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 106ms

After Hooks.deleteTransportAfterTest() 797ms

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" 6s 331ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

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

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

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 002ms

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

And Set advice window in schedule 3s 327ms

And Fill advice form 20s 544ms

And Click advice save button and wait for advice form to disappear 33s 322ms

And Go to "TRANSPORT_TABLE" 523ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 919ms

After Hooks.deleteTransportAfterTest() 813ms

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" 8s 522ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

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

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

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 543ms

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

And Set advice window in schedule 3s 393ms

And Fill advice form 20s 303ms

And Click advice save button and wait for advice form to disappear 33s 857ms

And Go to "TRANSPORT_TABLE" 458ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 681ms

After Hooks.deleteTransportAfterTest() 831ms

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" 4s 542ms

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

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

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

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 930ms

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

When Reject status: Book of disinfection 200ms

And Check if reject date is visible 1s 030ms

Then If user is login then logout 671ms

And Login as "lantmannen-admin" 2s 239ms

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

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

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

And Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 381ms

After Hooks.deleteTransportAfterTest() 774ms

After Hooks.rollbackWarehousesAccess() 736ms

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

And Prepare login page 372ms

And Click remind password button 276ms

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

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

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

And Extract password from mailgun mail 4s 937ms

And Reset password from link 1s 670ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 968ms

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

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

When Login as "oaa1-receiver-2@qa.qa-test" 4s 427ms

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

And Change user details "email" to "newEmailAddress@newEmail.com" 1s 156ms

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

Then Save user details 1s 021ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 655ms

After Hooks.rollbackAddedAuthorities() 250ms

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

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

When Login as "pskza1-carrier-2@qa.qa-test" 7s 414ms

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

And Expand "other" notification section 2s 385ms

And Select all notifications in "other" section 292ms

Then Save user details 1s 498ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 885ms

After Hooks.rollbackAddedAuthorities() 160ms

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

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

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

When Login as "adama-buyer@qa.qa-test" 5s 306ms

And Go to "USERS_TAB" 1s 539ms

And Find user "oaa1-receiver@qa.qa-test" 3s 715ms

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

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

Then Save user details 1s 057ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 644ms

After Hooks.rollbackAddedAuthorities() 248ms

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

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

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

When Login as "swisskrono-tradesman@qa.qa-test" 9s 099ms

And Go to "USERS_TAB" 1s 604ms

And Find user "pskza1-carrier@qa.qa-test" 3s 671ms

And Expand "GLUE_FACTORY" notification section 564ms

And Select all notifications in "GLUE_FACTORY" section 1s 532ms

Then Save user details 1s 777ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 063ms

After Hooks.rollbackAddedAuthorities() 249ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@cleanUserDetailsAfterTest	426	2	10	0	0	438	43	2	45	56m 8s 820ms	Failed

Tag Report