Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.123	18 sie 2021, 06:09

	Steps	Scenarios	Features
@cleanUserDetailsAfterTest	432	1	5	0	0	438	44	1	45	55m 30s 308ms	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" 225ms

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

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

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

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

Then Go to "INVITATIONS_TAB" 662ms

And Go to invitation details 144ms

Then Reject invitation by button as user 320ms

When If user is login then logout 5s 844ms

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

And Go to "INVITATIONS_TAB" 439ms

And Go to "REJECTED_TAB" invitation status tab 218ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 157ms

After Hooks.cleanUserDetailsAfterTest() 1s 161ms

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

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

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

And Go to "INVITATIONS_TAB" 473ms

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

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 121ms

Hooks

After Hooks.deleteInvitationAfterTest() 190ms

After Hooks.cleanUserDetailsAfterTest() 1s 288ms

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

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

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

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

And Show all transport types 1s 132ms

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

And Set advice window in schedule 3s 449ms

And Fill advice form 17s 201ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 842ms

After Hooks.cleanUserDetailsAfterTest() 1s 359ms

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

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

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

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

And Show all transport types 1s 155ms

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

And Set advice window in schedule 3s 438ms

And Fill advice form 12s 956ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 764ms

After Hooks.cleanUserDetailsAfterTest() 1s 059ms

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

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

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

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

And Show all transport types 1s 168ms

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

And Set advice window in schedule 3s 289ms

And Fill advice form 18s 595ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 752ms

After Hooks.cleanUserDetailsAfterTest() 1s 552ms

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

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

And Show all transport types 1s 164ms

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

And Go to "TRANSPORT_TABLE" 452ms

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

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

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

And Fill transport form 5s 148ms

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

And Expand advice panel 258ms

And Edit advice in transport details 17s 487ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 765ms

After Hooks.cleanUserDetailsAfterTest() 1s 397ms

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

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

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

And Show all transport types 1s 156ms

And Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast" 49s 853ms

And Go to "TRANSPORT_TABLE" 461ms

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

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

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

And Fill transport form 1m 8s 823ms

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

And Expand advice panel 238ms

And Edit advice in transport details 8s 121ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 967ms

After Hooks.cleanUserDetailsAfterTest() 1s 105ms

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

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

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

And Show all transport types 1s 171ms

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

And Go to "TRANSPORT_TABLE" 469ms

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

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

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

And Fill transport form 28s 791ms

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

And Expand advice panel 266ms

And Edit advice in transport details 23s 730ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 797ms

After Hooks.cleanUserDetailsAfterTest() 1s 651ms

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

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

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

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

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

Then Check if user got a mail 000ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 795ms

After Hooks.cleanUserDetailsAfterTest() 940ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 778ms

After Hooks.cleanUserDetailsAfterTest() 1s 640ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 427ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating a new auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 691ms

After Hooks.cleanUserDetailsAfterTest() 2s 122ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 586ms

After Hooks.cleanUserDetailsAfterTest() 2s 167ms

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

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

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

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

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

And Wait till auction end 1m 57s 016ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 715ms

After Hooks.cleanUserDetailsAfterTest() 2s 328ms

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

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

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

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

And Wait till auction end 1m 57s 015ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 672ms

After Hooks.cleanUserDetailsAfterTest() 1s 349ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 598ms

After Hooks.cleanUserDetailsAfterTest() 2s 202ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 592ms

After Hooks.cleanUserDetailsAfterTest() 2s 308ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 591ms

After Hooks.cleanUserDetailsAfterTest() 2s 121ms

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

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

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" and finish of auction in "121" minutes 3s 104ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 691ms

After Hooks.cleanUserDetailsAfterTest() 2s 046ms

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

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

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

And Go to "TRANSPORT_TABLE" 418ms

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

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

And Fill transport form 43s 013ms

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

And Fill discrepancy report section 52s 368ms

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

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

And Generate discrepancy report 21s 562ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 947ms

After Hooks.cleanUserDetailsAfterTest() 3s 380ms

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

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 477ms

After Hooks.deleteModeOfTransportationAfterTest() 354ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 440ms

After Hooks.deleteModeOfTransportationAfterTest() 299ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 442ms

And Select warehouse "Serownia" 1s 652ms

And Set week view 1s 240ms

And Show yesterday 1s 149ms

And Move window into the past 436ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 815ms

After Hooks.cleanUserDetailsAfterTest() 2s 341ms

After Hooks.rollbackAddedAuthorities() 120ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 596ms

After Hooks.cleanUserDetailsAfterTest() 2s 154ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 582ms

After Hooks.cleanUserDetailsAfterTest() 2s 150ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to carrier after transport transfer

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 799ms

After Hooks.cleanUserDetailsAfterTest() 2s 001ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to carrier after transport transfer with no confirmation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 601ms

After Hooks.cleanUserDetailsAfterTest() 2s 039ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing inquiry

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

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

Then If user is login then logout 259ms

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

And Go to auction details 1s 908ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 891ms

After Hooks.cleanUserDetailsAfterTest() 2s 744ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 685ms

After Hooks.cleanUserDetailsAfterTest() 2s 750ms

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 262ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

And Set advice window in schedule 3s 346ms

And Fill advice form 20s 266ms

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

And Go to "TRANSPORT_TABLE" 481ms

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

