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.
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
1s 294ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
005ms
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
54s 967ms
When
Click button advice in transport table "CONTAINER"
134ms
And
Set advice window in schedule
2s 818ms
And
Fill advice form
14s 838ms
And
Click advice save button and wait for advice form to disappear
31s 244ms
And
Go to "TRANSPORT_TABLE"
190ms
And
Go to transport details "CONTAINER"
4s 528ms
Then
Check are advice values equals
2s 336ms
After
Hooks.deleteTransportAfterTest()
112ms
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.
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
1s 179ms
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 466ms
When
Click button advice in transport table "OWN_COLLECTION"
139ms
And
Set advice window in schedule
2s 527ms
And
Fill advice form
14s 780ms
And
Click advice save button and wait for advice form to disappear
30s 741ms
And
Go to "TRANSPORT_TABLE"
188ms
And
Go to transport details "OWN_COLLECTION"
4s 478ms
Then
Check are advice values equals
2s 329ms
After
Hooks.deleteTransportAfterTest()
144ms
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.
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
1s 319ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id
3s 188ms
When
Click button advice in transport table "TRANSPORT_ORDER"
109ms
And
Set advice window in schedule
2s 620ms
And
Fill advice form
14s 722ms
And
Click advice save button and wait for advice form to disappear
30s 686ms
And
Go to "TRANSPORT_TABLE"
213ms
And
Go to transport details "TRANSPORT_ORDER"
4s 497ms
Then
Check are advice values equals
2s 338ms
After
Hooks.deleteTransportAfterTest()
136ms
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.
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
1s 237ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
3s 426ms
When
Click button advice in transport table "OWN_COLLECTION"
136ms
And
Set advice window in schedule
2s 533ms
And
Fill advice form
14s 775ms
And
Click advice save button and wait for advice form to disappear
30s 784ms
And
Go to "TRANSPORT_TABLE"
187ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 163ms
After
Hooks.deleteTransportAfterTest()
115ms
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.
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"
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 333ms
When
Click button advice in transport table "CONTAINER"
130ms
And
Set advice window in schedule
2s 521ms
And
Fill advice form
14s 866ms
And
Click advice save button and wait for advice form to disappear
30s 758ms
And
Go to "TRANSPORT_TABLE"
174ms
Then
Check advice data in SK API database "CONTAINER"
4s 111ms
After
Hooks.deleteTransportAfterTest()
146ms
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.
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
1s 286ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
008ms
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 246ms
When
Click button advice in transport table "TRANSPORT_ORDER"
132ms
And
Set advice window in schedule
2s 562ms
And
Fill advice form
14s 802ms
And
Click advice save button and wait for advice form to disappear
30s 754ms
And
Go to "TRANSPORT_TABLE"
209ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 047ms
After
Hooks.deleteTransportAfterTest()
127ms
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
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
1s 225ms
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
9s 346ms
When
Click button advice in transport table "CONTAINER"
130ms
And
Set advice window in schedule in the past
2s 623ms
And
Fill advice form
14s 810ms
And
Click advice save button to check error message
107ms
Then
Check if possible advice alert is displayed
023ms
After
Hooks.deleteTransportAfterTest()
120ms
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.
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
1s 228ms
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"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
39s 473ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 382ms
And
Go to "TRANSPORT_TABLE"
197ms
When
Go to transport details "OWN_COLLECTION"
4s 496ms
And
Expand advice panel
109ms
And
Edit advice in transport details
14s 121ms
And
Fill arrival date field
2s 281ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 651ms
Then
Check advice data in database after edition "OWN_COLLECTION"
039ms
After
Hooks.deleteTransportAfterTest()
149ms
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.
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
1s 260ms
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"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
33s 400ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 201ms
And
Go to "TRANSPORT_TABLE"
163ms
When
Go to transport details "CONTAINER"
4s 509ms
And
Expand advice panel
106ms
And
Edit advice in transport details
14s 059ms
And
Fill arrival date field
2s 297ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 617ms
Then
Check advice data in database after edition "CONTAINER"
036ms
After
Hooks.deleteTransportAfterTest()
120ms
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.
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
1s 255ms
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 323ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 324ms
And
Go to "TRANSPORT_TABLE"
213ms
When
Go to transport details "TRANSPORT_ORDER"
4s 484ms
And
Expand advice panel
125ms
And
Edit advice in transport details
14s 091ms
And
Fill arrival date field
2s 284ms
And
Click "save-transport-and-close" save button and wait for form to disappear
669ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
039ms
After
Hooks.deleteTransportAfterTest()
126ms