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 818ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
49s 121ms
When
Click button advice in transport table "CONTAINER"
234ms
And
Set advice window in schedule
3s 636ms
And
Fill advice form
18s 124ms
And
Click advice save button and wait for advice form to disappear
33s 836ms
And
Go to "TRANSPORT_TABLE"
446ms
And
Go to transport details "CONTAINER"
4s 911ms
Then
Check are advice values equals
2s 896ms
After
Hooks.deleteTransportAfterTest()
982ms
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 733ms
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
52s 348ms
When
Click button advice in transport table "OWN_COLLECTION"
240ms
And
Set advice window in schedule
3s 577ms
And
Fill advice form
18s 040ms
And
Click advice save button and wait for advice form to disappear
33s 244ms
And
Go to "TRANSPORT_TABLE"
435ms
And
Go to transport details "OWN_COLLECTION"
4s 894ms
Then
Check are advice values equals
2s 878ms
After
Hooks.deleteTransportAfterTest()
982ms
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 903ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
023ms
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 792ms
When
Click button advice in transport table "TRANSPORT_ORDER"
245ms
And
Set advice window in schedule
3s 596ms
And
Fill advice form
17s 951ms
And
Click advice save button and wait for advice form to disappear
33s 756ms
And
Go to "TRANSPORT_TABLE"
497ms
And
Go to transport details "TRANSPORT_ORDER"
4s 919ms
Then
Check are advice values equals
2s 925ms
After
Hooks.deleteTransportAfterTest()
970ms
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 925ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
036ms
And
Add transport by SKApi in "MGW"
020ms
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 280ms
When
Click button advice in transport table "OWN_COLLECTION"
229ms
And
Set advice window in schedule
3s 650ms
And
Fill advice form
18s 116ms
And
Click advice save button and wait for advice form to disappear
33s 285ms
And
Go to "TRANSPORT_TABLE"
430ms
Then
Check advice data in SK API database "OWN_COLLECTION"
457ms
After
Hooks.deleteTransportAfterTest()
958ms
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 870ms
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"
035ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 1s 077ms
When
Click button advice in transport table "CONTAINER"
210ms
And
Set advice window in schedule
3s 630ms
And
Fill advice form
18s 073ms
And
Click advice save button and wait for advice form to disappear
33s 193ms
And
Go to "TRANSPORT_TABLE"
453ms
Then
Check advice data in SK API database "CONTAINER"
252ms
After
Hooks.deleteTransportAfterTest()
1s 066ms
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 864ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
036ms
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
1m 800ms
When
Click button advice in transport table "TRANSPORT_ORDER"
237ms
And
Set advice window in schedule
3s 834ms
And
Fill advice form
17s 992ms
And
Click advice save button and wait for advice form to disappear
33s 245ms
And
Go to "TRANSPORT_TABLE"
563ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
094ms
After
Hooks.deleteTransportAfterTest()
1s 061ms
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 789ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
043ms
And
Add transport by SKApi in "MGW"
022ms
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 103ms
When
Click button advice in transport table "CONTAINER"
229ms
And
Set advice window in schedule in the past
3s 717ms
And
Fill advice form
18s 013ms
And
Click advice save button to check error message
165ms
Then
Check if possible advice alert is displayed
063ms
After
Hooks.deleteTransportAfterTest()
670ms
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 723ms
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 "EDIT_ADVICE" "super-admin-skz"
034ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
34s 256ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
55s 050ms
And
Go to "TRANSPORT_TABLE"
431ms
When
Go to transport details "OWN_COLLECTION"
4s 907ms
And
Expand advice panel
267ms
And
Edit advice in transport details
16s 488ms
And
Fill arrival date field
2s 580ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 424ms
Then
Check advice data in database after edition "OWN_COLLECTION"
106ms
After
Hooks.deleteTransportAfterTest()
959ms
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 825ms
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
16s 051ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
55s 063ms
And
Go to "TRANSPORT_TABLE"
438ms
When
Go to transport details "CONTAINER"
4s 933ms
And
Expand advice panel
255ms
And
Edit advice in transport details
16s 626ms
And
Fill arrival date field
2s 605ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 416ms
Then
Check advice data in database after edition "CONTAINER"
102ms
After
Hooks.deleteTransportAfterTest()
1s 058ms
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 849ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id
18s 741ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
55s 538ms
And
Go to "TRANSPORT_TABLE"
486ms
When
Go to transport details "TRANSPORT_ORDER"
4s 889ms
And
Expand advice panel
269ms
And
Edit advice in transport details
16s 546ms
And
Fill arrival date field
2s 543ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 428ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
100ms
After
Hooks.deleteTransportAfterTest()
1s 044ms