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"
2s 715ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "CONTAINER" created in transport table and set transport id
52s
When
Click button advice in transport table "CONTAINER"
231ms
And
Set advice window in schedule
3s 512ms
And
Fill advice form
18s 279ms
And
Click advice save button and wait for advice form to disappear
33s 271ms
And
Go to "TRANSPORT_TABLE"
450ms
And
Go to transport details "CONTAINER"
4s 932ms
Then
Check are advice values equals
2s 904ms
After
Hooks.deleteTransportAfterTest()
951ms
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"
2s 772ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
52s 171ms
When
Click button advice in transport table "OWN_COLLECTION"
228ms
And
Set advice window in schedule
3s 468ms
And
Fill advice form
18s 169ms
And
Click advice save button and wait for advice form to disappear
33s 267ms
And
Go to "TRANSPORT_TABLE"
464ms
And
Go to transport details "OWN_COLLECTION"
4s 919ms
Then
Check are advice values equals
2s 885ms
After
Hooks.deleteTransportAfterTest()
852ms
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"
2s 772ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
51s 632ms
When
Click button advice in transport table "TRANSPORT_ORDER"
222ms
And
Set advice window in schedule
3s 508ms
And
Fill advice form
18s 424ms
And
Click advice save button and wait for advice form to disappear
33s 840ms
And
Go to "TRANSPORT_TABLE"
493ms
And
Go to transport details "TRANSPORT_ORDER"
4s 923ms
Then
Check are advice values equals
2s 906ms
After
Hooks.deleteTransportAfterTest()
886ms
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"
2s 745ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
52s 202ms
When
Click button advice in transport table "OWN_COLLECTION"
229ms
And
Set advice window in schedule
3s 769ms
And
Fill advice form
18s 084ms
And
Click advice save button and wait for advice form to disappear
18s 361ms
And
Go to "TRANSPORT_TABLE"
465ms
Then
Check advice data in SK API database "OWN_COLLECTION"
12s 600ms
After
Hooks.deleteTransportAfterTest()
938ms
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"
2s 831ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
019ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
035ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 3s 999ms
When
Click button advice in transport table "CONTAINER"
225ms
And
Set advice window in schedule
3s 564ms
And
Fill advice form
18s 123ms
And
Click advice save button and wait for advice form to disappear
33s 323ms
And
Go to "TRANSPORT_TABLE"
463ms
Then
Check advice data in SK API database "CONTAINER"
238ms
After
Hooks.deleteTransportAfterTest()
1s 022ms
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"
2s 778ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
019ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
58s 533ms
When
Click button advice in transport table "TRANSPORT_ORDER"
236ms
And
Set advice window in schedule
3s 498ms
And
Fill advice form
18s 195ms
And
Click advice save button and wait for advice form to disappear
33s 824ms
And
Go to "TRANSPORT_TABLE"
483ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
090ms
After
Hooks.deleteTransportAfterTest()
898ms
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"
2s 767ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
035ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 1s 085ms
When
Click button advice in transport table "CONTAINER"
229ms
And
Set advice window in schedule in the past
3s 493ms
And
Fill advice form
18s 455ms
And
Click advice save button to check error message
266ms
Then
Check if possible advice alert is displayed
067ms
After
Hooks.deleteTransportAfterTest()
742ms
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 507ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
033ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
34s 122ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
55s 503ms
And
Go to "TRANSPORT_TABLE"
471ms
When
Go to transport details "OWN_COLLECTION"
4s 863ms
And
Expand advice panel
267ms
And
Edit advice in transport details
16s 961ms
And
Fill arrival date field
2s 663ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 485ms
Then
Check advice data in database after edition "OWN_COLLECTION"
093ms
After
Hooks.deleteTransportAfterTest()
923ms
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 742ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
033ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
033ms
And
Check is transport "CONTAINER" created in transport table and set transport id
18s 965ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
55s 369ms
And
Go to "TRANSPORT_TABLE"
461ms
When
Go to transport details "CONTAINER"
4s 946ms
And
Expand advice panel
273ms
And
Edit advice in transport details
16s 725ms
And
Fill arrival date field
2s 780ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 484ms
Then
Check advice data in database after edition "CONTAINER"
101ms
After
Hooks.deleteTransportAfterTest()
925ms
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 724ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
033ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
15s 587ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
56s 286ms
And
Go to "TRANSPORT_TABLE"
495ms
When
Go to transport details "TRANSPORT_ORDER"
4s 874ms
And
Expand advice panel
266ms
And
Edit advice in transport details
16s 825ms
And
Fill arrival date field
2s 632ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 481ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
103ms
After
Hooks.deleteTransportAfterTest()
1s 041ms