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 247ms
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 413ms
When
Click button advice in transport table "CONTAINER"
133ms
And
Set advice window in schedule
2s 598ms
And
Fill advice form
14s 808ms
And
Click advice save button and wait for advice form to disappear
30s 720ms
And
Go to "TRANSPORT_TABLE"
185ms
And
Go to transport details "CONTAINER"
4s 508ms
Then
Check are advice values equals
2s 339ms
After
Hooks.deleteTransportAfterTest()
142ms
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 236ms
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"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 370ms
When
Click button advice in transport table "OWN_COLLECTION"
149ms
And
Set advice window in schedule
2s 510ms
And
Fill advice form
14s 771ms
And
Click advice save button and wait for advice form to disappear
30s 774ms
And
Go to "TRANSPORT_TABLE"
181ms
And
Go to transport details "OWN_COLLECTION"
4s 478ms
Then
Check are advice values equals
2s 358ms
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 225ms
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 196ms
When
Click button advice in transport table "TRANSPORT_ORDER"
109ms
And
Set advice window in schedule
2s 504ms
And
Fill advice form
14s 693ms
And
Click advice save button and wait for advice form to disappear
30s 715ms
And
Go to "TRANSPORT_TABLE"
219ms
And
Go to transport details "TRANSPORT_ORDER"
4s 497ms
Then
Check are advice values equals
2s 345ms
After
Hooks.deleteTransportAfterTest()
116ms
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 299ms
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 370ms
When
Click button advice in transport table "OWN_COLLECTION"
118ms
And
Set advice window in schedule
2s 536ms
And
Fill advice form
14s 721ms
And
Click advice save button and wait for advice form to disappear
30s 760ms
And
Go to "TRANSPORT_TABLE"
187ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 174ms
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 277ms
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
6s 291ms
When
Click button advice in transport table "CONTAINER"
110ms
And
Set advice window in schedule
2s 515ms
And
Fill advice form
14s 769ms
And
Click advice save button and wait for advice form to disappear
30s 714ms
And
Go to "TRANSPORT_TABLE"
155ms
Then
Check advice data in SK API database "CONTAINER"
4s 098ms
After
Hooks.deleteTransportAfterTest()
128ms
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"
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
6s 220ms
When
Click button advice in transport table "TRANSPORT_ORDER"
117ms
And
Set advice window in schedule
2s 504ms
And
Fill advice form
14s 723ms
And
Click advice save button and wait for advice form to disappear
30s 732ms
And
Go to "TRANSPORT_TABLE"
219ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 062ms
After
Hooks.deleteTransportAfterTest()
115ms
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 217ms
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 296ms
When
Click button advice in transport table "CONTAINER"
107ms
And
Set advice window in schedule in the past
2s 519ms
And
Fill advice form
14s 859ms
And
Click advice save button to check error message
102ms
Then
Check if possible advice alert is displayed
018ms
After
Hooks.deleteTransportAfterTest()
132ms
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 265ms
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
42s 443ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 230ms
And
Go to "TRANSPORT_TABLE"
185ms
When
Go to transport details "OWN_COLLECTION"
4s 464ms
And
Expand advice panel
108ms
And
Edit advice in transport details
14s 137ms
And
Fill arrival date field
2s 309ms
And
Click "save-transport-and-close" save button and wait for form to disappear
682ms
Then
Check advice data in database after edition "OWN_COLLECTION"
028ms
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 254ms
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 451ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 249ms
And
Go to "TRANSPORT_TABLE"
173ms
When
Go to transport details "CONTAINER"
4s 511ms
And
Expand advice panel
117ms
And
Edit advice in transport details
14s 097ms
And
Fill arrival date field
2s 300ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 632ms
Then
Check advice data in database after edition "CONTAINER"
030ms
After
Hooks.deleteTransportAfterTest()
114ms
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 248ms
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 360ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 278ms
And
Go to "TRANSPORT_TABLE"
207ms
When
Go to transport details "TRANSPORT_ORDER"
4s 487ms
And
Expand advice panel
125ms
And
Edit advice in transport details
14s 154ms
And
Fill arrival date field
2s 287ms
And
Click "save-transport-and-close" save button and wait for form to disappear
637ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
035ms
After
Hooks.deleteTransportAfterTest()
141ms