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 231ms
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"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
54s 391ms
When
Click button advice in transport table "CONTAINER"
097ms
And
Set advice window in schedule
2s 633ms
And
Fill advice form
14s 810ms
And
Click advice save button and wait for advice form to disappear
30s 700ms
And
Go to "TRANSPORT_TABLE"
189ms
And
Go to transport details "CONTAINER"
4s 543ms
Then
Check are advice values equals
2s 323ms
After
Hooks.deleteTransportAfterTest()
151ms
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 174ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
001ms
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 381ms
When
Click button advice in transport table "OWN_COLLECTION"
129ms
And
Set advice window in schedule
2s 538ms
And
Fill advice form
14s 800ms
And
Click advice save button and wait for advice form to disappear
30s 756ms
And
Go to "TRANSPORT_TABLE"
180ms
And
Go to transport details "OWN_COLLECTION"
4s 473ms
Then
Check are advice values equals
2s 345ms
After
Hooks.deleteTransportAfterTest()
154ms
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 220ms
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
3s 235ms
When
Click button advice in transport table "TRANSPORT_ORDER"
120ms
And
Set advice window in schedule
2s 506ms
And
Fill advice form
14s 842ms
And
Click advice save button and wait for advice form to disappear
30s 682ms
And
Go to "TRANSPORT_TABLE"
205ms
And
Go to transport details "TRANSPORT_ORDER"
4s 455ms
Then
Check are advice values equals
2s 333ms
After
Hooks.deleteTransportAfterTest()
117ms
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 279ms
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"
141ms
And
Set advice window in schedule
2s 495ms
And
Fill advice form
14s 771ms
And
Click advice save button and wait for advice form to disappear
30s 763ms
And
Go to "TRANSPORT_TABLE"
171ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 137ms
After
Hooks.deleteTransportAfterTest()
135ms
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 234ms
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 309ms
When
Click button advice in transport table "CONTAINER"
128ms
And
Set advice window in schedule
2s 515ms
And
Fill advice form
14s 800ms
And
Click advice save button and wait for advice form to disappear
30s 748ms
And
Go to "TRANSPORT_TABLE"
167ms
Then
Check advice data in SK API database "CONTAINER"
3s 103ms
After
Hooks.deleteTransportAfterTest()
107ms
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 269ms
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 829ms
When
Click button advice in transport table "TRANSPORT_ORDER"
124ms
And
Set advice window in schedule
2s 511ms
And
Fill advice form
14s 804ms
And
Click advice save button and wait for advice form to disappear
30s 779ms
And
Go to "TRANSPORT_TABLE"
216ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 039ms
After
Hooks.deleteTransportAfterTest()
109ms
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 323ms
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"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 313ms
When
Click button advice in transport table "CONTAINER"
119ms
And
Set advice window in schedule in the past
2s 533ms
And
Fill advice form
14s 790ms
And
Click advice save button to check error message
100ms
Then
Check if possible advice alert is displayed
029ms
After
Hooks.deleteTransportAfterTest()
098ms
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 223ms
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 "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
42s 451ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 296ms
And
Go to "TRANSPORT_TABLE"
180ms
When
Go to transport details "OWN_COLLECTION"
4s 476ms
And
Expand advice panel
115ms
And
Edit advice in transport details
14s 123ms
And
Fill arrival date field
2s 318ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 132ms
Then
Check advice data in database after edition "OWN_COLLECTION"
033ms
After
Hooks.deleteTransportAfterTest()
151ms
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 272ms
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 418ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 338ms
And
Go to "TRANSPORT_TABLE"
156ms
When
Go to transport details "CONTAINER"
4s 516ms
And
Expand advice panel
120ms
And
Edit advice in transport details
14s 138ms
And
Fill arrival date field
2s 295ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 120ms
Then
Check advice data in database after edition "CONTAINER"
036ms
After
Hooks.deleteTransportAfterTest()
176ms
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 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
30s 906ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 294ms
And
Go to "TRANSPORT_TABLE"
232ms
When
Go to transport details "TRANSPORT_ORDER"
4s 505ms
And
Expand advice panel
102ms
And
Edit advice in transport details
14s 120ms
And
Fill arrival date field
2s 287ms
And
Click "save-transport-and-close" save button and wait for form to disappear
677ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
027ms
After
Hooks.deleteTransportAfterTest()
108ms