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 683ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
025ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "CONTAINER" created in transport table and set transport id
49s 034ms
When
Click button advice in transport table "CONTAINER"
238ms
And
Set advice window in schedule
3s 710ms
And
Fill advice form
18s 047ms
And
Click advice save button and wait for advice form to disappear
33s 875ms
And
Go to "TRANSPORT_TABLE"
472ms
And
Go to transport details "CONTAINER"
4s 920ms
Then
Check are advice values equals
2s 912ms
After
Hooks.deleteTransportAfterTest()
912ms
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 876ms
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"
034ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
52s 232ms
When
Click button advice in transport table "OWN_COLLECTION"
237ms
And
Set advice window in schedule
3s 659ms
And
Fill advice form
18s 177ms
And
Click advice save button and wait for advice form to disappear
33s 229ms
And
Go to "TRANSPORT_TABLE"
453ms
And
Go to transport details "OWN_COLLECTION"
4s 875ms
Then
Check are advice values equals
2s 899ms
After
Hooks.deleteTransportAfterTest()
901ms
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 793ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
023ms
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
52s 543ms
When
Click button advice in transport table "TRANSPORT_ORDER"
241ms
And
Set advice window in schedule
3s 489ms
And
Fill advice form
18s 127ms
And
Click advice save button and wait for advice form to disappear
33s 848ms
And
Go to "TRANSPORT_TABLE"
465ms
And
Go to transport details "TRANSPORT_ORDER"
4s 904ms
Then
Check are advice values equals
2s 897ms
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 686ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
52s 245ms
When
Click button advice in transport table "OWN_COLLECTION"
235ms
And
Set advice window in schedule
3s 649ms
And
Fill advice form
18s 359ms
And
Click advice save button and wait for advice form to disappear
33s 232ms
And
Go to "TRANSPORT_TABLE"
468ms
Then
Check advice data in SK API database "OWN_COLLECTION"
423ms
After
Hooks.deleteTransportAfterTest()
892ms
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 667ms
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"
033ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 1s 056ms
When
Click button advice in transport table "CONTAINER"
229ms
And
Set advice window in schedule
3s 521ms
And
Fill advice form
18s 059ms
And
Click advice save button and wait for advice form to disappear
33s 824ms
And
Go to "TRANSPORT_TABLE"
442ms
Then
Check advice data in SK API database "CONTAINER"
236ms
After
Hooks.deleteTransportAfterTest()
942ms
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 747ms
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"
034ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
58s 623ms
When
Click button advice in transport table "TRANSPORT_ORDER"
241ms
And
Set advice window in schedule
3s 503ms
And
Fill advice form
18s 254ms
And
Click advice save button and wait for advice form to disappear
33s 851ms
And
Go to "TRANSPORT_TABLE"
481ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
092ms
After
Hooks.deleteTransportAfterTest()
982ms
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 686ms
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"
033ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 997ms
When
Click button advice in transport table "CONTAINER"
218ms
And
Set advice window in schedule in the past
3s 649ms
And
Fill advice form
18s 133ms
And
Click advice save button to check error message
182ms
Then
Check if possible advice alert is displayed
064ms
After
Hooks.deleteTransportAfterTest()
699ms
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 622ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
033ms
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 215ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
55s 887ms
And
Go to "TRANSPORT_TABLE"
426ms
When
Go to transport details "OWN_COLLECTION"
4s 859ms
And
Expand advice panel
268ms
And
Edit advice in transport details
16s 719ms
And
Fill arrival date field
2s 601ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 490ms
Then
Check advice data in database after edition "OWN_COLLECTION"
099ms
After
Hooks.deleteTransportAfterTest()
1s 034ms
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 673ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
133ms
And
Check is transport "CONTAINER" created in transport table and set transport id
18s 947ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
40s 235ms
And
Go to "TRANSPORT_TABLE"
438ms
When
Go to transport details "CONTAINER"
4s 937ms
And
Expand advice panel
259ms
And
Edit advice in transport details
16s 550ms
And
Fill arrival date field
2s 621ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 497ms
Then
Check advice data in database after edition "CONTAINER"
105ms
After
Hooks.deleteTransportAfterTest()
936ms
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 621ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
034ms
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
31s 519ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
55s 836ms
And
Go to "TRANSPORT_TABLE"
497ms
When
Go to transport details "TRANSPORT_ORDER"
4s 874ms
And
Expand advice panel
250ms
And
Edit advice in transport details
16s 670ms
And
Fill arrival date field
2s 649ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 435ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
093ms
After
Hooks.deleteTransportAfterTest()
1s 028ms