Cucumber-JVM Reports - Feature: SK Api

Project	Number	Date
ApolloFullRunnerReport	after_release_3_6_0.325	27 lut 2021, 11:20

	Steps	Scenarios	Features
SK Api - Advice transport	118	0	0	0	0	118	10	0	10	13m 4s 505ms	Passed

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.

Steps

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

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

And Add transport by SKApi in "MGW" 003ms

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

And Check is transport "CONTAINER" created in transport table and set transport id 54s 419ms

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

And Set advice window in schedule 2s 610ms

And Fill advice form 14s 738ms

And Click advice save button and wait for advice form to disappear 30s 730ms

And Go to "TRANSPORT_TABLE" 187ms

And Go to transport details "CONTAINER" 4s 498ms

Then Check are advice values equals 2s 343ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

@deleteTransportAfterTest

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.

Steps

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

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

And Add transport by SKApi in "MGW" 002ms

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

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 363ms

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

And Set advice window in schedule 2s 525ms

And Fill advice form 14s 803ms

And Click advice save button and wait for advice form to disappear 30s 763ms

And Go to "TRANSPORT_TABLE" 188ms

And Go to transport details "OWN_COLLECTION" 4s 462ms

Then Check are advice values equals 2s 327ms

Hooks

After Hooks.deleteTransportAfterTest() 133ms

@deleteTransportAfterTest

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.

Steps

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

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

And Add transport by SKApi in "MGW" 003ms

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

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

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

And Set advice window in schedule 2s 548ms

And Fill advice form 14s 814ms

And Click advice save button and wait for advice form to disappear 30s 717ms

And Go to "TRANSPORT_TABLE" 200ms

And Go to transport details "TRANSPORT_ORDER" 4s 454ms

Then Check are advice values equals 2s 343ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

@deleteTransportAfterTest

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.

Steps

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

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

And Add transport by SKApi in "MGW" 003ms

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

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 405ms

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

And Set advice window in schedule 2s 485ms

And Fill advice form 14s 719ms

And Click advice save button and wait for advice form to disappear 30s 768ms

And Go to "TRANSPORT_TABLE" 192ms

Then Check advice data in SK API database "OWN_COLLECTION" 3s 170ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

@deleteTransportAfterTest

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.

Steps

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

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

And Add transport by SKApi in "MGW" 003ms

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

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

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

And Set advice window in schedule 2s 517ms

And Fill advice form 14s 773ms

And Click advice save button and wait for advice form to disappear 30s 746ms

And Go to "TRANSPORT_TABLE" 175ms

Then Check advice data in SK API database "CONTAINER" 4s 103ms

Hooks

After Hooks.deleteTransportAfterTest() 137ms

@deleteTransportAfterTest

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.

Steps

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

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

And Add transport by SKApi in "MGW" 003ms

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

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

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

And Set advice window in schedule 2s 530ms

And Fill advice form 14s 770ms

And Click advice save button and wait for advice form to disappear 30s 772ms

And Go to "TRANSPORT_TABLE" 203ms

Then Check advice data in SK API database "TRANSPORT_ORDER" 3s 042ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

@deleteTransportAfterTest

Scenario Outline Check if not possible to advice transport in the past when advice is created from transports table and transport is created by sk API

Steps

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

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

And Add transport by SKApi in "MGW" 003ms

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

And Check is transport "CONTAINER" created in transport table and set transport id 9s 337ms

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

And Set advice window in schedule in the past 2s 545ms

And Fill advice form 14s 787ms

And Click advice save button to check error message 095ms

Then Check if possible advice alert is displayed 025ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

@deleteTransportAfterTest

Scenario Outline Check if advice data saved in SK API database after edition

The scenario checks if you can correctly edit an advice. After that the correctness of the data that has been sent to the SK API microservice database is also verified.

Steps

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

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

And Add transport by SKApi in "MGW" 002ms

And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 001ms

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 39s 490ms

And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 48s 242ms

And Go to "TRANSPORT_TABLE" 184ms

When Go to transport details "OWN_COLLECTION" 4s 503ms

And Expand advice panel 110ms

And Edit advice in transport details 14s 127ms

And Fill arrival date field 2s 315ms

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

Then Check advice data in database after edition "OWN_COLLECTION" 042ms

Hooks

After Hooks.deleteTransportAfterTest() 131ms

@deleteTransportAfterTest

Scenario Outline Check if advice data saved in SK API database after edition

The scenario checks if you can correctly edit an advice. After that the correctness of the data that has been sent to the SK API microservice database is also verified.

Steps

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

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

And Add transport by SKApi in "MGW" 002ms

And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 001ms

And Check is transport "CONTAINER" created in transport table and set transport id 33s 935ms

And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 48s 308ms

And Go to "TRANSPORT_TABLE" 173ms

When Go to transport details "CONTAINER" 4s 468ms

And Expand advice panel 111ms

And Edit advice in transport details 14s 106ms

And Fill arrival date field 2s 283ms

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

Then Check advice data in database after edition "CONTAINER" 033ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

@deleteTransportAfterTest

Scenario Outline Check if advice data saved in SK API database after edition

The scenario checks if you can correctly edit an advice. After that the correctness of the data that has been sent to the SK API microservice database is also verified.

Steps

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

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

And Add transport by SKApi in "MGW" 003ms

And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 002ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 33s 329ms

And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 48s 252ms

And Go to "TRANSPORT_TABLE" 225ms

When Go to transport details "TRANSPORT_ORDER" 4s 476ms

And Expand advice panel 122ms

And Edit advice in transport details 14s 098ms

And Fill arrival date field 2s 284ms

And Click "save-transport-and-close" save button and wait for form to disappear 670ms

Then Check advice data in database after edition "TRANSPORT_ORDER" 021ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
SK Api - Advice transport	118	0	0	0	0	118	10	0	10	13m 4s 505ms	Passed

Feature Report