Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.112	10 sie 2021, 05:53

	Steps	Scenarios	Features
@cleanUserDetailsAfterTest	406	6	26	0	0	438	39	6	45	52m 28s 773ms	Failed

View Feature Invitation

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

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

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

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

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /invitations; status: 422, komunikat: [errors:[Niezgodny numer NIP! W platformie istnieje już użytkownik z podanym adresem mailowym (loginem). Jest on przypisany do firmy Piast Cargo Transport Sp. z o.o., NIP: . Prosimy o poprawienie danych.]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Invitation.RegistrationTest.createInvitationByJSONFile(RegistrationTest.java:63)
	at ✽.Create invitation by JSON file "super-admin-alrec" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION"(file:Features/Atom/Invitations/Invitation.feature:176)

When Login as "piast-admin" 000ms

Then Go to "INVITATIONS_TAB" 000ms

And Go to invitation details 000ms

Then Reject invitation by button as user 000ms

When If user is login then logout 000ms

Then Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 000ms

And Go to "INVITATIONS_TAB" 000ms

And Go to "REJECTED_TAB" invitation status tab 000ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 000ms

After Hooks.cleanUserDetailsAfterTest() 964ms

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

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

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

And Go to "INVITATIONS_TAB" 453ms

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

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 105ms

Hooks

After Hooks.deleteInvitationAfterTest() 189ms

After Hooks.cleanUserDetailsAfterTest() 1s 292ms

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

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

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

And Show all transport types 1s 182ms

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

And Set advice window in schedule 3s 393ms

And Fill advice form 16s 986ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 283ms

After Hooks.deleteTransportAfterTest() 782ms

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

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

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

And Show all transport types 1s 175ms

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

And Set advice window in schedule 3s 368ms

And Fill advice form 12s 923ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 124ms

After Hooks.deleteTransportAfterTest() 788ms

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

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 2s 082ms

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

And Show all transport types 1s 168ms

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

And Set advice window in schedule 3s 235ms

And Fill advice form 18s 591ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 579ms

After Hooks.deleteTransportAfterTest() 745ms

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

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

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

And Show all transport types 1s 176ms

And Create advice "ADVICE_CONTAINER" "CONTAINER" "super-admin-adama" 53s 691ms

And Go to "TRANSPORT_TABLE" 457ms

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

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

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

And Fill transport form 5s 149ms

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

And Expand advice panel 271ms

And Edit advice in transport details 17s 418ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 425ms

After Hooks.deleteTransportAfterTest() 765ms

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

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

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

And Show all transport types 1s 147ms

And Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast" 50s 394ms

And Go to "TRANSPORT_TABLE" 488ms

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

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

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

And Fill transport form 1m 8s 612ms

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

And Expand advice panel 278ms

And Edit advice in transport details 8s 057ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 170ms

After Hooks.deleteTransportAfterTest() 922ms

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

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

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

And Show all transport types 1s 176ms

And Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 55s 316ms

And Go to "TRANSPORT_TABLE" 396ms

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

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

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

And Fill transport form 28s 753ms

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

And Expand advice panel 244ms

And Edit advice in transport details 23s 671ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 756ms

After Hooks.deleteTransportAfterTest() 770ms

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

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

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

And Confirm status "ARRIVAL" by Public API "v1" 1s 200ms

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

Then Check if user got a mail 000ms

And Confirm status "DEPARTURE" by Public API "v1" 1s 369ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 947ms

After Hooks.deleteTransportAfterTest() 799ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 702ms

After Hooks.deleteTransportAfterTest() 704ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 412ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 064ms

After Hooks.deleteTransportAfterTest() 761ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 070ms

After Hooks.deleteTransportAfterTest() 568ms

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

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

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

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

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

And Wait till auction end 1m 57s 016ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 411ms

After Hooks.deleteTransportAfterTest() 648ms

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

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

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

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

And Wait till auction end 1m 57s 015ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 372ms

After Hooks.deleteTransportAfterTest() 618ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 089ms

After Hooks.deleteTransportAfterTest() 633ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 308ms

After Hooks.deleteTransportAfterTest() 578ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 133ms

After Hooks.deleteTransportAfterTest() 604ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @FLAKY-A-7898

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

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

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

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

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /auctions; status: 422, komunikat: [errors:[Termin zakończenia aukcji musi się znajdować w przyszłości]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Transport.AuctionTransport.setTransportOnAuction(AuctionTransport.java:54)
	at CucumberTests.Transport.AuctionTransport.setTransportOnAuctionByApiWith(AuctionTransport.java:71)
	at ✽.Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" and finish of auction in "121" minutes(file:Features/Atom/Mail/AuctionMail.feature:103)

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 050ms

After Hooks.deleteTransportAfterTest() 629ms

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

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

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

And Go to "TRANSPORT_TABLE" 415ms

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

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

And Fill transport form 43s 005ms

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

And Fill discrepancy report section 52s 357ms

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

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

And Generate discrepancy report 22s 268ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 394ms

After Hooks.deleteTransportAfterTest() 969ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 545ms

After Hooks.deleteModeOfTransportationAfterTest() 376ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 552ms

After Hooks.deleteModeOfTransportationAfterTest() 322ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 463ms

And Select warehouse "Serownia" 1s 697ms

And Set week view 1s 223ms

And Show yesterday 1s 183ms

And Move window into the past 403ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 560ms

After Hooks.deleteTransportAfterTest() 779ms

After Hooks.rollbackAddedAuthorities() 193ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 203ms

After Hooks.deleteTransportAfterTest() 547ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 290ms

After Hooks.deleteTransportAfterTest() 591ms

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

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

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

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

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='PASS'] (tried for 10 second(s) with 500 MILLISECONDS interval)
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=91.0.4472.101 (af52a90bf87030dd1523486a1cd3ae25c5d76c9b-refs/branch-heads/4472@{#1462}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.LZIrwc}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=91.0.4472.164, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 42bf766b86c071969f04804edb2a59a0
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:215)
	at Pages.Transport.TransportsPage.transferTransportToCarrier(TransportsPage.java:285)
	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.cleanUserDetailsAfterTest() 2s 125ms

After Hooks.deleteTransportAfterTest() 632ms

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

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

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

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

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='PASS'] (tried for 10 second(s) with 500 MILLISECONDS interval)
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=91.0.4472.101 (af52a90bf87030dd1523486a1cd3ae25c5d76c9b-refs/branch-heads/4472@{#1462}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.LZIrwc}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=91.0.4472.164, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 42bf766b86c071969f04804edb2a59a0
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:215)
	at Pages.Transport.TransportsPage.transferTransportToCarrier(TransportsPage.java:285)
	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.cleanUserDetailsAfterTest() 2s 054ms

After Hooks.deleteTransportAfterTest() 626ms

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

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

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

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

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

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

Then If user is login then logout 244ms

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

And Go to auction details 1s 998ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 077ms

After Hooks.deleteTransportAfterTest() 775ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 823ms

After Hooks.deleteTransportAfterTest() 668ms

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 241ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 334ms

And Fill advice form 20s 372ms

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

And Go to "TRANSPORT_TABLE" 464ms

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

Then Check are advice values equals 4s 986ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 292ms

After Hooks.deleteTransportAfterTest() 787ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 409ms

And Fill advice form 20s 334ms

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

And Go to "TRANSPORT_TABLE" 469ms

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

Then Check are advice values equals 4s 953ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 153ms

After Hooks.deleteTransportAfterTest() 782ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 295ms

And Fill advice form 20s 339ms

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

And Go to "TRANSPORT_TABLE" 469ms

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

Then Check are advice values equals 4s 940ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 545ms

After Hooks.deleteTransportAfterTest() 858ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 571ms

And Fill advice form 20s 290ms

And Click advice save button and wait for advice form to disappear 18s 364ms

And Go to "TRANSPORT_TABLE" 478ms

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

Then Check are advice values equals 4s 941ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 653ms

After Hooks.deleteTransportAfterTest() 888ms

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

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

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

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

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

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

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

And Set advice window in schedule 30s 118ms

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=91.0.4472.164)
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=91.0.4472.101 (af52a90bf87030dd1523486a1cd3ae25c5d76c9b-refs/branch-heads/4472@{#1462}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.LZIrwc}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=91.0.4472.164, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 42bf766b86c071969f04804edb2a59a0
*** 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.cleanUserDetailsAfterTest() 1s 759ms

After Hooks.deleteTransportAfterTest() 564ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 394ms

And Fill advice form 20s 322ms

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

And Go to "TRANSPORT_TABLE" 493ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 144ms

After Hooks.deleteTransportAfterTest() 795ms

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

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

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

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

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

And Check is transport "CONTAINER" created in transport table and set transport id 4s 007ms

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

And Set advice window in schedule 3s 355ms

And Fill advice form 20s 438ms

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

And Go to "TRANSPORT_TABLE" 413ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 479ms

After Hooks.deleteTransportAfterTest() 814ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 412ms

And Fill advice form 20s 367ms

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

And Go to "TRANSPORT_TABLE" 501ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 140ms

After Hooks.deleteTransportAfterTest() 794ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

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

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

And Set advice window in schedule 3s 437ms

And Fill advice form 20s 469ms

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

And Go to "TRANSPORT_TABLE" 471ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 972ms

After Hooks.deleteTransportAfterTest() 793ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 407ms

And Fill advice form 20s 323ms

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

And Go to "TRANSPORT_TABLE" 458ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 735ms

After Hooks.deleteTransportAfterTest() 776ms

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

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

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

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

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

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

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

When Reject status: Book of disinfection 192ms

And Check if reject date is visible 986ms

Then If user is login then logout 724ms

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

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

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

And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nieaktualna księga mycia i dezynfekcji" 6s 070ms

And Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 154ms

After Hooks.deleteTransportAfterTest() 776ms

After Hooks.rollbackWarehousesAccess() 722ms

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

And Prepare login page 050ms

And Click remind password button 15s 092ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//span[@data-button-name='remind-password']"}
  (Session info: headless chrome=91.0.4472.164)
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=91.0.4472.101 (af52a90bf87030dd1523486a1cd3ae25c5d76c9b-refs/branch-heads/4472@{#1462}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.LZIrwc}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=91.0.4472.164, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 42bf766b86c071969f04804edb2a59a0
*** Element info: {Using=xpath, value=//span[@data-button-name='remind-password']}
	at sun.reflect.GeneratedConstructorAccessor217.newInstance(Unknown Source)
	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.LoginTest.clickRemindPasswordButton(LoginTest.java:126)
	at ✽.Click remind password button(file:Features/Atom/Users/User.feature:81)

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Restart hasła! | Password reset!" 000ms

And Extract password from mail 000ms

And Reset password from link 000ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 000ms

Error message

java.lang.NullPointerException
	at Utils.JsonApiUtil.editJsonTextNode(JsonApiUtil.java:158)
	at CucumberTests.Hooks.cleanUserDetailsAfterTest(Hooks.java:334)
	at sun.reflect.GeneratedMethodAccessor263.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at cucumber.runtime.Utils$1.call(Utils.java:26)
	at cucumber.runtime.Timeout.timeout(Timeout.java:16)
	at cucumber.runtime.Utils.invoke(Utils.java:20)
	at cucumber.runtime.java.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	at cucumber.runner.Runner.runPickle(Runner.java:40)
	at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)

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

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

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

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

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

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

Then Save user details 1s 036ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 657ms

After Hooks.rollbackAddedAuthorities() 266ms

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

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

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

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

And Expand "other" notification section 2s 558ms

And Select all notifications in "other" section 271ms

Then Save user details 1s 476ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 882ms

After Hooks.rollbackAddedAuthorities() 146ms

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

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

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

When Login as "adama-buyer@qa.qa-test" 4s 912ms

And Go to "USERS_TAB" 2s 765ms

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

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

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

Then Save user details 994ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 651ms

After Hooks.rollbackAddedAuthorities() 230ms

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

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

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

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

And Go to "USERS_TAB" 1s 527ms

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

And Expand "GLUE_FACTORY" notification section 557ms

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

Then Save user details 1s 793ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 054ms

After Hooks.rollbackAddedAuthorities() 246ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@cleanUserDetailsAfterTest	406	6	26	0	0	438	39	6	45	52m 28s 773ms	Failed

Tag Report