Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.120	16 sie 2021, 06:00

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

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

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

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

When Login as "piast-admin" 4s 927ms

Then Go to "INVITATIONS_TAB" 637ms

And Go to invitation details 139ms

Then Reject invitation by button as user 309ms

When If user is login then logout 5s 702ms

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

And Go to "INVITATIONS_TAB" 497ms

And Go to "REJECTED_TAB" invitation status tab 338ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 155ms

After Hooks.cleanUserDetailsAfterTest() 1s 309ms

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

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

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

And Go to "INVITATIONS_TAB" 454ms

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

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 118ms

Hooks

After Hooks.deleteInvitationAfterTest() 183ms

After Hooks.cleanUserDetailsAfterTest() 1s 287ms

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

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

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

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

And Show all transport types 1s 153ms

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

And Set advice window in schedule 3s 385ms

And Fill advice form 17s 231ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 274ms

After Hooks.deleteTransportAfterTest() 852ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 583ms

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

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

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

And Show all transport types 1s 222ms

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

And Set advice window in schedule 3s 456ms

And Fill advice form 12s 873ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 081ms

After Hooks.deleteTransportAfterTest() 771ms

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

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

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

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

And Show all transport types 1s 177ms

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

And Set advice window in schedule 3s 257ms

And Fill advice form 18s 876ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 480ms

After Hooks.deleteTransportAfterTest() 715ms

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

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

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

And Show all transport types 1s 165ms

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

And Go to "TRANSPORT_TABLE" 473ms

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

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

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

And Fill transport form 5s 184ms

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

And Expand advice panel 237ms

And Edit advice in transport details 17s 548ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 360ms

After Hooks.deleteTransportAfterTest() 796ms

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

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

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

And Show all transport types 1s 140ms

And Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast" 35s 052ms

And Go to "TRANSPORT_TABLE" 476ms

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

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

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

And Fill transport form 1m 8s 676ms

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

And Expand advice panel 258ms

And Edit advice in transport details 8s 122ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 158ms

After Hooks.deleteTransportAfterTest() 906ms

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

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

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

And Show all transport types 1s 165ms

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

And Go to "TRANSPORT_TABLE" 432ms

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

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

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

And Fill transport form 28s 726ms

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

And Expand advice panel 270ms

And Edit advice in transport details 23s 752ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 615ms

After Hooks.deleteTransportAfterTest() 757ms

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

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

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

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

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

Then Check if user got a mail 000ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 965ms

After Hooks.deleteTransportAfterTest() 801ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 696ms

After Hooks.deleteTransportAfterTest() 747ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 415ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 088ms

After Hooks.deleteTransportAfterTest() 740ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 054ms

After Hooks.deleteTransportAfterTest() 557ms

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

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

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

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

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

And Wait till auction end 1m 57s 016ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 349ms

After Hooks.deleteTransportAfterTest() 619ms

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

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

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

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

And Wait till auction end 1m 57s 017ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 416ms

After Hooks.deleteTransportAfterTest() 633ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing first place in auction

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 965ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 075ms

After Hooks.deleteTransportAfterTest() 610ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 253ms

After Hooks.deleteTransportAfterTest() 586ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 053ms

After Hooks.deleteTransportAfterTest() 594ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 285ms

After Hooks.deleteTransportAfterTest() 646ms

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

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

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

And Go to "TRANSPORT_TABLE" 430ms

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

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

And Fill transport form 43s 156ms

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

And Fill discrepancy report section 52s 532ms

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

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

And Generate discrepancy report 6s 618ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 456ms

After Hooks.deleteTransportAfterTest() 929ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 589ms

After Hooks.deleteModeOfTransportationAfterTest() 388ms

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

Steps

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 532ms

After Hooks.deleteModeOfTransportationAfterTest() 294ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 435ms

And Select warehouse "Serownia" 1s 569ms

And Set week view 1s 227ms

And Show yesterday 1s 148ms

And Move window into the past 388ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 378ms

After Hooks.deleteTransportAfterTest() 796ms

After Hooks.rollbackAddedAuthorities() 168ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 284ms

After Hooks.deleteTransportAfterTest() 555ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 139ms

After Hooks.deleteTransportAfterTest() 782ms

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

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

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

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

Error message

java.lang.AssertionError: Formularz nie zniknął! Pojawił się błędy walidacji:
[Podana data nie może być w przeszłości]
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at Pages.Transport.TransportsPage.transferTransportToCarrier(TransportsPage.java:288)
	at CucumberTests.Transport.TransferTransportTest.transferTransportToCarrier(TransferTransportTest.java:37)
	at ✽.Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true"(file:Features/Atom/Mail/TransportTransferMail.feature:8)

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 035ms

After Hooks.deleteTransportAfterTest() 636ms

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

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 493ms

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

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

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

