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 260ms
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"
003ms
And
Check is transport "CONTAINER" created in transport table and set transport id
54s 471ms
When
Click button advice in transport table "CONTAINER"
089ms
And
Set advice window in schedule
2s 894ms
And
Fill advice form
14s 696ms
And
Click advice save button and wait for advice form to disappear
30s 730ms
And
Go to "TRANSPORT_TABLE"
213ms
And
Go to transport details "CONTAINER"
4s 530ms
Then
Check are advice values equals
2s 345ms
After
Hooks.deleteTransportAfterTest()
148ms
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 269ms
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
4s 062ms
When
Click button advice in transport table "OWN_COLLECTION"
077ms
And
Set advice window in schedule
2s 676ms
And
Fill advice form
14s 628ms
And
Click advice save button and wait for advice form to disappear
30s 762ms
And
Go to "TRANSPORT_TABLE"
158ms
And
Go to transport details "OWN_COLLECTION"
4s 470ms
Then
Check are advice values equals
2s 301ms
After
Hooks.deleteTransportAfterTest()
160ms
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 334ms
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"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 871ms
When
Click button advice in transport table "TRANSPORT_ORDER"
084ms
And
Set advice window in schedule
2s 679ms
And
Fill advice form
14s 647ms
And
Click advice save button and wait for advice form to disappear
30s 710ms
And
Go to "TRANSPORT_TABLE"
252ms
And
Go to transport details "TRANSPORT_ORDER"
4s 475ms
Then
Check are advice values equals
2s 300ms
After
Hooks.deleteTransportAfterTest()
176ms
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 287ms
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"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
4s 096ms
When
Click button advice in transport table "OWN_COLLECTION"
092ms
And
Set advice window in schedule
2s 687ms
And
Fill advice form
14s 590ms
And
Click advice save button and wait for advice form to disappear
30s 702ms
And
Go to "TRANSPORT_TABLE"
196ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 227ms
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 275ms
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 967ms
When
Click button advice in transport table "CONTAINER"
070ms
And
Set advice window in schedule
2s 650ms
And
Fill advice form
14s 604ms
And
Click advice save button and wait for advice form to disappear
30s 720ms
And
Go to "TRANSPORT_TABLE"
199ms
Then
Check advice data in SK API database "CONTAINER"
2s 110ms
After
Hooks.deleteTransportAfterTest()
149ms
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_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 902ms
When
Click button advice in transport table "TRANSPORT_ORDER"
070ms
And
Set advice window in schedule
2s 660ms
And
Fill advice form
14s 651ms
And
Click advice save button and wait for advice form to disappear
30s 769ms
And
Go to "TRANSPORT_TABLE"
227ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 038ms
After
Hooks.deleteTransportAfterTest()
153ms
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 261ms
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 399ms
When
Click button advice in transport table "CONTAINER"
073ms
And
Set advice window in schedule in the past
2s 718ms
And
Fill advice form
14s 693ms
And
Click advice save button to check error message
093ms
Then
Check if possible advice alert is displayed
022ms
After
Hooks.deleteTransportAfterTest()
129ms
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 268ms
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
39s 541ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 171ms
And
Go to "TRANSPORT_TABLE"
198ms
When
Go to transport details "OWN_COLLECTION"
4s 458ms
And
Expand advice panel
110ms
And
Edit advice in transport details
13s 995ms
And
Fill arrival date field
2s 296ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 624ms
Then
Check advice data in database after edition "OWN_COLLECTION"
032ms
After
Hooks.deleteTransportAfterTest()
127ms
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 266ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
001ms
And
Add transport by SKApi in "MGW"
002ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
34s 021ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 188ms
And
Go to "TRANSPORT_TABLE"
207ms
When
Go to transport details "CONTAINER"
4s 516ms
And
Expand advice panel
113ms
And
Edit advice in transport details
13s 997ms
And
Fill arrival date field
2s 264ms
And
Click "save-transport-and-close" save button and wait for form to disappear
646ms
Then
Check advice data in database after edition "CONTAINER"
045ms
After
Hooks.deleteTransportAfterTest()
130ms
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 209ms
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"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
48s 976ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 129ms
And
Go to "TRANSPORT_TABLE"
237ms
When
Go to transport details "TRANSPORT_ORDER"
4s 415ms
And
Expand advice panel
115ms
And
Edit advice in transport details
14s 002ms
And
Fill arrival date field
2s 257ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 570ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
030ms
After
Hooks.deleteTransportAfterTest()
137ms