Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.118	14 sie 2021, 06:07

	Steps	Scenarios	Features
@cleanUserDetailsAfterTest	426	3	9	0	0	438	42	3	45	56m 45s 732ms	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" 089ms

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

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

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

Then Go to "INVITATIONS_TAB" 685ms

And Go to invitation details 143ms

Then Reject invitation by button as user 313ms

When If user is login then logout 282ms

Then Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 5s 118ms

And Go to "INVITATIONS_TAB" 493ms

And Go to "REJECTED_TAB" invitation status tab 343ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 161ms

After Hooks.cleanUserDetailsAfterTest() 1s 240ms

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

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

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

And Go to "INVITATIONS_TAB" 442ms

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

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 119ms

Hooks

After Hooks.deleteInvitationAfterTest() 186ms

After Hooks.cleanUserDetailsAfterTest() 1s 303ms

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

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

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

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

And Show all transport types 1s 173ms

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

And Set advice window in schedule 3s 413ms

And Fill advice form 17s 137ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 802ms

After Hooks.cleanUserDetailsAfterTest() 1s 253ms

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

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

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

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

And Show all transport types 1s 210ms

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

And Set advice window in schedule 3s 550ms

And Fill advice form 12s 930ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 773ms

After Hooks.cleanUserDetailsAfterTest() 1s 057ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 727ms

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

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

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

And Show all transport types 1s 160ms

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

And Set advice window in schedule 3s 291ms

And Fill advice form 18s 737ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 747ms

After Hooks.cleanUserDetailsAfterTest() 1s 522ms

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

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

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

And Show all transport types 1s 164ms

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

And Go to "TRANSPORT_TABLE" 460ms

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

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

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

And Fill transport form 5s 153ms

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

And Expand advice panel 275ms

And Edit advice in transport details 17s 473ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 773ms

After Hooks.cleanUserDetailsAfterTest() 1s 387ms

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

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

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

And Show all transport types 1s 162ms

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

And Go to "TRANSPORT_TABLE" 443ms

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

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

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

And Fill transport form 1m 8s 779ms

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

And Expand advice panel 258ms

And Edit advice in transport details 8s 164ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 952ms

After Hooks.cleanUserDetailsAfterTest() 1s 078ms

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

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

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

And Show all transport types 1s 159ms

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

And Go to "TRANSPORT_TABLE" 421ms

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

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

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

And Fill transport form 28s 789ms

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

And Expand advice panel 256ms

And Edit advice in transport details 23s 746ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 790ms

After Hooks.cleanUserDetailsAfterTest() 1s 645ms

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

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

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

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

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

Then Check if user got a mail 000ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 779ms

After Hooks.cleanUserDetailsAfterTest() 995ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 730ms

After Hooks.cleanUserDetailsAfterTest() 1s 657ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 401ms

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

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

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

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

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.deleteTransportAfterTest() 737ms

After Hooks.cleanUserDetailsAfterTest() 2s 015ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing auction

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

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 "Nie otrzymano zlecenia" 10s 570ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 616ms

After Hooks.cleanUserDetailsAfterTest() 2s 084ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after bid has been added to auction

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "swisskrono-producer" and set token of apiUsername "super-admin-skz" 12s 445ms

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

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

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

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

And Wait till auction end 1m 56s 019ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 695ms

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

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

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

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

And Wait till auction end 1m 57s 016ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 649ms

After Hooks.cleanUserDetailsAfterTest() 1s 254ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 578ms

After Hooks.cleanUserDetailsAfterTest() 1s 977ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 572ms

After Hooks.cleanUserDetailsAfterTest() 2s 220ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 587ms

After Hooks.cleanUserDetailsAfterTest() 2s 125ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 672ms

After Hooks.cleanUserDetailsAfterTest() 2s 202ms

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

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

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

And Go to "TRANSPORT_TABLE" 409ms

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

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

And Fill transport form 43s 109ms

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

And Fill discrepancy report section 52s 432ms

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

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

And Generate discrepancy report 21s 680ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 887ms

After Hooks.cleanUserDetailsAfterTest() 3s 485ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 554ms

After Hooks.deleteModeOfTransportationAfterTest() 381ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 473ms

After Hooks.deleteModeOfTransportationAfterTest() 305ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 381ms

And Select warehouse "Serownia" 1s 729ms

And Set week view 1s 251ms

And Show yesterday 1s 171ms

And Move window into the past 430ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 816ms

After Hooks.cleanUserDetailsAfterTest() 2s 685ms

After Hooks.rollbackAddedAuthorities() 212ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 604ms

After Hooks.cleanUserDetailsAfterTest() 2s 140ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 608ms

After Hooks.cleanUserDetailsAfterTest() 2s 337ms

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

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

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

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

Error message

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 552ms

After Hooks.cleanUserDetailsAfterTest() 1s 994ms

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

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

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

Error message

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 636ms

After Hooks.cleanUserDetailsAfterTest() 1s 990ms

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

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

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

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

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

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

Then If user is login then logout 266ms

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

And Go to auction details 2s 285ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 927ms

