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 270ms
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
55s 024ms
When
Click button advice in transport table "CONTAINER"
074ms
And
Set advice window in schedule
2s 749ms
And
Fill advice form
14s 689ms
And
Click advice save button and wait for advice form to disappear
30s 715ms
And
Go to "TRANSPORT_TABLE"
196ms
And
Go to transport details "CONTAINER"
4s 478ms
Then
Check are advice values equals
2s 327ms
After
Hooks.deleteTransportAfterTest()
174ms
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 251ms
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 425ms
When
Click button advice in transport table "OWN_COLLECTION"
086ms
And
Set advice window in schedule
2s 650ms
And
Fill advice form
14s 567ms
And
Click advice save button and wait for advice form to disappear
30s 713ms
And
Go to "TRANSPORT_TABLE"
226ms
And
Go to transport details "OWN_COLLECTION"
4s 453ms
Then
Check are advice values equals
2s 307ms
After
Hooks.deleteTransportAfterTest()
162ms
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 298ms
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 858ms
When
Click button advice in transport table "TRANSPORT_ORDER"
079ms
And
Set advice window in schedule
2s 615ms
And
Fill advice form
14s 636ms
And
Click advice save button and wait for advice form to disappear
30s 734ms
And
Go to "TRANSPORT_TABLE"
224ms
And
Go to transport details "TRANSPORT_ORDER"
4s 416ms
Then
Check are advice values equals
2s 318ms
After
Hooks.deleteTransportAfterTest()
144ms
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 271ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
004ms
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
1s 161ms
When
Click button advice in transport table "OWN_COLLECTION"
099ms
And
Set advice window in schedule
2s 649ms
And
Fill advice form
14s 616ms
And
Click advice save button and wait for advice form to disappear
30s 711ms
And
Go to "TRANSPORT_TABLE"
211ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 230ms
After
Hooks.deleteTransportAfterTest()
169ms
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 253ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
003ms
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 952ms
When
Click button advice in transport table "CONTAINER"
093ms
And
Set advice window in schedule
2s 635ms
And
Fill advice form
14s 690ms
And
Click advice save button and wait for advice form to disappear
30s 740ms
And
Go to "TRANSPORT_TABLE"
180ms
Then
Check advice data in SK API database "CONTAINER"
3s 123ms
After
Hooks.deleteTransportAfterTest()
154ms
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 209ms
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 "CREATE_ADVICE" "super-admin-skz"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 873ms
When
Click button advice in transport table "TRANSPORT_ORDER"
088ms
And
Set advice window in schedule
2s 636ms
And
Fill advice form
14s 576ms
And
Click advice save button and wait for advice form to disappear
30s 758ms
And
Go to "TRANSPORT_TABLE"
203ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 036ms
After
Hooks.deleteTransportAfterTest()
126ms
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 220ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
013ms
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 358ms
When
Click button advice in transport table "CONTAINER"
073ms
And
Set advice window in schedule in the past
2s 643ms
And
Fill advice form
14s 435ms
And
Click advice save button to check error message
076ms
Then
Check if possible advice alert is displayed
015ms
After
Hooks.deleteTransportAfterTest()
107ms
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 194ms
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
40s 056ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
47s 725ms
And
Go to "TRANSPORT_TABLE"
188ms
When
Go to transport details "OWN_COLLECTION"
4s 449ms
And
Expand advice panel
094ms
And
Edit advice in transport details
13s 853ms
And
Fill arrival date field
2s 253ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 153ms
Then
Check advice data in database after edition "OWN_COLLECTION"
033ms
After
Hooks.deleteTransportAfterTest()
147ms
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 242ms
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 964ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
47s 945ms
And
Go to "TRANSPORT_TABLE"
186ms
When
Go to transport details "CONTAINER"
4s 418ms
And
Expand advice panel
091ms
And
Edit advice in transport details
13s 823ms
And
Fill arrival date field
2s 230ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 610ms
Then
Check advice data in database after edition "CONTAINER"
033ms
After
Hooks.deleteTransportAfterTest()
164ms
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"
2s 736ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
135ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
003ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 172ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
47s 979ms
And
Go to "TRANSPORT_TABLE"
257ms
When
Go to transport details "TRANSPORT_ORDER"
4s 434ms
And
Expand advice panel
118ms
And
Edit advice in transport details
13s 958ms
And
Fill arrival date field
2s 281ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 170ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
035ms
After
Hooks.deleteTransportAfterTest()
137ms