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 232ms
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 419ms
When
Click button advice in transport table "CONTAINER"
111ms
And
Set advice window in schedule
2s 693ms
And
Fill advice form
14s 789ms
And
Click advice save button and wait for advice form to disappear
30s 712ms
And
Go to "TRANSPORT_TABLE"
223ms
And
Go to transport details "CONTAINER"
4s 535ms
Then
Check are advice values equals
2s 323ms
After
Hooks.deleteTransportAfterTest()
129ms
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 233ms
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"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
1m 3s 541ms
When
Click button advice in transport table "OWN_COLLECTION"
115ms
And
Set advice window in schedule
2s 601ms
And
Fill advice form
14s 727ms
And
Click advice save button and wait for advice form to disappear
30s 745ms
And
Go to "TRANSPORT_TABLE"
198ms
And
Go to transport details "OWN_COLLECTION"
4s 484ms
Then
Check are advice values equals
2s 341ms
After
Hooks.deleteTransportAfterTest()
149ms
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 257ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id
1m 915ms
When
Click button advice in transport table "TRANSPORT_ORDER"
132ms
And
Set advice window in schedule
2s 567ms
And
Fill advice form
14s 668ms
And
Click advice save button and wait for advice form to disappear
30s 709ms
And
Go to "TRANSPORT_TABLE"
229ms
And
Go to transport details "TRANSPORT_ORDER"
4s 477ms
Then
Check are advice values equals
2s 361ms
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 255ms
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 414ms
When
Click button advice in transport table "OWN_COLLECTION"
116ms
And
Set advice window in schedule
2s 539ms
And
Fill advice form
14s 792ms
And
Click advice save button and wait for advice form to disappear
30s 717ms
And
Go to "TRANSPORT_TABLE"
217ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 186ms
After
Hooks.deleteTransportAfterTest()
125ms
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 232ms
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
9s 358ms
When
Click button advice in transport table "CONTAINER"
106ms
And
Set advice window in schedule
2s 672ms
And
Fill advice form
14s 813ms
And
Click advice save button and wait for advice form to disappear
30s 668ms
And
Go to "TRANSPORT_TABLE"
208ms
Then
Check advice data in SK API database "CONTAINER"
1s 110ms
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 203ms
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"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 835ms
When
Click button advice in transport table "TRANSPORT_ORDER"
113ms
And
Set advice window in schedule
2s 543ms
And
Fill advice form
14s 684ms
And
Click advice save button and wait for advice form to disappear
30s 742ms
And
Go to "TRANSPORT_TABLE"
246ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 040ms
After
Hooks.deleteTransportAfterTest()
107ms
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 173ms
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
9s 355ms
When
Click button advice in transport table "CONTAINER"
112ms
And
Set advice window in schedule in the past
2s 593ms
And
Fill advice form
14s 791ms
And
Click advice save button to check error message
083ms
Then
Check if possible advice alert is displayed
018ms
After
Hooks.deleteTransportAfterTest()
081ms
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 150ms
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
40s 117ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 228ms
And
Go to "TRANSPORT_TABLE"
209ms
When
Go to transport details "OWN_COLLECTION"
4s 465ms
And
Expand advice panel
111ms
And
Edit advice in transport details
14s 107ms
And
Fill arrival date field
2s 307ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 596ms
Then
Check advice data in database after edition "OWN_COLLECTION"
037ms
After
Hooks.deleteTransportAfterTest()
133ms
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 232ms
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 449ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 247ms
And
Go to "TRANSPORT_TABLE"
196ms
When
Go to transport details "CONTAINER"
4s 489ms
And
Expand advice panel
117ms
And
Edit advice in transport details
14s 138ms
And
Fill arrival date field
2s 308ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 592ms
Then
Check advice data in database after edition "CONTAINER"
040ms
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 275ms
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"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 359ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 268ms
And
Go to "TRANSPORT_TABLE"
264ms
When
Go to transport details "TRANSPORT_ORDER"
4s 456ms
And
Expand advice panel
110ms
And
Edit advice in transport details
14s 111ms
And
Fill arrival date field
2s 304ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 630ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
035ms
After
Hooks.deleteTransportAfterTest()
139ms