Error message

java.lang.AssertionError: Formularz nie zniknął! Pojawił się błędy walidacji:
[Podana data nie może być w przeszłości]
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at Pages.Transport.TransportsPage.transferTransportToCarrier(TransportsPage.java:288)
	at CucumberTests.Transport.TransferTransportTest.transferTransportToCarrier(TransferTransportTest.java:37)
	at ✽.Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false"(file:Features/Atom/Mail/TransportTransferMail.feature:20)

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 069ms

After Hooks.deleteTransportAfterTest() 634ms

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

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

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

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

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

Then If user is login then logout 258ms

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

And Go to auction details 2s 221ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 110ms

After Hooks.deleteTransportAfterTest() 675ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 831ms

After Hooks.deleteTransportAfterTest() 651ms

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 378ms

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

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

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

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

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

And Check is transport "CONTAINER" created in transport table and set transport id 7s 128ms

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

And Set advice window in schedule 3s 432ms

And Fill advice form 20s 535ms

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

And Go to "TRANSPORT_TABLE" 455ms

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

Then Check are advice values equals 4s 976ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 378ms

After Hooks.deleteTransportAfterTest() 814ms

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

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

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

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

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

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 4s 157ms

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

And Set advice window in schedule 3s 387ms

And Fill advice form 20s 404ms

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

And Go to "TRANSPORT_TABLE" 508ms

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

Then Check are advice values equals 4s 967ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 170ms

After Hooks.deleteTransportAfterTest() 835ms

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

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

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

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

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

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

And Set advice window in schedule 3s 411ms

And Fill advice form 20s 523ms

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

And Go to "TRANSPORT_TABLE" 477ms

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

Then Check are advice values equals 5s 036ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 232ms

After Hooks.deleteTransportAfterTest() 779ms

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

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

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

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

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

And Set advice window in schedule 3s 412ms

And Fill advice form 20s 534ms

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

And Go to "TRANSPORT_TABLE" 470ms

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

Then Check are advice values equals 4s 983ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 713ms

After Hooks.deleteTransportAfterTest() 905ms

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

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

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

And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 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 4s 497ms

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

And Set advice window in schedule 30s 100ms

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.3zdI0E}, 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: a54bcfb9f282785de8230b0d9aa78078
*** 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 817ms

After Hooks.deleteTransportAfterTest() 538ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 417ms

And Fill advice form 20s 458ms

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

And Go to "TRANSPORT_TABLE" 454ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 132ms

After Hooks.deleteTransportAfterTest() 815ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 426ms

And Fill advice form 20s 303ms

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

And Go to "TRANSPORT_TABLE" 461ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 269ms

After Hooks.deleteTransportAfterTest() 811ms

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

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

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

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

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

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

And Set advice window in schedule 3s 375ms

And Fill advice form 20s 575ms

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

And Go to "TRANSPORT_TABLE" 482ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 233ms

After Hooks.deleteTransportAfterTest() 809ms

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

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

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

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

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

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

And Set advice window in schedule 3s 513ms

And Fill advice form 20s 508ms

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

And Go to "TRANSPORT_TABLE" 505ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 167ms

After Hooks.deleteTransportAfterTest() 848ms

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

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

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

And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 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 566ms

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

And Set advice window in schedule 3s 429ms

And Fill advice form 20s 275ms

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

And Go to "TRANSPORT_TABLE" 481ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 785ms

After Hooks.deleteTransportAfterTest() 781ms

View Feature Status rejection

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackWarehousesAccess

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 4s 564ms

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

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

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

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

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

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

When Reject status: Book of disinfection 211ms

And Check if reject date is visible 1s 007ms

Then If user is login then logout 237ms

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

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

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

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

And Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 264ms

After Hooks.deleteTransportAfterTest() 728ms

After Hooks.rollbackWarehousesAccess() 725ms

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

And Prepare login page 444ms

And Click remind password button 267ms

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

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

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

And Extract password from mailgun mail 4s 408ms

And Reset password from link 1s 597ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 952ms

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

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

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

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

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

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

Then Save user details 1s 017ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 676ms

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

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

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

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

And Expand "other" notification section 2s 503ms

And Select all notifications in "other" section 268ms

Then Save user details 1s 506ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 906ms

After Hooks.rollbackAddedAuthorities() 159ms

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

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

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

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

And Go to "USERS_TAB" 2s 881ms

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

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

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

Then Save user details 1s 065ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 632ms

After Hooks.rollbackAddedAuthorities() 245ms

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

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

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

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

And Go to "USERS_TAB" 1s 570ms

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

And Expand "GLUE_FACTORY" notification section 538ms

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

Then Save user details 1s 828ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 123ms

After Hooks.rollbackAddedAuthorities() 235ms

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

Tag Report