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 253ms
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
52s 056ms
When
Click button advice in transport table "CONTAINER"
084ms
And
Set advice window in schedule
2s 780ms
And
Fill advice form
14s 681ms
And
Click advice save button and wait for advice form to disappear
15s 780ms
And
Go to "TRANSPORT_TABLE"
185ms
And
Go to transport details "CONTAINER"
4s 440ms
Then
Check are advice values equals
2s 306ms
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 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"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
19s 099ms
When
Click button advice in transport table "OWN_COLLECTION"
099ms
And
Set advice window in schedule
2s 709ms
And
Fill advice form
14s 645ms
And
Click advice save button and wait for advice form to disappear
30s 749ms
And
Go to "TRANSPORT_TABLE"
187ms
And
Go to transport details "OWN_COLLECTION"
4s 482ms
Then
Check are advice values equals
2s 300ms
After
Hooks.deleteTransportAfterTest()
176ms
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 255ms
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 870ms
When
Click button advice in transport table "TRANSPORT_ORDER"
084ms
And
Set advice window in schedule
2s 608ms
And
Fill advice form
14s 664ms
And
Click advice save button and wait for advice form to disappear
30s 760ms
And
Go to "TRANSPORT_TABLE"
249ms
And
Go to transport details "TRANSPORT_ORDER"
4s 473ms
Then
Check are advice values equals
2s 296ms
After
Hooks.deleteTransportAfterTest()
158ms
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 303ms
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
4s 063ms
When
Click button advice in transport table "OWN_COLLECTION"
105ms
And
Set advice window in schedule
2s 614ms
And
Fill advice form
14s 570ms
And
Click advice save button and wait for advice form to disappear
30s 782ms
And
Go to "TRANSPORT_TABLE"
198ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 219ms
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 235ms
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 400ms
When
Click button advice in transport table "CONTAINER"
098ms
And
Set advice window in schedule
2s 612ms
And
Fill advice form
14s 590ms
And
Click advice save button and wait for advice form to disappear
30s 703ms
And
Go to "TRANSPORT_TABLE"
209ms
Then
Check advice data in SK API database "CONTAINER"
4s 122ms
After
Hooks.deleteTransportAfterTest()
157ms
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 286ms
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 867ms
When
Click button advice in transport table "TRANSPORT_ORDER"
094ms
And
Set advice window in schedule
2s 603ms
And
Fill advice form
14s 819ms
And
Click advice save button and wait for advice form to disappear
31s 254ms
And
Go to "TRANSPORT_TABLE"
214ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
2s 037ms
After
Hooks.deleteTransportAfterTest()
185ms
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 235ms
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"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 985ms
When
Click button advice in transport table "CONTAINER"
092ms
And
Set advice window in schedule in the past
2s 643ms
And
Fill advice form
14s 678ms
And
Click advice save button to check error message
090ms
Then
Check if possible advice alert is displayed
018ms
After
Hooks.deleteTransportAfterTest()
127ms
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_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
43s 141ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
33s 218ms
And
Go to "TRANSPORT_TABLE"
195ms
When
Go to transport details "OWN_COLLECTION"
4s 454ms
And
Expand advice panel
100ms
And
Edit advice in transport details
13s 982ms
And
Fill arrival date field
2s 261ms
And
Click "save-transport-and-close" save button and wait for form to disappear
660ms
Then
Check advice data in database after edition "OWN_COLLECTION"
026ms
After
Hooks.deleteTransportAfterTest()
190ms
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 238ms
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
3s 401ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 068ms
And
Go to "TRANSPORT_TABLE"
199ms
When
Go to transport details "CONTAINER"
4s 454ms
And
Expand advice panel
104ms
And
Edit advice in transport details
13s 926ms
And
Fill arrival date field
2s 253ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 149ms
Then
Check advice data in database after edition "CONTAINER"
028ms
After
Hooks.deleteTransportAfterTest()
118ms
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 224ms
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 966ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 185ms
And
Go to "TRANSPORT_TABLE"
226ms
When
Go to transport details "TRANSPORT_ORDER"
4s 439ms
And
Expand advice panel
108ms
And
Edit advice in transport details
13s 991ms
And
Fill arrival date field
2s 242ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 606ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
025ms
After
Hooks.deleteTransportAfterTest()
141ms