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 250ms
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
55s 048ms
When
Click button advice in transport table "CONTAINER"
083ms
And
Set advice window in schedule
2s 698ms
And
Fill advice form
14s 639ms
And
Click advice save button and wait for advice form to disappear
30s 666ms
And
Go to "TRANSPORT_TABLE"
215ms
And
Go to transport details "CONTAINER"
4s 496ms
Then
Check are advice values equals
2s 345ms
After
Hooks.deleteTransportAfterTest()
171ms
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 301ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
3s 451ms
When
Click button advice in transport table "OWN_COLLECTION"
088ms
And
Set advice window in schedule
2s 672ms
And
Fill advice form
14s 674ms
And
Click advice save button and wait for advice form to disappear
30s 738ms
And
Go to "TRANSPORT_TABLE"
161ms
And
Go to transport details "OWN_COLLECTION"
4s 433ms
Then
Check are advice values equals
2s 318ms
After
Hooks.deleteTransportAfterTest()
127ms
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 282ms
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"
003ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 291ms
When
Click button advice in transport table "TRANSPORT_ORDER"
066ms
And
Set advice window in schedule
2s 633ms
And
Fill advice form
14s 618ms
And
Click advice save button and wait for advice form to disappear
30s 725ms
And
Go to "TRANSPORT_TABLE"
222ms
And
Go to transport details "TRANSPORT_ORDER"
4s 409ms
Then
Check are advice values equals
2s 300ms
After
Hooks.deleteTransportAfterTest()
156ms
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 251ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
004ms
And
Add transport by SKApi in "MGW"
004ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
004ms
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"
077ms
And
Set advice window in schedule
2s 642ms
And
Fill advice form
14s 621ms
And
Click advice save button and wait for advice form to disappear
30s 709ms
And
Go to "TRANSPORT_TABLE"
157ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 203ms
After
Hooks.deleteTransportAfterTest()
123ms
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 220ms
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 969ms
When
Click button advice in transport table "CONTAINER"
072ms
And
Set advice window in schedule
2s 628ms
And
Fill advice form
14s 652ms
And
Click advice save button and wait for advice form to disappear
30s 733ms
And
Go to "TRANSPORT_TABLE"
200ms
Then
Check advice data in SK API database "CONTAINER"
3s 117ms
After
Hooks.deleteTransportAfterTest()
151ms
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 231ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
001ms
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 918ms
When
Click button advice in transport table "TRANSPORT_ORDER"
078ms
And
Set advice window in schedule
2s 649ms
And
Fill advice form
14s 646ms
And
Click advice save button and wait for advice form to disappear
30s 728ms
And
Go to "TRANSPORT_TABLE"
212ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 041ms
After
Hooks.deleteTransportAfterTest()
141ms
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 207ms
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"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 972ms
When
Click button advice in transport table "CONTAINER"
087ms
And
Set advice window in schedule in the past
2s 644ms
And
Fill advice form
14s 723ms
And
Click advice save button to check error message
095ms
Then
Check if possible advice alert is displayed
019ms
After
Hooks.deleteTransportAfterTest()
165ms
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 272ms
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
43s 148ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 159ms
And
Go to "TRANSPORT_TABLE"
179ms
When
Go to transport details "OWN_COLLECTION"
4s 405ms
And
Expand advice panel
105ms
And
Edit advice in transport details
14s
And
Fill arrival date field
2s 295ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 099ms
Then
Check advice data in database after edition "OWN_COLLECTION"
037ms
After
Hooks.deleteTransportAfterTest()
126ms
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 234ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
004ms
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 453ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 174ms
And
Go to "TRANSPORT_TABLE"
165ms
When
Go to transport details "CONTAINER"
4s 435ms
And
Expand advice panel
104ms
And
Edit advice in transport details
13s 957ms
And
Fill arrival date field
2s 278ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 679ms
Then
Check advice data in database after edition "CONTAINER"
028ms
After
Hooks.deleteTransportAfterTest()
115ms
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 196ms
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
33s 942ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 116ms
And
Go to "TRANSPORT_TABLE"
216ms
When
Go to transport details "TRANSPORT_ORDER"
4s 435ms
And
Expand advice panel
107ms
And
Edit advice in transport details
13s 998ms
And
Fill arrival date field
2s 290ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 116ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
034ms
After
Hooks.deleteTransportAfterTest()
113ms