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 208ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
005ms
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 438ms
When
Click button advice in transport table "CONTAINER"
113ms
And
Set advice window in schedule
2s 661ms
And
Fill advice form
14s 751ms
And
Click advice save button and wait for advice form to disappear
30s 758ms
And
Go to "TRANSPORT_TABLE"
213ms
And
Go to transport details "CONTAINER"
4s 506ms
Then
Check are advice values equals
2s 333ms
After
Hooks.deleteTransportAfterTest()
134ms
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 722ms
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 381ms
When
Click button advice in transport table "OWN_COLLECTION"
104ms
And
Set advice window in schedule
2s 542ms
And
Fill advice form
14s 754ms
And
Click advice save button and wait for advice form to disappear
30s 688ms
And
Go to "TRANSPORT_TABLE"
213ms
And
Go to transport details "OWN_COLLECTION"
4s 486ms
Then
Check are advice values equals
2s 354ms
After
Hooks.deleteTransportAfterTest()
154ms
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 205ms
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"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 228ms
When
Click button advice in transport table "TRANSPORT_ORDER"
125ms
And
Set advice window in schedule
2s 550ms
And
Fill advice form
14s 735ms
And
Click advice save button and wait for advice form to disappear
30s 765ms
And
Go to "TRANSPORT_TABLE"
220ms
And
Go to transport details "TRANSPORT_ORDER"
4s 453ms
Then
Check are advice values equals
2s 337ms
After
Hooks.deleteTransportAfterTest()
139ms
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_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 386ms
When
Click button advice in transport table "OWN_COLLECTION"
124ms
And
Set advice window in schedule
2s 573ms
And
Fill advice form
14s 710ms
And
Click advice save button and wait for advice form to disappear
30s 732ms
And
Go to "TRANSPORT_TABLE"
205ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 155ms
After
Hooks.deleteTransportAfterTest()
091ms
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 229ms
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 363ms
When
Click button advice in transport table "CONTAINER"
103ms
And
Set advice window in schedule
2s 610ms
And
Fill advice form
14s 755ms
And
Click advice save button and wait for advice form to disappear
30s 761ms
And
Go to "TRANSPORT_TABLE"
224ms
Then
Check advice data in SK API database "CONTAINER"
1s 101ms
After
Hooks.deleteTransportAfterTest()
120ms
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 202ms
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 230ms
When
Click button advice in transport table "TRANSPORT_ORDER"
119ms
And
Set advice window in schedule
2s 515ms
And
Fill advice form
14s 722ms
And
Click advice save button and wait for advice form to disappear
30s 764ms
And
Go to "TRANSPORT_TABLE"
219ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 048ms
After
Hooks.deleteTransportAfterTest()
120ms
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 215ms
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 332ms
When
Click button advice in transport table "CONTAINER"
127ms
And
Set advice window in schedule in the past
2s 536ms
And
Fill advice form
14s 706ms
And
Click advice save button to check error message
092ms
Then
Check if possible advice alert is displayed
019ms
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 243ms
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
42s 483ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 247ms
And
Go to "TRANSPORT_TABLE"
218ms
When
Go to transport details "OWN_COLLECTION"
4s 478ms
And
Expand advice panel
122ms
And
Edit advice in transport details
14s 159ms
And
Fill arrival date field
2s 304ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 616ms
Then
Check advice data in database after edition "OWN_COLLECTION"
042ms
After
Hooks.deleteTransportAfterTest()
113ms
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 214ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
33s 411ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 242ms
And
Go to "TRANSPORT_TABLE"
223ms
When
Go to transport details "CONTAINER"
4s 531ms
And
Expand advice panel
118ms
And
Edit advice in transport details
14s 162ms
And
Fill arrival date field
2s 290ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 619ms
Then
Check advice data in database after edition "CONTAINER"
033ms
After
Hooks.deleteTransportAfterTest()
131ms
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 271ms
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 335ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 234ms
And
Go to "TRANSPORT_TABLE"
259ms
When
Go to transport details "TRANSPORT_ORDER"
4s 475ms
And
Expand advice panel
120ms
And
Edit advice in transport details
14s 129ms
And
Fill arrival date field
2s 291ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 630ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
040ms
After
Hooks.deleteTransportAfterTest()
112ms