Cucumber-JVM Reports - Feature: SK Api

Project	Number	Date
ApolloFullRunnerReport	after_release_3_6_0.328	02 mar 2021, 13:55

	Steps	Scenarios	Features
SK Api - Advice transport	118	0	0	0	0	118	10	0	10	13m 2s 981ms	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 218ms

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 54s 407ms

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

And Set advice window in schedule 2s 654ms

And Fill advice form 14s 776ms

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

And Go to "TRANSPORT_TABLE" 182ms

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

Then Check are advice values equals 2s 315ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

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

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

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

And Set advice window in schedule 2s 552ms

And Fill advice form 14s 770ms

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

And Go to "TRANSPORT_TABLE" 174ms

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

Then Check are advice values equals 2s 315ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

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

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

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 1s 119ms

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

And Set advice window in schedule 2s 567ms

And Fill advice form 14s 830ms

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

And Go to "TRANSPORT_TABLE" 222ms

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

Then Check are advice values equals 2s 334ms

Hooks

After Hooks.deleteTransportAfterTest() 131ms

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

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

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

And Set advice window in schedule 2s 509ms

And Fill advice form 14s 754ms

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

And Go to "TRANSPORT_TABLE" 167ms

Then Check advice data in SK API database "OWN_COLLECTION" 4s 199ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

@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_CONTAINER" "super-admin-skz" 002ms

And Add transport by SKApi in "MGW" 026ms

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

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

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

And Set advice window in schedule 2s 483ms

And Fill advice form 14s 522ms

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

And Go to "TRANSPORT_TABLE" 145ms

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

Hooks

After Hooks.deleteTransportAfterTest() 106ms

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

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

And Add transport by SKApi in "MGW" 010ms

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

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

And Set advice window in schedule 2s 464ms

And Fill advice form 14s 580ms

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

And Go to "TRANSPORT_TABLE" 192ms

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

Hooks

After Hooks.deleteTransportAfterTest() 101ms

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

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 9s 324ms

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

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

And Fill advice form 14s 618ms

And Click advice save button to check error message 084ms

Then Check if possible advice alert is displayed 022ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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

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

And Add transport by SKApi in "MGW" 034ms

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

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

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

And Go to "TRANSPORT_TABLE" 169ms

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

And Expand advice panel 112ms

And Edit advice in transport details 14s 084ms

And Fill arrival date field 2s 360ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 166ms

@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_CONTAINER" "super-admin-skz" 003ms

And Add transport by SKApi in "MGW" 004ms

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

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

And Go to "TRANSPORT_TABLE" 159ms

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

And Expand advice panel 099ms

And Edit advice in transport details 14s 049ms

And Fill arrival date field 2s 293ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 127ms

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

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 33s 341ms

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

And Go to "TRANSPORT_TABLE" 231ms

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

And Expand advice panel 116ms

And Edit advice in transport details 14s 013ms

And Fill arrival date field 2s 291ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 094ms

	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 2s 981ms	Passed

Feature Report