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 841ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
037ms
And
Check is transport "CONTAINER" created in transport table and set transport id
49s 114ms
When
Click button advice in transport table "CONTAINER"
229ms
And
Set advice window in schedule
3s 821ms
And
Fill advice form
18s 046ms
And
Click advice save button and wait for advice form to disappear
33s 759ms
And
Go to "TRANSPORT_TABLE"
470ms
And
Go to transport details "CONTAINER"
4s 945ms
Then
Check are advice values equals
2s 886ms
After
Hooks.deleteTransportAfterTest()
876ms
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 770ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
021ms
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 339ms
When
Click button advice in transport table "OWN_COLLECTION"
221ms
And
Set advice window in schedule
3s 670ms
And
Fill advice form
18s 052ms
And
Click advice save button and wait for advice form to disappear
33s 293ms
And
Go to "TRANSPORT_TABLE"
452ms
And
Go to transport details "OWN_COLLECTION"
4s 887ms
Then
Check are advice values equals
2s 912ms
After
Hooks.deleteTransportAfterTest()
916ms
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 850ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
035ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
52s 740ms
When
Click button advice in transport table "TRANSPORT_ORDER"
237ms
And
Set advice window in schedule
3s 709ms
And
Fill advice form
18s 044ms
And
Click advice save button and wait for advice form to disappear
33s 271ms
And
Go to "TRANSPORT_TABLE"
500ms
And
Go to transport details "TRANSPORT_ORDER"
4s 917ms
Then
Check are advice values equals
2s 898ms
After
Hooks.deleteTransportAfterTest()
877ms
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 871ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
037ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
52s 332ms
When
Click button advice in transport table "OWN_COLLECTION"
231ms
And
Set advice window in schedule
3s 595ms
And
Fill advice form
18s 010ms
And
Click advice save button and wait for advice form to disappear
33s 810ms
And
Go to "TRANSPORT_TABLE"
449ms
Then
Check advice data in SK API database "OWN_COLLECTION"
468ms
After
Hooks.deleteTransportAfterTest()
1s 031ms
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 840ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
023ms
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 099ms
When
Click button advice in transport table "CONTAINER"
232ms
And
Set advice window in schedule
3s 583ms
And
Fill advice form
17s 945ms
And
Click advice save button and wait for advice form to disappear
33s 271ms
And
Go to "TRANSPORT_TABLE"
436ms
Then
Check advice data in SK API database "CONTAINER"
245ms
After
Hooks.deleteTransportAfterTest()
1s 063ms
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 851ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
038ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
58s 640ms
When
Click button advice in transport table "TRANSPORT_ORDER"
251ms
And
Set advice window in schedule
3s 582ms
And
Fill advice form
18s 205ms
And
Click advice save button and wait for advice form to disappear
33s 314ms
And
Go to "TRANSPORT_TABLE"
481ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
091ms
After
Hooks.deleteTransportAfterTest()
1s 057ms
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 749ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
035ms
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 104ms
When
Click button advice in transport table "CONTAINER"
235ms
And
Set advice window in schedule in the past
3s 714ms
And
Fill advice form
18s 113ms
And
Click advice save button to check error message
178ms
Then
Check if possible advice alert is displayed
069ms
After
Hooks.deleteTransportAfterTest()
624ms
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 777ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
022ms
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 332ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
55s 121ms
And
Go to "TRANSPORT_TABLE"
381ms
When
Go to transport details "OWN_COLLECTION"
4s 855ms
And
Expand advice panel
224ms
And
Edit advice in transport details
16s 508ms
And
Fill arrival date field
2s 540ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 449ms
Then
Check advice data in database after edition "OWN_COLLECTION"
111ms
After
Hooks.deleteTransportAfterTest()
1s
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 819ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
19s 078ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
40s 203ms
And
Go to "TRANSPORT_TABLE"
450ms
When
Go to transport details "CONTAINER"
4s 941ms
And
Expand advice panel
262ms
And
Edit advice in transport details
16s 671ms
And
Fill arrival date field
2s 638ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 502ms
Then
Check advice data in database after edition "CONTAINER"
082ms
After
Hooks.deleteTransportAfterTest()
1s 092ms
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 900ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
037ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
037ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 789ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
55s 613ms
And
Go to "TRANSPORT_TABLE"
472ms
When
Go to transport details "TRANSPORT_ORDER"
4s 885ms
And
Expand advice panel
251ms
And
Edit advice in transport details
16s 538ms
And
Fill arrival date field
2s 574ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 513ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
103ms
After
Hooks.deleteTransportAfterTest()
1s 017ms