Cucumber-JVM Reports - Feature: SK Api

Project	Number	Date
ApolloFullRunnerReport	after_release_3_7_0.348	19 mar 2021, 18:02

	Steps	Scenarios	Features
SK Api - Advice transport	118	0	0	0	0	118	10	0	10	13m 19s 007ms	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 287ms

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

And Add transport by SKApi in "MGW" 002ms

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

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

And Set advice window in schedule 2s 656ms

And Fill advice form 14s 776ms

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

And Go to "TRANSPORT_TABLE" 203ms

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

Then Check are advice values equals 2s 338ms

Hooks

After Hooks.deleteTransportAfterTest() 142ms

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

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

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

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

And Set advice window in schedule 2s 583ms

And Fill advice form 14s 820ms

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

And Go to "TRANSPORT_TABLE" 207ms

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

Then Check are advice values equals 2s 347ms

Hooks

After Hooks.deleteTransportAfterTest() 132ms

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

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

And Add transport by SKApi in "MGW" 005ms

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 3s 209ms

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

And Set advice window in schedule 2s 542ms

And Fill advice form 14s 765ms

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

And Go to "TRANSPORT_TABLE" 234ms

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

Then Check are advice values equals 2s 282ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

@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 279ms

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

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

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

And Set advice window in schedule 2s 545ms

And Fill advice form 14s 732ms

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

And Go to "TRANSPORT_TABLE" 214ms

Then Check advice data in SK API database "OWN_COLLECTION" 2s 166ms

Hooks

After Hooks.deleteTransportAfterTest() 132ms

@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 277ms

And Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id 6s 326ms

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

And Set advice window in schedule 2s 531ms

And Fill advice form 14s 801ms

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

And Go to "TRANSPORT_TABLE" 192ms

Then Check advice data in SK API database "CONTAINER" 3s 112ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

@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 193ms

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

And Add transport by SKApi in "MGW" 002ms

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

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

And Set advice window in schedule 2s 571ms

And Fill advice form 14s 537ms

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

And Go to "TRANSPORT_TABLE" 225ms

Then Check advice data in SK API database "TRANSPORT_ORDER" 4s 039ms

Hooks

After Hooks.deleteTransportAfterTest() 158ms

@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 157ms

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

And Add transport by SKApi in "MGW" 002ms

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

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

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

And Fill advice form 14s 507ms

And Click advice save button to check error message 078ms

Then Check if possible advice alert is displayed 024ms

Hooks

After Hooks.deleteTransportAfterTest() 078ms

@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 195ms

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

And Add transport by SKApi in "MGW" 001ms

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 42s 440ms

And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 47s 868ms

And Go to "TRANSPORT_TABLE" 184ms

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

And Expand advice panel 093ms

And Edit advice in transport details 13s 890ms

And Fill arrival date field 2s 256ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 130ms

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

And Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id 33s 393ms

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

And Go to "TRANSPORT_TABLE" 181ms

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

And Expand advice panel 107ms

And Edit advice in transport details 13s 943ms

And Fill arrival date field 2s 249ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 126ms

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

And Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id 36s 284ms

And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 47s 921ms

And Go to "TRANSPORT_TABLE" 199ms

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

And Expand advice panel 104ms

And Edit advice in transport details 13s 917ms

And Fill arrival date field 2s 253ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 118ms

	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 19s 007ms	Passed

Feature Report