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 258ms
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
54s 424ms
When
Click button advice in transport table "CONTAINER"
089ms
And
Set advice window in schedule
2s 805ms
And
Fill advice form
14s 663ms
And
Click advice save button and wait for advice form to disappear
15s 761ms
And
Go to "TRANSPORT_TABLE"
208ms
And
Go to transport details "CONTAINER"
4s 515ms
Then
Check are advice values equals
2s 324ms
After
Hooks.deleteTransportAfterTest()
191ms
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 268ms
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
19s 082ms
When
Click button advice in transport table "OWN_COLLECTION"
086ms
And
Set advice window in schedule
2s 652ms
And
Fill advice form
14s 592ms
And
Click advice save button and wait for advice form to disappear
30s 749ms
And
Go to "TRANSPORT_TABLE"
181ms
And
Go to transport details "OWN_COLLECTION"
4s 460ms
Then
Check are advice values equals
2s 303ms
After
Hooks.deleteTransportAfterTest()
137ms
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 249ms
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"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 275ms
When
Click button advice in transport table "TRANSPORT_ORDER"
084ms
And
Set advice window in schedule
2s 619ms
And
Fill advice form
14s 582ms
And
Click advice save button and wait for advice form to disappear
30s 682ms
And
Go to "TRANSPORT_TABLE"
256ms
And
Go to transport details "TRANSPORT_ORDER"
4s 475ms
Then
Check are advice values equals
2s 326ms
After
Hooks.deleteTransportAfterTest()
111ms
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 217ms
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"
077ms
And
Set advice window in schedule
2s 595ms
And
Fill advice form
14s 623ms
And
Click advice save button and wait for advice form to disappear
30s 728ms
And
Go to "TRANSPORT_TABLE"
214ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 191ms
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 181ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
6s 351ms
When
Click button advice in transport table "CONTAINER"
089ms
And
Set advice window in schedule
2s 606ms
And
Fill advice form
14s 634ms
And
Click advice save button and wait for advice form to disappear
30s 734ms
And
Go to "TRANSPORT_TABLE"
209ms
Then
Check advice data in SK API database "CONTAINER"
3s 099ms
After
Hooks.deleteTransportAfterTest()
112ms
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 245ms
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 861ms
When
Click button advice in transport table "TRANSPORT_ORDER"
091ms
And
Set advice window in schedule
2s 612ms
And
Fill advice form
14s 731ms
And
Click advice save button and wait for advice form to disappear
30s 741ms
And
Go to "TRANSPORT_TABLE"
231ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 045ms
After
Hooks.deleteTransportAfterTest()
160ms
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 278ms
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 354ms
When
Click button advice in transport table "CONTAINER"
092ms
And
Set advice window in schedule in the past
2s 712ms
And
Fill advice form
14s 661ms
And
Click advice save button to check error message
119ms
Then
Check if possible advice alert is displayed
016ms
After
Hooks.deleteTransportAfterTest()
099ms
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 246ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
004ms
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 539ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 139ms
And
Go to "TRANSPORT_TABLE"
206ms
When
Go to transport details "OWN_COLLECTION"
4s 476ms
And
Expand advice panel
112ms
And
Edit advice in transport details
13s 983ms
And
Fill arrival date field
2s 285ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 629ms
Then
Check advice data in database after edition "OWN_COLLECTION"
038ms
After
Hooks.deleteTransportAfterTest()
163ms
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 289ms
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"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
33s 441ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
47s 984ms
And
Go to "TRANSPORT_TABLE"
220ms
When
Go to transport details "CONTAINER"
4s 502ms
And
Expand advice panel
113ms
And
Edit advice in transport details
14s 047ms
And
Fill arrival date field
2s 285ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 638ms
Then
Check advice data in database after edition "CONTAINER"
036ms
After
Hooks.deleteTransportAfterTest()
131ms
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 247ms
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 376ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 116ms
And
Go to "TRANSPORT_TABLE"
244ms
When
Go to transport details "TRANSPORT_ORDER"
4s 473ms
And
Expand advice panel
122ms
And
Edit advice in transport details
14s 063ms
And
Fill arrival date field
2s 265ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 611ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
033ms
After
Hooks.deleteTransportAfterTest()
201ms