Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.130	24 sie 2021, 05:52

	Steps	Scenarios	Features
@cleanUserDetailsAfterTest	432	1	5	0	0	438	44	1	45	55m 41s 702ms	Failed

View Feature Invitation

@deleteInvitationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if rejected invitation is visible in rejected tab

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

Then Go to "INVITATIONS_TAB" 721ms

And Go to invitation details 146ms

Then Reject invitation by button as user 321ms

When If user is login then logout 670ms

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

And Go to "INVITATIONS_TAB" 559ms

And Go to "REJECTED_TAB" invitation status tab 345ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 256ms

After Hooks.cleanUserDetailsAfterTest() 1s 287ms

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

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

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

And Go to "INVITATIONS_TAB" 457ms

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

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 095ms

Hooks

After Hooks.deleteInvitationAfterTest() 221ms

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 "adama-admin" and set token of apiUsername "super-admin-adama" 2s 497ms

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

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

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

And Show all transport types 1s 170ms

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

And Set advice window in schedule 3s 328ms

And Fill advice form 17s 112ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 261ms

After Hooks.deleteTransportAfterTest() 752ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

And Show all transport types 1s 161ms

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

And Set advice window in schedule 3s 421ms

And Fill advice form 12s 910ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 086ms

After Hooks.deleteTransportAfterTest() 763ms

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

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

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

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

And Show all transport types 1s 165ms

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

And Set advice window in schedule 3s 302ms

And Fill advice form 18s 822ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 462ms

After Hooks.deleteTransportAfterTest() 696ms

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

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

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

And Show all transport types 1s 140ms

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

And Go to "TRANSPORT_TABLE" 420ms

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

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

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

And Fill transport form 5s 175ms

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

And Expand advice panel 265ms

And Edit advice in transport details 17s 600ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 307ms

After Hooks.deleteTransportAfterTest() 757ms

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

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

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

And Show all transport types 1s 162ms

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

And Go to "TRANSPORT_TABLE" 405ms

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

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

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

And Fill transport form 1m 8s 819ms

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

And Expand advice panel 254ms

And Edit advice in transport details 8s 165ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 136ms

After Hooks.deleteTransportAfterTest() 906ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 5s 949ms

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

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

And Show all transport types 1s 165ms

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

And Go to "TRANSPORT_TABLE" 378ms

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

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

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

And Fill transport form 28s 556ms

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

And Expand advice panel 285ms

And Edit advice in transport details 23s 463ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 636ms

After Hooks.deleteTransportAfterTest() 796ms

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

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

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

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

Then Check if user got a mail 000ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 955ms

After Hooks.deleteTransportAfterTest() 847ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 610ms

After Hooks.deleteTransportAfterTest() 845ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 438ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 003ms

After Hooks.deleteTransportAfterTest() 779ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 069ms

After Hooks.deleteTransportAfterTest() 584ms

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

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

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

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

And Wait till auction end 1m 57s 017ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 459ms

After Hooks.deleteTransportAfterTest() 629ms

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

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

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

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

And Wait till auction end 1m 57s 016ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 395ms

After Hooks.deleteTransportAfterTest() 603ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 172ms

After Hooks.deleteTransportAfterTest() 627ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after winning an auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 334ms

After Hooks.deleteTransportAfterTest() 585ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 174ms

After Hooks.deleteTransportAfterTest() 602ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 172ms

After Hooks.deleteTransportAfterTest() 653ms

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

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

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

And Go to "TRANSPORT_TABLE" 411ms

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

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

And Fill transport form 43s 081ms

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

And Fill discrepancy report section 52s 492ms

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

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

And Generate discrepancy report 21s 612ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 554ms

After Hooks.deleteTransportAfterTest() 909ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 512ms

After Hooks.deleteModeOfTransportationAfterTest() 344ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 453ms

After Hooks.deleteModeOfTransportationAfterTest() 310ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 432ms

And Select warehouse "Serownia" 1s 700ms

And Set week view 1s 281ms

And Show yesterday 1s 168ms

And Move window into the past 435ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 427ms

After Hooks.deleteTransportAfterTest() 766ms

After Hooks.rollbackAddedAuthorities() 177ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 189ms

After Hooks.deleteTransportAfterTest() 579ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 172ms

After Hooks.deleteTransportAfterTest() 572ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 071ms

