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 254ms
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 448ms
When
Click button advice in transport table "CONTAINER"
126ms
And
Set advice window in schedule
2s 724ms
And
Fill advice form
14s 652ms
And
Click advice save button and wait for advice form to disappear
31s 296ms
And
Go to "TRANSPORT_TABLE"
180ms
And
Go to transport details "CONTAINER"
4s 501ms
Then
Check are advice values equals
2s 313ms
After
Hooks.deleteTransportAfterTest()
116ms
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 351ms
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 951ms
When
Click button advice in transport table "OWN_COLLECTION"
144ms
And
Set advice window in schedule
2s 507ms
And
Fill advice form
14s 660ms
And
Click advice save button and wait for advice form to disappear
30s 768ms
And
Go to "TRANSPORT_TABLE"
178ms
And
Go to transport details "OWN_COLLECTION"
4s 478ms
Then
Check are advice values equals
2s 332ms
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 200ms
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
3s 251ms
When
Click button advice in transport table "TRANSPORT_ORDER"
123ms
And
Set advice window in schedule
2s 499ms
And
Fill advice form
14s 601ms
And
Click advice save button and wait for advice form to disappear
30s 751ms
And
Go to "TRANSPORT_TABLE"
234ms
And
Go to transport details "TRANSPORT_ORDER"
4s 472ms
Then
Check are advice values equals
2s 340ms
After
Hooks.deleteTransportAfterTest()
192ms
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 208ms
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 374ms
When
Click button advice in transport table "OWN_COLLECTION"
133ms
And
Set advice window in schedule
2s 517ms
And
Fill advice form
14s 727ms
And
Click advice save button and wait for advice form to disappear
30s 715ms
And
Go to "TRANSPORT_TABLE"
193ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 154ms
After
Hooks.deleteTransportAfterTest()
172ms
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 198ms
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 320ms
When
Click button advice in transport table "CONTAINER"
123ms
And
Set advice window in schedule
2s 500ms
And
Fill advice form
14s 628ms
And
Click advice save button and wait for advice form to disappear
30s 744ms
And
Go to "TRANSPORT_TABLE"
179ms
Then
Check advice data in SK API database "CONTAINER"
4s 104ms
After
Hooks.deleteTransportAfterTest()
140ms
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 265ms
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 223ms
When
Click button advice in transport table "TRANSPORT_ORDER"
098ms
And
Set advice window in schedule
2s 541ms
And
Fill advice form
14s 599ms
And
Click advice save button and wait for advice form to disappear
30s 766ms
And
Go to "TRANSPORT_TABLE"
197ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 049ms
After
Hooks.deleteTransportAfterTest()
138ms
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 277ms
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 321ms
When
Click button advice in transport table "CONTAINER"
119ms
And
Set advice window in schedule in the past
2s 557ms
And
Fill advice form
14s 614ms
And
Click advice save button to check error message
107ms
Then
Check if possible advice alert is displayed
151ms
After
Hooks.deleteTransportAfterTest()
102ms
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 227ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
004ms
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 433ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 100ms
And
Go to "TRANSPORT_TABLE"
190ms
When
Go to transport details "OWN_COLLECTION"
4s 492ms
And
Expand advice panel
128ms
And
Edit advice in transport details
14s 128ms
And
Fill arrival date field
2s 305ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 155ms
Then
Check advice data in database after edition "OWN_COLLECTION"
035ms
After
Hooks.deleteTransportAfterTest()
165ms
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 255ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
001ms
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 420ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 108ms
And
Go to "TRANSPORT_TABLE"
181ms
When
Go to transport details "CONTAINER"
4s 444ms
And
Expand advice panel
123ms
And
Edit advice in transport details
14s 095ms
And
Fill arrival date field
2s 285ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 645ms
Then
Check advice data in database after edition "CONTAINER"
039ms
After
Hooks.deleteTransportAfterTest()
106ms
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 268ms
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"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 323ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 130ms
And
Go to "TRANSPORT_TABLE"
215ms
When
Go to transport details "TRANSPORT_ORDER"
4s 452ms
And
Expand advice panel
124ms
And
Edit advice in transport details
14s 050ms
And
Fill arrival date field
2s 293ms
And
Click "save-transport-and-close" save button and wait for form to disappear
663ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
029ms
After
Hooks.deleteTransportAfterTest()
140ms