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 235ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
006ms
And
Add transport by SKApi in "MGW"
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
003ms
And
Check is transport "CONTAINER" created in transport table and set transport id
54s 486ms
When
Click button advice in transport table "CONTAINER"
080ms
And
Set advice window in schedule
2s 762ms
And
Fill advice form
14s 639ms
And
Click advice save button and wait for advice form to disappear
30s 759ms
And
Go to "TRANSPORT_TABLE"
202ms
And
Go to transport details "CONTAINER"
4s 453ms
Then
Check are advice values equals
2s 296ms
After
Hooks.deleteTransportAfterTest()
167ms
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 286ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
004ms
And
Add transport by SKApi in "MGW"
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
006ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
4s 064ms
When
Click button advice in transport table "OWN_COLLECTION"
069ms
And
Set advice window in schedule
2s 660ms
And
Fill advice form
14s 622ms
And
Click advice save button and wait for advice form to disappear
30s 710ms
And
Go to "TRANSPORT_TABLE"
193ms
And
Go to transport details "OWN_COLLECTION"
4s 443ms
Then
Check are advice values equals
2s 305ms
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 265ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
005ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
003ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 281ms
When
Click button advice in transport table "TRANSPORT_ORDER"
075ms
And
Set advice window in schedule
2s 664ms
And
Fill advice form
14s 639ms
And
Click advice save button and wait for advice form to disappear
30s 769ms
And
Go to "TRANSPORT_TABLE"
255ms
And
Go to transport details "TRANSPORT_ORDER"
4s 469ms
Then
Check are advice values equals
2s 308ms
After
Hooks.deleteTransportAfterTest()
163ms
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 306ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
005ms
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 483ms
When
Click button advice in transport table "OWN_COLLECTION"
082ms
And
Set advice window in schedule
2s 663ms
And
Fill advice form
14s 669ms
And
Click advice save button and wait for advice form to disappear
30s 771ms
And
Go to "TRANSPORT_TABLE"
190ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 229ms
After
Hooks.deleteTransportAfterTest()
161ms
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 310ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
004ms
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
6s 378ms
When
Click button advice in transport table "CONTAINER"
082ms
And
Set advice window in schedule
2s 617ms
And
Fill advice form
14s 706ms
And
Click advice save button and wait for advice form to disappear
30s 714ms
And
Go to "TRANSPORT_TABLE"
196ms
Then
Check advice data in SK API database "CONTAINER"
3s 119ms
After
Hooks.deleteTransportAfterTest()
126ms
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 224ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
007ms
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 863ms
When
Click button advice in transport table "TRANSPORT_ORDER"
085ms
And
Set advice window in schedule
2s 651ms
And
Fill advice form
14s 636ms
And
Click advice save button and wait for advice form to disappear
30s 711ms
And
Go to "TRANSPORT_TABLE"
227ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 039ms
After
Hooks.deleteTransportAfterTest()
133ms
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 263ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
002ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
003ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 357ms
When
Click button advice in transport table "CONTAINER"
077ms
And
Set advice window in schedule in the past
2s 660ms
And
Fill advice form
14s 636ms
And
Click advice save button to check error message
073ms
Then
Check if possible advice alert is displayed
021ms
After
Hooks.deleteTransportAfterTest()
100ms
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 217ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
003ms
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
43s 146ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 164ms
And
Go to "TRANSPORT_TABLE"
177ms
When
Go to transport details "OWN_COLLECTION"
4s 406ms
And
Expand advice panel
097ms
And
Edit advice in transport details
13s 976ms
And
Fill arrival date field
2s 281ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 157ms
Then
Check advice data in database after edition "OWN_COLLECTION"
029ms
After
Hooks.deleteTransportAfterTest()
163ms
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 320ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
003ms
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
34s 024ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 078ms
And
Go to "TRANSPORT_TABLE"
187ms
When
Go to transport details "CONTAINER"
4s 432ms
And
Expand advice panel
104ms
And
Edit advice in transport details
13s 957ms
And
Fill arrival date field
2s 276ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 631ms
Then
Check advice data in database after edition "CONTAINER"
029ms
After
Hooks.deleteTransportAfterTest()
116ms
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 541ms
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 950ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 100ms
And
Go to "TRANSPORT_TABLE"
246ms
When
Go to transport details "TRANSPORT_ORDER"
4s 447ms
And
Expand advice panel
109ms
And
Edit advice in transport details
13s 960ms
And
Fill arrival date field
2s 293ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 180ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
029ms
After
Hooks.deleteTransportAfterTest()
137ms