Cucumber-JVM Reports - Feature: SK Api

Project	Number	Date
ApolloFullRunnerReport	f_after_release_3_4_0.306	10 lut 2021, 23:29

	Steps	Scenarios	Features
SK Api - Advice transport	118	0	0	0	0	118	10	0	10	13m 4s 304ms	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 195ms

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

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

And Set advice window in schedule 2s 660ms

And Fill advice form 14s 801ms

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

And Go to "TRANSPORT_TABLE" 171ms

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

Then Check are advice values equals 2s 330ms

Hooks

After Hooks.deleteTransportAfterTest() 144ms

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

And Add transport by SKApi in "MGW" 003ms

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

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

And Set advice window in schedule 2s 634ms

And Fill advice form 14s 781ms

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

And Go to "TRANSPORT_TABLE" 177ms

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

Then Check are advice values equals 2s 347ms

Hooks

After Hooks.deleteTransportAfterTest() 130ms

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

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

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

And Set advice window in schedule 2s 526ms

And Fill advice form 14s 764ms

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

And Go to "TRANSPORT_TABLE" 231ms

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

Then Check are advice values equals 2s 337ms

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

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

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

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

And Set advice window in schedule 2s 516ms

And Fill advice form 14s 741ms

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

And Go to "TRANSPORT_TABLE" 188ms

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

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

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

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

And Set advice window in schedule 2s 509ms

And Fill advice form 14s 752ms

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

And Go to "TRANSPORT_TABLE" 186ms

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

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

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

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

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

And Set advice window in schedule 2s 492ms

And Fill advice form 14s 781ms

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

And Go to "TRANSPORT_TABLE" 203ms

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

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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

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

And Add transport by SKApi in "MGW" 004ms

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

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

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

And Fill advice form 14s 812ms

And Click advice save button to check error message 098ms

Then Check if possible advice alert is displayed 025ms

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

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

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

And Go to "TRANSPORT_TABLE" 180ms

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

And Expand advice panel 117ms

And Edit advice in transport details 14s 082ms

And Fill arrival date field 2s 325ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 134ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 185ms

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

And Expand advice panel 120ms

And Edit advice in transport details 14s 140ms

And Fill arrival date field 2s 291ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 101ms

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

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

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

And Go to "TRANSPORT_TABLE" 200ms

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

And Expand advice panel 116ms

And Edit advice in transport details 14s 090ms

And Fill arrival date field 2s 292ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 124ms

	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 304ms	Passed

Feature Report