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 518ms
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
55s 055ms
When
Click button advice in transport table "CONTAINER"
091ms
And
Set advice window in schedule
2s 708ms
And
Fill advice form
14s 590ms
And
Click advice save button and wait for advice form to disappear
31s 292ms
And
Go to "TRANSPORT_TABLE"
206ms
And
Go to transport details "CONTAINER"
4s 435ms
Then
Check are advice values equals
2s 327ms
After
Hooks.deleteTransportAfterTest()
143ms
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_OWN_COLLECTION" "super-admin-skz"
003ms
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 086ms
When
Click button advice in transport table "OWN_COLLECTION"
067ms
And
Set advice window in schedule
2s 649ms
And
Fill advice form
14s 566ms
And
Click advice save button and wait for advice form to disappear
30s 723ms
And
Go to "TRANSPORT_TABLE"
177ms
And
Go to transport details "OWN_COLLECTION"
4s 417ms
Then
Check are advice values equals
2s 318ms
After
Hooks.deleteTransportAfterTest()
128ms
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 243ms
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 900ms
When
Click button advice in transport table "TRANSPORT_ORDER"
075ms
And
Set advice window in schedule
2s 635ms
And
Fill advice form
14s 630ms
And
Click advice save button and wait for advice form to disappear
30s 706ms
And
Go to "TRANSPORT_TABLE"
203ms
And
Go to transport details "TRANSPORT_ORDER"
4s 429ms
Then
Check are advice values equals
2s 303ms
After
Hooks.deleteTransportAfterTest()
134ms
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 288ms
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 462ms
When
Click button advice in transport table "OWN_COLLECTION"
079ms
And
Set advice window in schedule
2s 637ms
And
Fill advice form
14s 635ms
And
Click advice save button and wait for advice form to disappear
30s 751ms
And
Go to "TRANSPORT_TABLE"
203ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 197ms
After
Hooks.deleteTransportAfterTest()
150ms
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 391ms
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
6s 982ms
When
Click button advice in transport table "CONTAINER"
074ms
And
Set advice window in schedule
2s 651ms
And
Fill advice form
14s 639ms
And
Click advice save button and wait for advice form to disappear
30s 674ms
And
Go to "TRANSPORT_TABLE"
186ms
Then
Check advice data in SK API database "CONTAINER"
2s 110ms
After
Hooks.deleteTransportAfterTest()
143ms
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 282ms
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"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 915ms
When
Click button advice in transport table "TRANSPORT_ORDER"
078ms
And
Set advice window in schedule
2s 632ms
And
Fill advice form
14s 624ms
And
Click advice save button and wait for advice form to disappear
30s 734ms
And
Go to "TRANSPORT_TABLE"
186ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 040ms
After
Hooks.deleteTransportAfterTest()
156ms
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 246ms
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 987ms
When
Click button advice in transport table "CONTAINER"
076ms
And
Set advice window in schedule in the past
2s 700ms
And
Fill advice form
14s 659ms
And
Click advice save button to check error message
085ms
Then
Check if possible advice alert is displayed
028ms
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 258ms
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 "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
40s 130ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 116ms
And
Go to "TRANSPORT_TABLE"
163ms
When
Go to transport details "OWN_COLLECTION"
4s 440ms
And
Expand advice panel
117ms
And
Edit advice in transport details
13s 930ms
And
Fill arrival date field
2s 297ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 632ms
Then
Check advice data in database after edition "OWN_COLLECTION"
034ms
After
Hooks.deleteTransportAfterTest()
117ms
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 229ms
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
36s 518ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 128ms
And
Go to "TRANSPORT_TABLE"
162ms
When
Go to transport details "CONTAINER"
4s 425ms
And
Expand advice panel
105ms
And
Edit advice in transport details
13s 999ms
And
Fill arrival date field
2s 247ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 633ms
Then
Check advice data in database after edition "CONTAINER"
035ms
After
Hooks.deleteTransportAfterTest()
143ms
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 182ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
003ms
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
33s 948ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 124ms
And
Go to "TRANSPORT_TABLE"
227ms
When
Go to transport details "TRANSPORT_ORDER"
4s 428ms
And
Expand advice panel
109ms
And
Edit advice in transport details
13s 962ms
And
Fill arrival date field
2s 304ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 635ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
031ms
After
Hooks.deleteTransportAfterTest()
123ms