After Hooks.cleanUserDetailsAfterTest() 3s 010ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 682ms

After Hooks.cleanUserDetailsAfterTest() 2s 724ms

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 295ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 450ms

And Fill advice form 20s 383ms

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

And Go to "TRANSPORT_TABLE" 478ms

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

Then Check are advice values equals 5s 022ms

Hooks

After Hooks.deleteTransportAfterTest() 810ms

After Hooks.cleanUserDetailsAfterTest() 2s 260ms

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

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

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

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

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

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

And Set advice window in schedule 3s 354ms

And Fill advice form 20s 377ms

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

And Go to "TRANSPORT_TABLE" 469ms

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

Then Check are advice values equals 5s 047ms

Hooks

After Hooks.deleteTransportAfterTest() 804ms

After Hooks.cleanUserDetailsAfterTest() 2s 164ms

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

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

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

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

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

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

And Set advice window in schedule 3s 400ms

And Fill advice form 20s 579ms

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

And Go to "TRANSPORT_TABLE" 470ms

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

Then Check are advice values equals 4s 974ms

Hooks

After Hooks.deleteTransportAfterTest() 844ms

After Hooks.cleanUserDetailsAfterTest() 2s 370ms

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

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

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

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

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

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

And Set advice window in schedule 3s 378ms

And Fill advice form 20s 471ms

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

And Go to "TRANSPORT_TABLE" 487ms

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

Then Check are advice values equals 4s 903ms

Hooks

After Hooks.deleteTransportAfterTest() 840ms

After Hooks.cleanUserDetailsAfterTest() 2s 735ms

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

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

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

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

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

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

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

And Set advice window in schedule 30s 161ms

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

And Fill advice form 000ms

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

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "TRANSPORT_ORDER" 000ms

Then Check are advice values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 554ms

After Hooks.cleanUserDetailsAfterTest() 1s 764ms

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

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

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

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 "OWN_COLLECTION" created in transport table and set transport id 7s 257ms

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

And Set advice window in schedule 3s 398ms

And Fill advice form 20s 409ms

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

And Go to "TRANSPORT_TABLE" 476ms

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

Hooks

After Hooks.deleteTransportAfterTest() 809ms

After Hooks.cleanUserDetailsAfterTest() 2s 196ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 388ms

And Fill advice form 20s 564ms

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

And Go to "TRANSPORT_TABLE" 433ms

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

Hooks

After Hooks.deleteTransportAfterTest() 850ms

After Hooks.cleanUserDetailsAfterTest() 2s 261ms

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

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

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

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

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

And Set advice window in schedule 3s 392ms

And Fill advice form 20s 476ms

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

And Go to "TRANSPORT_TABLE" 476ms

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

Hooks

After Hooks.deleteTransportAfterTest() 863ms

After Hooks.cleanUserDetailsAfterTest() 2s 161ms

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

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

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

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

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

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

And Set advice window in schedule 3s 497ms

And Fill advice form 20s 495ms

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

And Go to "TRANSPORT_TABLE" 495ms

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

Hooks

After Hooks.deleteTransportAfterTest() 939ms

After Hooks.cleanUserDetailsAfterTest() 2s 911ms

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

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

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

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

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

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

And Set advice window in schedule 3s 433ms

And Fill advice form 20s 383ms

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

And Go to "TRANSPORT_TABLE" 420ms

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

Hooks

After Hooks.deleteTransportAfterTest() 865ms

After Hooks.cleanUserDetailsAfterTest() 1s 668ms

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

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

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

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

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

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

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

When Reject status: Book of disinfection 243ms

And Check if reject date is visible 1s 065ms

Then If user is login then logout 667ms

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

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

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

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

And Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 811ms

After Hooks.cleanUserDetailsAfterTest() 1s 240ms

After Hooks.rollbackWarehousesAccess() 791ms

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

And Prepare login page 382ms

And Click remind password button 282ms

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

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

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

And Extract password from mailgun mail 4s 212ms

And Reset password from link 1s 609ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 983ms

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

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

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

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

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

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

Then Save user details 1s 038ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 660ms

After Hooks.rollbackAddedAuthorities() 260ms

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

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

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

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

And Expand "other" notification section 2s 503ms

And Select all notifications in "other" section 313ms

Then Save user details 1s 529ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 901ms

After Hooks.rollbackAddedAuthorities() 141ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

Scenario Outline Permission - Edit user main data from other company [A-7887]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

And Go to "USERS_TAB" 2s 847ms

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

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

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

Then Save user details 1s 061ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 636ms

After Hooks.rollbackAddedAuthorities() 222ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

Scenario Outline Permission - Edit user notifications from other company [A-7887]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Set token of apiUsername "super-admin-skz" 237ms

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

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

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

And Go to "USERS_TAB" 1s 539ms

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

And Expand "GLUE_FACTORY" notification section 564ms

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

Then Save user details 1s 870ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 021ms

After Hooks.rollbackAddedAuthorities() 228ms

	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	56m 45s 732ms	Failed

Tag Report