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 118ms
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
54s 350ms
When
Click button advice in transport table "CONTAINER"
084ms
And
Set advice window in schedule
2s 622ms
And
Fill advice form
14s 395ms
And
Click advice save button and wait for advice form to disappear
30s 674ms
And
Go to "TRANSPORT_TABLE"
181ms
And
Go to transport details "CONTAINER"
4s 457ms
Then
Check are advice values equals
2s 281ms
After
Hooks.deleteTransportAfterTest()
102ms
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 113ms
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
3s 356ms
When
Click button advice in transport table "OWN_COLLECTION"
094ms
And
Set advice window in schedule
2s 571ms
And
Fill advice form
14s 395ms
And
Click advice save button and wait for advice form to disappear
30s 706ms
And
Go to "TRANSPORT_TABLE"
187ms
And
Go to transport details "OWN_COLLECTION"
4s 389ms
Then
Check are advice values equals
2s 302ms
After
Hooks.deleteTransportAfterTest()
109ms
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 122ms
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 814ms
When
Click button advice in transport table "TRANSPORT_ORDER"
079ms
And
Set advice window in schedule
2s 552ms
And
Fill advice form
14s 373ms
And
Click advice save button and wait for advice form to disappear
30s 720ms
And
Go to "TRANSPORT_TABLE"
197ms
And
Go to transport details "TRANSPORT_ORDER"
4s 414ms
Then
Check are advice values equals
2s 254ms
After
Hooks.deleteTransportAfterTest()
103ms
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 136ms
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
6s 355ms
When
Click button advice in transport table "OWN_COLLECTION"
079ms
And
Set advice window in schedule
2s 514ms
And
Fill advice form
14s 306ms
And
Click advice save button and wait for advice form to disappear
30s 726ms
And
Go to "TRANSPORT_TABLE"
167ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 136ms
After
Hooks.deleteTransportAfterTest()
121ms
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 156ms
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 298ms
When
Click button advice in transport table "CONTAINER"
098ms
And
Set advice window in schedule
2s 495ms
And
Fill advice form
14s 537ms
And
Click advice save button and wait for advice form to disappear
30s 780ms
And
Go to "TRANSPORT_TABLE"
190ms
Then
Check advice data in SK API database "CONTAINER"
4s 103ms
After
Hooks.deleteTransportAfterTest()
136ms
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 206ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
010ms
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 211ms
When
Click button advice in transport table "TRANSPORT_ORDER"
096ms
And
Set advice window in schedule
2s 547ms
And
Fill advice form
14s 628ms
And
Click advice save button and wait for advice form to disappear
30s 711ms
And
Go to "TRANSPORT_TABLE"
221ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 049ms
After
Hooks.deleteTransportAfterTest()
118ms
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 204ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
004ms
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 322ms
When
Click button advice in transport table "CONTAINER"
108ms
And
Set advice window in schedule in the past
2s 558ms
And
Fill advice form
14s 583ms
And
Click advice save button to check error message
080ms
Then
Check if possible advice alert is displayed
017ms
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 212ms
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 "EDIT_ADVICE" "super-admin-skz"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
42s 457ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 112ms
And
Go to "TRANSPORT_TABLE"
209ms
When
Go to transport details "OWN_COLLECTION"
4s 466ms
And
Expand advice panel
111ms
And
Edit advice in transport details
14s
And
Fill arrival date field
2s 259ms
And
Click "save-transport-and-close" save button and wait for form to disappear
640ms
Then
Check advice data in database after edition "OWN_COLLECTION"
032ms
After
Hooks.deleteTransportAfterTest()
110ms
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 173ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
48s 398ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
47s 935ms
And
Go to "TRANSPORT_TABLE"
197ms
When
Go to transport details "CONTAINER"
4s 509ms
And
Expand advice panel
110ms
And
Edit advice in transport details
13s 946ms
And
Fill arrival date field
2s 300ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 652ms
Then
Check advice data in database after edition "CONTAINER"
026ms
After
Hooks.deleteTransportAfterTest()
118ms
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"
001ms
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 315ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 089ms
And
Go to "TRANSPORT_TABLE"
244ms
When
Go to transport details "TRANSPORT_ORDER"
4s 459ms
And
Expand advice panel
105ms
And
Edit advice in transport details
13s 985ms
And
Fill arrival date field
2s 279ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 659ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
035ms
After
Hooks.deleteTransportAfterTest()
108ms