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 246ms
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"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
54s 372ms
When
Click button advice in transport table "CONTAINER"
131ms
And
Set advice window in schedule
2s 628ms
And
Fill advice form
14s 865ms
And
Click advice save button and wait for advice form to disappear
30s 757ms
And
Go to "TRANSPORT_TABLE"
191ms
And
Go to transport details "CONTAINER"
4s 527ms
Then
Check are advice values equals
2s 322ms
After
Hooks.deleteTransportAfterTest()
126ms
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 238ms
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
3s 372ms
When
Click button advice in transport table "OWN_COLLECTION"
131ms
And
Set advice window in schedule
2s 525ms
And
Fill advice form
14s 785ms
And
Click advice save button and wait for advice form to disappear
30s 764ms
And
Go to "TRANSPORT_TABLE"
180ms
And
Go to transport details "OWN_COLLECTION"
4s 470ms
Then
Check are advice values equals
2s 322ms
After
Hooks.deleteTransportAfterTest()
126ms
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 264ms
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"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 233ms
When
Click button advice in transport table "TRANSPORT_ORDER"
126ms
And
Set advice window in schedule
2s 535ms
And
Fill advice form
14s 782ms
And
Click advice save button and wait for advice form to disappear
30s 759ms
And
Go to "TRANSPORT_TABLE"
211ms
And
Go to transport details "TRANSPORT_ORDER"
4s 484ms
Then
Check are advice values equals
2s 305ms
After
Hooks.deleteTransportAfterTest()
095ms
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"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 376ms
When
Click button advice in transport table "OWN_COLLECTION"
120ms
And
Set advice window in schedule
2s 518ms
And
Fill advice form
14s 732ms
And
Click advice save button and wait for advice form to disappear
30s 742ms
And
Go to "TRANSPORT_TABLE"
186ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 169ms
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 227ms
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 303ms
When
Click button advice in transport table "CONTAINER"
130ms
And
Set advice window in schedule
2s 483ms
And
Fill advice form
14s 841ms
And
Click advice save button and wait for advice form to disappear
30s 783ms
And
Go to "TRANSPORT_TABLE"
171ms
Then
Check advice data in SK API database "CONTAINER"
3s 102ms
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 239ms
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
6s 787ms
When
Click button advice in transport table "TRANSPORT_ORDER"
114ms
And
Set advice window in schedule
2s 499ms
And
Fill advice form
14s 803ms
And
Click advice save button and wait for advice form to disappear
30s 762ms
And
Go to "TRANSPORT_TABLE"
229ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 057ms
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 272ms
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
6s 300ms
When
Click button advice in transport table "CONTAINER"
125ms
And
Set advice window in schedule in the past
2s 542ms
And
Fill advice form
14s 768ms
And
Click advice save button to check error message
083ms
Then
Check if possible advice alert is displayed
023ms
After
Hooks.deleteTransportAfterTest()
071ms
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 274ms
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"
008ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
42s 450ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 088ms
And
Go to "TRANSPORT_TABLE"
187ms
When
Go to transport details "OWN_COLLECTION"
4s 473ms
And
Expand advice panel
110ms
And
Edit advice in transport details
14s 157ms
And
Fill arrival date field
2s 318ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 605ms
Then
Check advice data in database after edition "OWN_COLLECTION"
031ms
After
Hooks.deleteTransportAfterTest()
104ms
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 267ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
003ms
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 403ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 171ms
And
Go to "TRANSPORT_TABLE"
176ms
When
Go to transport details "CONTAINER"
4s 485ms
And
Expand advice panel
110ms
And
Edit advice in transport details
14s 162ms
And
Fill arrival date field
2s 302ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 595ms
Then
Check advice data in database after edition "CONTAINER"
031ms
After
Hooks.deleteTransportAfterTest()
128ms
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 239ms
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 "EDIT_ADVICE" "super-admin-skz"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 337ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 064ms
And
Go to "TRANSPORT_TABLE"
196ms
When
Go to transport details "TRANSPORT_ORDER"
4s 447ms
And
Expand advice panel
115ms
And
Edit advice in transport details
14s 077ms
And
Fill arrival date field
2s 311ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 117ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
035ms
After
Hooks.deleteTransportAfterTest()
126ms