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 242ms
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 411ms
When
Click button advice in transport table "CONTAINER"
116ms
And
Set advice window in schedule
2s 731ms
And
Fill advice form
14s 656ms
And
Click advice save button and wait for advice form to disappear
30s 699ms
And
Go to "TRANSPORT_TABLE"
215ms
And
Go to transport details "CONTAINER"
4s 523ms
Then
Check are advice values equals
2s 344ms
After
Hooks.deleteTransportAfterTest()
116ms
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 333ms
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 379ms
When
Click button advice in transport table "OWN_COLLECTION"
114ms
And
Set advice window in schedule
2s 576ms
And
Fill advice form
14s 602ms
And
Click advice save button and wait for advice form to disappear
30s 744ms
And
Go to "TRANSPORT_TABLE"
230ms
And
Go to transport details "OWN_COLLECTION"
4s 491ms
Then
Check are advice values equals
2s 341ms
After
Hooks.deleteTransportAfterTest()
193ms
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 283ms
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"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
1s 146ms
When
Click button advice in transport table "TRANSPORT_ORDER"
116ms
And
Set advice window in schedule
2s 550ms
And
Fill advice form
14s 727ms
And
Click advice save button and wait for advice form to disappear
30s 704ms
And
Go to "TRANSPORT_TABLE"
249ms
And
Go to transport details "TRANSPORT_ORDER"
4s 495ms
Then
Check are advice values equals
2s 337ms
After
Hooks.deleteTransportAfterTest()
132ms
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 260ms
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 387ms
When
Click button advice in transport table "OWN_COLLECTION"
121ms
And
Set advice window in schedule
2s 571ms
And
Fill advice form
14s 701ms
And
Click advice save button and wait for advice form to disappear
30s 685ms
And
Go to "TRANSPORT_TABLE"
226ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 175ms
After
Hooks.deleteTransportAfterTest()
122ms
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 226ms
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 340ms
When
Click button advice in transport table "CONTAINER"
108ms
And
Set advice window in schedule
2s 570ms
And
Fill advice form
14s 712ms
And
Click advice save button and wait for advice form to disappear
30s 749ms
And
Go to "TRANSPORT_TABLE"
189ms
Then
Check advice data in SK API database "CONTAINER"
3s 105ms
After
Hooks.deleteTransportAfterTest()
130ms
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"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 817ms
When
Click button advice in transport table "TRANSPORT_ORDER"
106ms
And
Set advice window in schedule
2s 546ms
And
Fill advice form
14s 787ms
And
Click advice save button and wait for advice form to disappear
30s 772ms
And
Go to "TRANSPORT_TABLE"
224ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 040ms
After
Hooks.deleteTransportAfterTest()
103ms
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 233ms
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
9s 367ms
When
Click button advice in transport table "CONTAINER"
110ms
And
Set advice window in schedule in the past
2s 594ms
And
Fill advice form
14s 735ms
And
Click advice save button to check error message
090ms
Then
Check if possible advice alert is displayed
024ms
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 298ms
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"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
39s 457ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 163ms
And
Go to "TRANSPORT_TABLE"
224ms
When
Go to transport details "OWN_COLLECTION"
4s 484ms
And
Expand advice panel
111ms
And
Edit advice in transport details
14s 159ms
And
Fill arrival date field
2s 311ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 635ms
Then
Check advice data in database after edition "OWN_COLLECTION"
039ms
After
Hooks.deleteTransportAfterTest()
122ms
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 250ms
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
33s 420ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 220ms
And
Go to "TRANSPORT_TABLE"
205ms
When
Go to transport details "CONTAINER"
4s 536ms
And
Expand advice panel
115ms
And
Edit advice in transport details
14s 130ms
And
Fill arrival date field
2s 298ms
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"
042ms
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 282ms
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 "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 293ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 186ms
And
Go to "TRANSPORT_TABLE"
245ms
When
Go to transport details "TRANSPORT_ORDER"
4s 489ms
And
Expand advice panel
109ms
And
Edit advice in transport details
14s 116ms
And
Fill arrival date field
2s 302ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 615ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
035ms
After
Hooks.deleteTransportAfterTest()
110ms