After Hooks.deleteTransportAfterTest() 795ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 049ms

After Hooks.deleteTransportAfterTest() 614ms

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

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

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

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

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

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

Then If user is login then logout 286ms

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

And Go to auction details 2s 271ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 912ms

After Hooks.deleteTransportAfterTest() 826ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 776ms

After Hooks.deleteTransportAfterTest() 654ms

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 249ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 395ms

And Fill advice form 20s 533ms

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

And Go to "TRANSPORT_TABLE" 476ms

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

Then Check are advice values equals 4s 935ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 318ms

After Hooks.deleteTransportAfterTest() 800ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

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

And Set advice window in schedule 3s 362ms

And Fill advice form 20s 610ms

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

And Go to "TRANSPORT_TABLE" 431ms

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

Then Check are advice values equals 4s 994ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 103ms

After Hooks.deleteTransportAfterTest() 781ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 331ms

And Fill advice form 20s 312ms

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

And Go to "TRANSPORT_TABLE" 519ms

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

Then Check are advice values equals 4s 919ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 263ms

After Hooks.deleteTransportAfterTest() 808ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 365ms

And Fill advice form 20s 616ms

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

And Go to "TRANSPORT_TABLE" 483ms

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

Then Check are advice values equals 4s 962ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 781ms

After Hooks.deleteTransportAfterTest() 808ms

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-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 7s 569ms

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

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

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

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

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

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

And Set advice window in schedule 30s 147ms

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.Y8LWut}, 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: 70d7a785ff1f116280ffd51b62a002a5
*** Element info: {Using=xpath, value=//button[@data-button-name='SHIFT_RIGHT_DAY']}
	at sun.reflect.GeneratedConstructorAccessor215.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:356)
	at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:458)
	at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
	at Pages.BasePage.getWebElementByXpath(BasePage.java: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.cleanUserDetailsAfterTest() 1s 761ms

After Hooks.deleteTransportAfterTest() 546ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

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

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

And Set advice window in schedule 3s 349ms

And Fill advice form 20s 348ms

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

And Go to "TRANSPORT_TABLE" 475ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 175ms

After Hooks.deleteTransportAfterTest() 798ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

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

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

And Set advice window in schedule 3s 404ms

And Fill advice form 20s 331ms

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

And Go to "TRANSPORT_TABLE" 446ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 274ms

After Hooks.deleteTransportAfterTest() 814ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

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

And Set advice window in schedule 3s 354ms

And Fill advice form 20s 462ms

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

And Go to "TRANSPORT_TABLE" 488ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 194ms

After Hooks.deleteTransportAfterTest() 802ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

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

And Set advice window in schedule 3s 372ms

And Fill advice form 20s 497ms

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

And Go to "TRANSPORT_TABLE" 480ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 020ms

After Hooks.deleteTransportAfterTest() 822ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 380ms

And Fill advice form 20s 517ms

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

And Go to "TRANSPORT_TABLE" 412ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 938ms

After Hooks.deleteTransportAfterTest() 944ms

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

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

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

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

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

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

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

When Reject status: Book of disinfection 227ms

And Check if reject date is visible 904ms

Then If user is login then logout 291ms

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

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

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

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

And Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 231ms

After Hooks.deleteTransportAfterTest() 720ms

After Hooks.rollbackWarehousesAccess() 773ms

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

And Prepare login page 458ms

And Click remind password button 287ms

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

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

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

And Extract password from mailgun mail 4s 008ms

And Reset password from link 1s 572ms

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

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

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

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

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

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

Then Save user details 1s 062ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 656ms

After Hooks.rollbackAddedAuthorities() 259ms

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

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

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

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

And Expand "other" notification section 2s 399ms

And Select all notifications in "other" section 278ms

Then Save user details 1s 510ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 086ms

After Hooks.rollbackAddedAuthorities() 176ms

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

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

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

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

And Go to "USERS_TAB" 1s 591ms

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

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

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

Then Save user details 948ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 655ms

After Hooks.rollbackAddedAuthorities() 243ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

And Go to "USERS_TAB" 1s 574ms

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

And Expand "GLUE_FACTORY" notification section 556ms

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

Then Save user details 1s 847ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 048ms

After Hooks.rollbackAddedAuthorities() 238ms

	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 41s 702ms	Failed

Tag Report