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 714ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
026ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
035ms
And
Check is transport "CONTAINER" created in transport table and set transport id
52s 039ms
When
Click button advice in transport table "CONTAINER"
226ms
And
Set advice window in schedule
3s 667ms
And
Fill advice form
17s 861ms
And
Click advice save button and wait for advice form to disappear
33s 159ms
And
Go to "TRANSPORT_TABLE"
431ms
And
Go to transport details "CONTAINER"
4s 894ms
Then
Check are advice values equals
2s 912ms
After
Hooks.deleteTransportAfterTest()
851ms
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 670ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
038ms
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 240ms
When
Click button advice in transport table "OWN_COLLECTION"
233ms
And
Set advice window in schedule
3s 536ms
And
Fill advice form
17s 930ms
And
Click advice save button and wait for advice form to disappear
33s 834ms
And
Go to "TRANSPORT_TABLE"
444ms
And
Go to transport details "OWN_COLLECTION"
4s 886ms
Then
Check are advice values equals
2s 911ms
After
Hooks.deleteTransportAfterTest()
890ms
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 665ms
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 "CREATE_ADVICE" "super-admin-skz"
035ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
51s 663ms
When
Click button advice in transport table "TRANSPORT_ORDER"
233ms
And
Set advice window in schedule
3s 538ms
And
Fill advice form
17s 944ms
And
Click advice save button and wait for advice form to disappear
18s 274ms
And
Go to "TRANSPORT_TABLE"
472ms
And
Go to transport details "TRANSPORT_ORDER"
4s 913ms
Then
Check are advice values equals
2s 943ms
After
Hooks.deleteTransportAfterTest()
940ms
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 562ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
018ms
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
10s 100ms
When
Click button advice in transport table "OWN_COLLECTION"
223ms
And
Set advice window in schedule
3s 526ms
And
Fill advice form
17s 883ms
And
Click advice save button and wait for advice form to disappear
33s 321ms
And
Go to "TRANSPORT_TABLE"
463ms
Then
Check advice data in SK API database "OWN_COLLECTION"
423ms
After
Hooks.deleteTransportAfterTest()
1s 051ms
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 753ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
58s 045ms
When
Click button advice in transport table "CONTAINER"
223ms
And
Set advice window in schedule
3s 546ms
And
Fill advice form
18s 001ms
And
Click advice save button and wait for advice form to disappear
33s 196ms
And
Go to "TRANSPORT_TABLE"
431ms
Then
Check advice data in SK API database "CONTAINER"
203ms
After
Hooks.deleteTransportAfterTest()
918ms
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 753ms
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"
034ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
1m 703ms
When
Click button advice in transport table "TRANSPORT_ORDER"
234ms
And
Set advice window in schedule
3s 480ms
And
Fill advice form
17s 984ms
And
Click advice save button and wait for advice form to disappear
33s 202ms
And
Go to "TRANSPORT_TABLE"
486ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
093ms
After
Hooks.deleteTransportAfterTest()
945ms
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 719ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
1m 1s 032ms
When
Click button advice in transport table "CONTAINER"
230ms
And
Set advice window in schedule in the past
3s 646ms
And
Fill advice form
17s 941ms
And
Click advice save button to check error message
170ms
Then
Check if possible advice alert is displayed
060ms
After
Hooks.deleteTransportAfterTest()
606ms
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 699ms
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 "EDIT_ADVICE" "super-admin-skz"
034ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
34s 226ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
54s 968ms
And
Go to "TRANSPORT_TABLE"
451ms
When
Go to transport details "OWN_COLLECTION"
4s 934ms
And
Expand advice panel
261ms
And
Edit advice in transport details
16s 591ms
And
Fill arrival date field
2s 552ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 422ms
Then
Check advice data in database after edition "OWN_COLLECTION"
103ms
After
Hooks.deleteTransportAfterTest()
1s 030ms
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 687ms
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"
034ms
And
Check is transport "CONTAINER" created in transport table and set transport id
18s 957ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
54s 904ms
And
Go to "TRANSPORT_TABLE"
437ms
When
Go to transport details "CONTAINER"
4s 981ms
And
Expand advice panel
260ms
And
Edit advice in transport details
16s 545ms
And
Fill arrival date field
2s 542ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 462ms
Then
Check advice data in database after edition "CONTAINER"
104ms
After
Hooks.deleteTransportAfterTest()
1s 013ms
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 756ms
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 "EDIT_ADVICE" "super-admin-skz"
034ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
18s 653ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
55s 150ms
And
Go to "TRANSPORT_TABLE"
469ms
When
Go to transport details "TRANSPORT_ORDER"
4s 896ms
And
Expand advice panel
266ms
And
Edit advice in transport details
16s 614ms
And
Fill arrival date field
2s 534ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 445ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
105ms
After
Hooks.deleteTransportAfterTest()
1s 057ms