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 519ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
024ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 903ms
When
Click button advice in transport table "CONTAINER"
225ms
And
Set advice window in schedule
3s 378ms
And
Fill advice form
17s 965ms
And
Click advice save button and wait for advice form to disappear
33s 301ms
And
Go to "TRANSPORT_TABLE"
410ms
And
Go to transport details "CONTAINER"
2s 883ms
Then
Check are advice values equals
2s 878ms
After
Hooks.deleteTransportAfterTest()
908ms
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_OWN_COLLECTION" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
025ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
018ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 104ms
When
Click button advice in transport table "OWN_COLLECTION"
244ms
And
Set advice window in schedule
3s 297ms
And
Fill advice form
17s 952ms
And
Click advice save button and wait for advice form to disappear
33s 271ms
And
Go to "TRANSPORT_TABLE"
390ms
And
Go to transport details "OWN_COLLECTION"
2s 888ms
Then
Check are advice values equals
2s 840ms
After
Hooks.deleteTransportAfterTest()
957ms
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 890ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
025ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
018ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 629ms
When
Click button advice in transport table "TRANSPORT_ORDER"
239ms
And
Set advice window in schedule
3s 381ms
And
Fill advice form
17s 982ms
And
Click advice save button and wait for advice form to disappear
33s 340ms
And
Go to "TRANSPORT_TABLE"
465ms
And
Go to transport details "TRANSPORT_ORDER"
2s 861ms
Then
Check are advice values equals
2s 903ms
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 846ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
024ms
And
Add transport by SKApi in "MGW"
019ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
015ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
4s 081ms
When
Click button advice in transport table "OWN_COLLECTION"
233ms
And
Set advice window in schedule
3s 323ms
And
Fill advice form
18s 061ms
And
Click advice save button and wait for advice form to disappear
33s 292ms
And
Go to "TRANSPORT_TABLE"
416ms
Then
Check advice data in SK API database "OWN_COLLECTION"
402ms
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 803ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
018ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 924ms
When
Click button advice in transport table "CONTAINER"
233ms
And
Set advice window in schedule
3s 480ms
And
Fill advice form
18s 087ms
And
Click advice save button and wait for advice form to disappear
33s 349ms
And
Go to "TRANSPORT_TABLE"
415ms
Then
Check advice data in SK API database "CONTAINER"
241ms
After
Hooks.deleteTransportAfterTest()
891ms
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 858ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
4s 417ms
When
Click button advice in transport table "TRANSPORT_ORDER"
213ms
And
Set advice window in schedule
3s 363ms
And
Fill advice form
18s 042ms
And
Click advice save button and wait for advice form to disappear
33s 314ms
And
Go to "TRANSPORT_TABLE"
465ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
082ms
After
Hooks.deleteTransportAfterTest()
865ms
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 524ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
025ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
017ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 923ms
When
Click button advice in transport table "CONTAINER"
225ms
And
Set advice window in schedule in the past
3s 340ms
And
Fill advice form
17s 944ms
And
Click advice save button to check error message
177ms
Then
Check if possible advice alert is displayed
076ms
After
Hooks.deleteTransportAfterTest()
595ms
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 732ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
017ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
4s 117ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
54s 722ms
And
Go to "TRANSPORT_TABLE"
401ms
When
Go to transport details "OWN_COLLECTION"
2s 815ms
And
Expand advice panel
293ms
And
Edit advice in transport details
16s 558ms
And
Fill arrival date field
2s 600ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 219ms
Then
Check advice data in database after edition "OWN_COLLECTION"
109ms
After
Hooks.deleteTransportAfterTest()
907ms
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 711ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
017ms
And
Add transport by SKApi in "MGW"
024ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
018ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 889ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
54s 859ms
And
Go to "TRANSPORT_TABLE"
408ms
When
Go to transport details "CONTAINER"
2s 859ms
And
Expand advice panel
298ms
And
Edit advice in transport details
16s 560ms
And
Fill arrival date field
2s 642ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 285ms
Then
Check advice data in database after edition "CONTAINER"
103ms
After
Hooks.deleteTransportAfterTest()
827ms
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 881ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
019ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
016ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 604ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
39s 870ms
And
Go to "TRANSPORT_TABLE"
442ms
When
Go to transport details "TRANSPORT_ORDER"
2s 891ms
And
Expand advice panel
301ms
And
Edit advice in transport details
16s 580ms
And
Fill arrival date field
2s 621ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 226ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
106ms
After
Hooks.deleteTransportAfterTest()
912ms