Cucumber-JVM Reports - Feature: SK Api

Project	Number	Date
ApolloFullRunnerReport	after_release_3_6_0.326	28 lut 2021, 13:03

	Steps	Scenarios	Features
SK Api - Advice transport	118	0	0	0	0	118	10	0	10	13m 20s 124ms	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 286ms

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

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

And Set advice window in schedule 2s 610ms

And Fill advice form 14s 843ms

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

And Go to "TRANSPORT_TABLE" 169ms

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

Then Check are advice values equals 2s 317ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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

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

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

And Set advice window in schedule 2s 536ms

And Fill advice form 14s 705ms

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

And Go to "TRANSPORT_TABLE" 163ms

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

Then Check are advice values equals 2s 319ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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

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

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

And Set advice window in schedule 2s 542ms

And Fill advice form 14s 695ms

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

And Go to "TRANSPORT_TABLE" 224ms

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

Then Check are advice values equals 2s 316ms

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

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

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

And Set advice window in schedule 2s 495ms

And Fill advice form 14s 774ms

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

And Go to "TRANSPORT_TABLE" 192ms

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

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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

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

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

And Set advice window in schedule 2s 503ms

And Fill advice form 14s 847ms

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

And Go to "TRANSPORT_TABLE" 184ms

Then Check advice data in SK API database "CONTAINER" 19s 157ms

Hooks

After Hooks.deleteTransportAfterTest() 149ms

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

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

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

And Set advice window in schedule 2s 487ms

And Fill advice form 14s 811ms

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

And Go to "TRANSPORT_TABLE" 192ms

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

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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

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

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

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

And Fill advice form 14s 809ms

And Click advice save button to check error message 097ms

Then Check if possible advice alert is displayed 019ms

Hooks

After Hooks.deleteTransportAfterTest() 175ms

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

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

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

And Go to "TRANSPORT_TABLE" 170ms

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

And Expand advice panel 112ms

And Edit advice in transport details 14s 088ms

And Fill arrival date field 2s 306ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 123ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 168ms

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

And Expand advice panel 115ms

And Edit advice in transport details 14s 062ms

And Fill arrival date field 2s 285ms

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

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 213ms

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

And Expand advice panel 127ms

And Edit advice in transport details 14s 045ms

And Fill arrival date field 2s 305ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 111ms

	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 20s 124ms	Passed

Feature Report