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"
3s 051ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
025ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "CONTAINER" created in transport table and set transport id
48s 980ms
When
Click button advice in transport table "CONTAINER"
212ms
And
Set advice window in schedule
3s 510ms
And
Fill advice form
18s 002ms
And
Click advice save button and wait for advice form to disappear
33s 228ms
And
Go to "TRANSPORT_TABLE"
445ms
And
Go to transport details "CONTAINER"
4s 948ms
Then
Check are advice values equals
2s 898ms
After
Hooks.deleteTransportAfterTest()
860ms
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 794ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
019ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
035ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
55s 240ms
When
Click button advice in transport table "OWN_COLLECTION"
237ms
And
Set advice window in schedule
3s 560ms
And
Fill advice form
17s 828ms
And
Click advice save button and wait for advice form to disappear
33s 890ms
And
Go to "TRANSPORT_TABLE"
448ms
And
Go to transport details "OWN_COLLECTION"
4s 858ms
Then
Check are advice values equals
2s 904ms
After
Hooks.deleteTransportAfterTest()
879ms
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 819ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
036ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
51s 692ms
When
Click button advice in transport table "TRANSPORT_ORDER"
239ms
And
Set advice window in schedule
3s 542ms
And
Fill advice form
17s 913ms
And
Click advice save button and wait for advice form to disappear
33s 287ms
And
Go to "TRANSPORT_TABLE"
489ms
And
Go to transport details "TRANSPORT_ORDER"
4s 898ms
Then
Check are advice values equals
2s 917ms
After
Hooks.deleteTransportAfterTest()
965ms
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 710ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
024ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
52s 185ms
When
Click button advice in transport table "OWN_COLLECTION"
218ms
And
Set advice window in schedule
3s 489ms
And
Fill advice form
18s 017ms
And
Click advice save button and wait for advice form to disappear
33s 305ms
And
Go to "TRANSPORT_TABLE"
410ms
Then
Check advice data in SK API database "OWN_COLLECTION"
448ms
After
Hooks.deleteTransportAfterTest()
1s 009ms
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 841ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
037ms
And
Add transport by SKApi in "MGW"
019ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 1s 028ms
When
Click button advice in transport table "CONTAINER"
250ms
And
Set advice window in schedule
3s 723ms
And
Fill advice form
17s 935ms
And
Click advice save button and wait for advice form to disappear
33s 840ms
And
Go to "TRANSPORT_TABLE"
473ms
Then
Check advice data in SK API database "CONTAINER"
236ms
After
Hooks.deleteTransportAfterTest()
962ms
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 768ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
58s 568ms
When
Click button advice in transport table "TRANSPORT_ORDER"
245ms
And
Set advice window in schedule
3s 583ms
And
Fill advice form
18s 114ms
And
Click advice save button and wait for advice form to disappear
33s 868ms
And
Go to "TRANSPORT_TABLE"
492ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
087ms
After
Hooks.deleteTransportAfterTest()
914ms
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 734ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
037ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 994ms
When
Click button advice in transport table "CONTAINER"
231ms
And
Set advice window in schedule in the past
3s 453ms
And
Fill advice form
17s 991ms
And
Click advice save button to check error message
160ms
Then
Check if possible advice alert is displayed
069ms
After
Hooks.deleteTransportAfterTest()
654ms
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 561ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
025ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
034ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
34s 205ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
54s 891ms
And
Go to "TRANSPORT_TABLE"
442ms
When
Go to transport details "OWN_COLLECTION"
4s 885ms
And
Expand advice panel
258ms
And
Edit advice in transport details
16s 581ms
And
Fill arrival date field
2s 576ms
And
Click "save-transport-and-close" save button and wait for form to disappear
1s 956ms
Then
Check advice data in database after edition "OWN_COLLECTION"
084ms
After
Hooks.deleteTransportAfterTest()
932ms
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 681ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
034ms
And
Check is transport "CONTAINER" created in transport table and set transport id
34s 009ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
54s 826ms
And
Go to "TRANSPORT_TABLE"
463ms
When
Go to transport details "CONTAINER"
4s 910ms
And
Expand advice panel
278ms
And
Edit advice in transport details
16s 645ms
And
Fill arrival date field
2s 547ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 486ms
Then
Check advice data in database after edition "CONTAINER"
113ms
After
Hooks.deleteTransportAfterTest()
983ms
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 795ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
035ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
18s 649ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
40s 082ms
And
Go to "TRANSPORT_TABLE"
452ms
When
Go to transport details "TRANSPORT_ORDER"
4s 879ms
And
Expand advice panel
266ms
And
Edit advice in transport details
16s 545ms
And
Fill arrival date field
2s 636ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 493ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
076ms
After
Hooks.deleteTransportAfterTest()
930ms