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_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
54s 407ms
When
Click button advice in transport table "CONTAINER"
124ms
And
Set advice window in schedule
2s 621ms
And
Fill advice form
14s 756ms
And
Click advice save button and wait for advice form to disappear
30s 791ms
And
Go to "TRANSPORT_TABLE"
183ms
And
Go to transport details "CONTAINER"
4s 513ms
Then
Check are advice values equals
2s 316ms
After
Hooks.deleteTransportAfterTest()
130ms
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 842ms
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
1m 527ms
When
Click button advice in transport table "OWN_COLLECTION"
139ms
And
Set advice window in schedule
2s 540ms
And
Fill advice form
14s 792ms
And
Click advice save button and wait for advice form to disappear
30s 755ms
And
Go to "TRANSPORT_TABLE"
188ms
And
Go to transport details "OWN_COLLECTION"
4s 465ms
Then
Check are advice values equals
2s 302ms
After
Hooks.deleteTransportAfterTest()
128ms
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 565ms
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"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 239ms
When
Click button advice in transport table "TRANSPORT_ORDER"
113ms
And
Set advice window in schedule
2s 522ms
And
Fill advice form
14s 808ms
And
Click advice save button and wait for advice form to disappear
30s 721ms
And
Go to "TRANSPORT_TABLE"
232ms
And
Go to transport details "TRANSPORT_ORDER"
4s 479ms
Then
Check are advice values equals
2s 275ms
After
Hooks.deleteTransportAfterTest()
149ms
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 295ms
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 402ms
When
Click button advice in transport table "OWN_COLLECTION"
111ms
And
Set advice window in schedule
2s 568ms
And
Fill advice form
14s 764ms
And
Click advice save button and wait for advice form to disappear
30s 781ms
And
Go to "TRANSPORT_TABLE"
154ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 173ms
After
Hooks.deleteTransportAfterTest()
149ms
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 266ms
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
6s 304ms
When
Click button advice in transport table "CONTAINER"
129ms
And
Set advice window in schedule
2s 518ms
And
Fill advice form
14s 867ms
And
Click advice save button and wait for advice form to disappear
30s 745ms
And
Go to "TRANSPORT_TABLE"
172ms
Then
Check advice data in SK API database "CONTAINER"
4s 105ms
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 238ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
003ms
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 219ms
When
Click button advice in transport table "TRANSPORT_ORDER"
132ms
And
Set advice window in schedule
2s 545ms
And
Fill advice form
14s 797ms
And
Click advice save button and wait for advice form to disappear
30s 747ms
And
Go to "TRANSPORT_TABLE"
221ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 035ms
After
Hooks.deleteTransportAfterTest()
131ms
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 223ms
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 335ms
When
Click button advice in transport table "CONTAINER"
130ms
And
Set advice window in schedule in the past
2s 514ms
And
Fill advice form
14s 820ms
And
Click advice save button to check error message
101ms
Then
Check if possible advice alert is displayed
021ms
After
Hooks.deleteTransportAfterTest()
085ms
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 218ms
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"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
42s 463ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 344ms
And
Go to "TRANSPORT_TABLE"
150ms
When
Go to transport details "OWN_COLLECTION"
4s 494ms
And
Expand advice panel
131ms
And
Edit advice in transport details
14s 149ms
And
Fill arrival date field
2s 314ms
And
Click "save-transport-and-close" save button and wait for form to disappear
641ms
Then
Check advice data in database after edition "OWN_COLLECTION"
029ms
After
Hooks.deleteTransportAfterTest()
112ms
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_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
48s 417ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 244ms
And
Go to "TRANSPORT_TABLE"
151ms
When
Go to transport details "CONTAINER"
4s 489ms
And
Expand advice panel
117ms
And
Edit advice in transport details
14s 122ms
And
Fill arrival date field
2s 284ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 628ms
Then
Check advice data in database after edition "CONTAINER"
034ms
After
Hooks.deleteTransportAfterTest()
157ms
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 244ms
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 "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 314ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 344ms
And
Go to "TRANSPORT_TABLE"
222ms
When
Go to transport details "TRANSPORT_ORDER"
4s 485ms
And
Expand advice panel
126ms
And
Edit advice in transport details
14s 173ms
And
Fill arrival date field
2s 313ms
And
Click "save-transport-and-close" save button and wait for form to disappear
659ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
039ms
After
Hooks.deleteTransportAfterTest()
136ms