Then Check are advice values equals 4s 936ms

Hooks

After Hooks.deleteTransportAfterTest() 798ms

After Hooks.cleanUserDetailsAfterTest() 2s 238ms

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

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

And Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id 7s 122ms

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

And Set advice window in schedule 3s 391ms

And Fill advice form 20s 353ms

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

And Go to "TRANSPORT_TABLE" 444ms

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

Then Check are advice values equals 4s 969ms

Hooks

After Hooks.deleteTransportAfterTest() 802ms

After Hooks.cleanUserDetailsAfterTest() 2s 059ms

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

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

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

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

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

And Set advice window in schedule 3s 360ms

And Fill advice form 20s 478ms

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

And Go to "TRANSPORT_TABLE" 484ms

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

Then Check are advice values equals 5s 152ms

Hooks

After Hooks.deleteTransportAfterTest() 832ms

After Hooks.cleanUserDetailsAfterTest() 2s 119ms

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

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

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

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 "TRANSPORT_ORDER" created in transport table and set transport id 4s 707ms

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

And Set advice window in schedule 3s 577ms

And Fill advice form 20s 247ms

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

And Go to "TRANSPORT_TABLE" 468ms

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

Then Check are advice values equals 4s 991ms

Hooks

After Hooks.deleteTransportAfterTest() 784ms

After Hooks.cleanUserDetailsAfterTest() 2s 704ms

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

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

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

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

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

And Set advice window in schedule 30s 193ms

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.Wp7ONc}, 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: e145d6961212f956fc0dcb269d0fc6f2
*** Element info: {Using=xpath, value=//button[@data-button-name='SHIFT_RIGHT_DAY']}
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:356)
	at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:458)
	at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
	at Pages.BasePage.getWebElementByXpath(BasePage.java:325)
	at CucumberTests.Transport.AdviceTransport.setAdviceWindowInSchedule(AdviceTransport.java:91)
	at ✽.Set advice window in schedule(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:13)

And Fill advice form 000ms

And Click advice save button and wait for advice form to disappear 000ms

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "TRANSPORT_ORDER" 000ms

Then Check are advice values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 567ms

After Hooks.cleanUserDetailsAfterTest() 1s 771ms

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

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

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

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

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 7s 142ms

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

And Set advice window in schedule 3s 401ms

And Fill advice form 20s 497ms

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

And Go to "TRANSPORT_TABLE" 450ms

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

Hooks

After Hooks.deleteTransportAfterTest() 805ms

After Hooks.cleanUserDetailsAfterTest() 2s 113ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 378ms

And Fill advice form 20s 452ms

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

And Go to "TRANSPORT_TABLE" 451ms

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

Hooks

After Hooks.deleteTransportAfterTest() 849ms

After Hooks.cleanUserDetailsAfterTest() 2s 341ms

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

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

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

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

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

And Set advice window in schedule 3s 347ms

And Fill advice form 20s 451ms

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

And Go to "TRANSPORT_TABLE" 424ms

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

Hooks

After Hooks.deleteTransportAfterTest() 830ms

After Hooks.cleanUserDetailsAfterTest() 2s 073ms

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

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

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

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

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

And Set advice window in schedule 3s 400ms

And Fill advice form 20s 508ms

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

And Go to "TRANSPORT_TABLE" 504ms

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

Hooks

After Hooks.deleteTransportAfterTest() 923ms

After Hooks.cleanUserDetailsAfterTest() 2s 933ms

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

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

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

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

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

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

And Set advice window in schedule 3s 357ms

And Fill advice form 20s 453ms

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

And Go to "TRANSPORT_TABLE" 446ms

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

Hooks

After Hooks.deleteTransportAfterTest() 853ms

After Hooks.cleanUserDetailsAfterTest() 1s 660ms

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

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

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

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

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

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

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

When Reject status: Book of disinfection 210ms

And Check if reject date is visible 1s 042ms

Then If user is login then logout 5s 655ms

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

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

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

And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nieaktualna księga mycia i dezynfekcji" 3m 19s 833ms

And Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 856ms

After Hooks.cleanUserDetailsAfterTest() 1s 209ms

After Hooks.rollbackWarehousesAccess() 802ms

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

And Prepare login page 443ms

And Click remind password button 276ms

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

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

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

And Extract password from mailgun mail 3s 903ms

And Reset password from link 1s 481ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 968ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7965

Scenario Outline Permission - Edit user main data [A-7965]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 230ms

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

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

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

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

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

Then Save user details 1s 034ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 670ms

After Hooks.rollbackAddedAuthorities() 263ms

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

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

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

And Expand "other" notification section 2s 564ms

And Select all notifications in "other" section 275ms

Then Save user details 1s 508ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 904ms

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

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

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

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

And Go to "USERS_TAB" 2s 978ms

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

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

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

Then Save user details 1s 049ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 640ms

After Hooks.rollbackAddedAuthorities() 228ms

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

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

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

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

And Go to "USERS_TAB" 1s 502ms

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

And Expand "GLUE_FACTORY" notification section 596ms

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

Then Save user details 1s 781ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 046ms

After Hooks.rollbackAddedAuthorities() 239ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@cleanUserDetailsAfterTest	432	1	5	0	0	438	44	1	45	55m 30s 308ms	Failed

Tag Report