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 217ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
013ms
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 391ms
When
Click button advice in transport table "CONTAINER"
114ms
And
Set advice window in schedule
2s 744ms
And
Fill advice form
14s 871ms
And
Click advice save button and wait for advice form to disappear
30s 725ms
And
Go to "TRANSPORT_TABLE"
212ms
And
Go to transport details "CONTAINER"
4s 538ms
Then
Check are advice values equals
2s 327ms
After
Hooks.deleteTransportAfterTest()
146ms
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 261ms
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 348ms
When
Click button advice in transport table "OWN_COLLECTION"
125ms
And
Set advice window in schedule
2s 522ms
And
Fill advice form
14s 662ms
And
Click advice save button and wait for advice form to disappear
30s 758ms
And
Go to "TRANSPORT_TABLE"
229ms
And
Go to transport details "OWN_COLLECTION"
4s 475ms
Then
Check are advice values equals
2s 336ms
After
Hooks.deleteTransportAfterTest()
139ms
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 161ms
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 237ms
When
Click button advice in transport table "TRANSPORT_ORDER"
109ms
And
Set advice window in schedule
2s 513ms
And
Fill advice form
14s 719ms
And
Click advice save button and wait for advice form to disappear
30s 752ms
And
Go to "TRANSPORT_TABLE"
260ms
And
Go to transport details "TRANSPORT_ORDER"
4s 489ms
Then
Check are advice values equals
2s 340ms
After
Hooks.deleteTransportAfterTest()
147ms
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 233ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
3s 403ms
When
Click button advice in transport table "OWN_COLLECTION"
102ms
And
Set advice window in schedule
2s 599ms
And
Fill advice form
14s 666ms
And
Click advice save button and wait for advice form to disappear
30s 690ms
And
Go to "TRANSPORT_TABLE"
214ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 174ms
After
Hooks.deleteTransportAfterTest()
131ms
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 180ms
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
9s 342ms
When
Click button advice in transport table "CONTAINER"
107ms
And
Set advice window in schedule
2s 613ms
And
Fill advice form
14s 752ms
And
Click advice save button and wait for advice form to disappear
30s 733ms
And
Go to "TRANSPORT_TABLE"
216ms
Then
Check advice data in SK API database "CONTAINER"
1s 094ms
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 218ms
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 820ms
When
Click button advice in transport table "TRANSPORT_ORDER"
097ms
And
Set advice window in schedule
2s 527ms
And
Fill advice form
14s 684ms
And
Click advice save button and wait for advice form to disappear
30s 813ms
And
Go to "TRANSPORT_TABLE"
251ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 057ms
After
Hooks.deleteTransportAfterTest()
096ms
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 131ms
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 352ms
When
Click button advice in transport table "CONTAINER"
107ms
And
Set advice window in schedule in the past
2s 594ms
And
Fill advice form
14s 748ms
And
Click advice save button to check error message
099ms
Then
Check if possible advice alert is displayed
024ms
After
Hooks.deleteTransportAfterTest()
149ms
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 222ms
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"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
39s 470ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 177ms
And
Go to "TRANSPORT_TABLE"
204ms
When
Go to transport details "OWN_COLLECTION"
4s 474ms
And
Expand advice panel
107ms
And
Edit advice in transport details
14s 071ms
And
Fill arrival date field
2s 296ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 622ms
Then
Check advice data in database after edition "OWN_COLLECTION"
040ms
After
Hooks.deleteTransportAfterTest()
143ms
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_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 412ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 225ms
And
Go to "TRANSPORT_TABLE"
221ms
When
Go to transport details "CONTAINER"
4s 561ms
And
Expand advice panel
117ms
And
Edit advice in transport details
14s 168ms
And
Fill arrival date field
2s 290ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 659ms
Then
Check advice data in database after edition "CONTAINER"
032ms
After
Hooks.deleteTransportAfterTest()
137ms
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 239ms
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 346ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 368ms
And
Go to "TRANSPORT_TABLE"
255ms
When
Go to transport details "TRANSPORT_ORDER"
4s 484ms
And
Expand advice panel
108ms
And
Edit advice in transport details
14s 120ms
And
Fill arrival date field
2s 303ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 648ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
042ms
After
Hooks.deleteTransportAfterTest()
110ms