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 198ms
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 395ms
When
Click button advice in transport table "CONTAINER"
121ms
And
Set advice window in schedule
2s 678ms
And
Fill advice form
14s 791ms
And
Click advice save button and wait for advice form to disappear
30s 718ms
And
Go to "TRANSPORT_TABLE"
214ms
And
Go to transport details "CONTAINER"
4s 514ms
Then
Check are advice values equals
2s 348ms
After
Hooks.deleteTransportAfterTest()
119ms
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 219ms
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 332ms
When
Click button advice in transport table "OWN_COLLECTION"
121ms
And
Set advice window in schedule
2s 539ms
And
Fill advice form
14s 682ms
And
Click advice save button and wait for advice form to disappear
30s 730ms
And
Go to "TRANSPORT_TABLE"
217ms
And
Go to transport details "OWN_COLLECTION"
4s 496ms
Then
Check are advice values equals
2s 358ms
After
Hooks.deleteTransportAfterTest()
141ms
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 241ms
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 217ms
When
Click button advice in transport table "TRANSPORT_ORDER"
113ms
And
Set advice window in schedule
2s 526ms
And
Fill advice form
14s 746ms
And
Click advice save button and wait for advice form to disappear
30s 794ms
And
Go to "TRANSPORT_TABLE"
233ms
And
Go to transport details "TRANSPORT_ORDER"
4s 470ms
Then
Check are advice values equals
2s 340ms
After
Hooks.deleteTransportAfterTest()
102ms
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_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 346ms
When
Click button advice in transport table "OWN_COLLECTION"
128ms
And
Set advice window in schedule
2s 561ms
And
Fill advice form
14s 711ms
And
Click advice save button and wait for advice form to disappear
30s 722ms
And
Go to "TRANSPORT_TABLE"
183ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 170ms
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 779ms
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 308ms
When
Click button advice in transport table "CONTAINER"
099ms
And
Set advice window in schedule
2s 527ms
And
Fill advice form
14s 687ms
And
Click advice save button and wait for advice form to disappear
30s 718ms
And
Go to "TRANSPORT_TABLE"
204ms
Then
Check advice data in SK API database "CONTAINER"
3s 110ms
After
Hooks.deleteTransportAfterTest()
110ms
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 788ms
When
Click button advice in transport table "TRANSPORT_ORDER"
114ms
And
Set advice window in schedule
2s 529ms
And
Fill advice form
14s 825ms
And
Click advice save button and wait for advice form to disappear
30s 736ms
And
Go to "TRANSPORT_TABLE"
191ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 048ms
After
Hooks.deleteTransportAfterTest()
268ms
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 273ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
034ms
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 284ms
When
Click button advice in transport table "CONTAINER"
122ms
And
Set advice window in schedule in the past
2s 532ms
And
Fill advice form
14s 607ms
And
Click advice save button to check error message
079ms
Then
Check if possible advice alert is displayed
020ms
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 217ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
001ms
And
Add transport by SKApi in "MGW"
009ms
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 369ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 005ms
And
Go to "TRANSPORT_TABLE"
181ms
When
Go to transport details "OWN_COLLECTION"
4s 476ms
And
Expand advice panel
110ms
And
Edit advice in transport details
14s 084ms
And
Fill arrival date field
2s 313ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 599ms
Then
Check advice data in database after edition "OWN_COLLECTION"
037ms
After
Hooks.deleteTransportAfterTest()
135ms
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 322ms
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 337ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 137ms
And
Go to "TRANSPORT_TABLE"
221ms
When
Go to transport details "CONTAINER"
4s 528ms
And
Expand advice panel
126ms
And
Edit advice in transport details
14s 173ms
And
Fill arrival date field
2s 310ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 624ms
Then
Check advice data in database after edition "CONTAINER"
030ms
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 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 "EDIT_ADVICE" "super-admin-skz"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 284ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 190ms
And
Go to "TRANSPORT_TABLE"
255ms
When
Go to transport details "TRANSPORT_ORDER"
4s 486ms
And
Expand advice panel
109ms
And
Edit advice in transport details
14s 154ms
And
Fill arrival date field
2s 305ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 590ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
038ms
After
Hooks.deleteTransportAfterTest()
137ms