Cucumber-JVM Reports - Feature: SK Api

Project	Number	Date
ApolloFullRunnerReport	after_release_3_6_0.318	24 lut 2021, 23:40

	Steps	Scenarios	Features
SK Api - Advice transport	118	0	0	0	0	118	10	0	10	14m 19s 188ms	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 165ms

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

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

And Set advice window in schedule 2s 701ms

And Fill advice form 14s 860ms

And Click advice save button and wait for advice form to disappear 31s 300ms

And Go to "TRANSPORT_TABLE" 183ms

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

Then Check are advice values equals 2s 348ms

Hooks

After Hooks.deleteTransportAfterTest() 135ms

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

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 1m 483ms

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

And Set advice window in schedule 2s 558ms

And Fill advice form 14s 699ms

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

And Go to "TRANSPORT_TABLE" 196ms

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

Then Check are advice values equals 2s 327ms

Hooks

After Hooks.deleteTransportAfterTest() 131ms

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

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

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

And Set advice window in schedule 2s 537ms

And Fill advice form 14s 759ms

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

And Go to "TRANSPORT_TABLE" 195ms

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

Then Check are advice values equals 2s 325ms

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

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

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

And Set advice window in schedule 2s 511ms

And Fill advice form 14s 731ms

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

And Go to "TRANSPORT_TABLE" 171ms

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

Hooks

After Hooks.deleteTransportAfterTest() 143ms

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

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

And Add transport by SKApi in "MGW" 004ms

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

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

And Set advice window in schedule 2s 500ms

And Fill advice form 14s 740ms

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

And Go to "TRANSPORT_TABLE" 168ms

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

Hooks

After Hooks.deleteTransportAfterTest() 157ms

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

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 6s 235ms

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

And Set advice window in schedule 2s 519ms

And Fill advice form 14s 734ms

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

And Go to "TRANSPORT_TABLE" 232ms

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

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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

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

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

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

And Fill advice form 14s 910ms

And Click advice save button to check error message 099ms

Then Check if possible advice alert is displayed 021ms

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

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 "EDIT_ADVICE" "super-admin-skz" 001ms

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

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

And Go to "TRANSPORT_TABLE" 194ms

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

And Expand advice panel 108ms

And Edit advice in transport details 14s 114ms

And Fill arrival date field 2s 295ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 125ms

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

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

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

And Go to "TRANSPORT_TABLE" 198ms

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

And Expand advice panel 115ms

And Edit advice in transport details 14s 111ms

And Fill arrival date field 2s 312ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 121ms

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

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

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

And Go to "TRANSPORT_TABLE" 206ms

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

And Expand advice panel 132ms

And Edit advice in transport details 14s 145ms

And Fill arrival date field 2s 302ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 150ms

	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	14m 19s 188ms	Passed

Feature Report