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 685ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
026ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "CONTAINER" created in transport table and set transport id
12s 926ms
When
Click button advice in transport table "CONTAINER"
218ms
And
Set advice window in schedule
3s 403ms
And
Fill advice form
17s 857ms
And
Click advice save button and wait for advice form to disappear
33s 793ms
And
Go to "TRANSPORT_TABLE"
413ms
And
Go to transport details "CONTAINER"
2s 908ms
Then
Check are advice values equals
2s 923ms
After
Hooks.deleteTransportAfterTest()
878ms
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 869ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
018ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
4s 160ms
When
Click button advice in transport table "OWN_COLLECTION"
232ms
And
Set advice window in schedule
3s 292ms
And
Fill advice form
17s 846ms
And
Click advice save button and wait for advice form to disappear
33s 333ms
And
Go to "TRANSPORT_TABLE"
447ms
And
Go to transport details "OWN_COLLECTION"
2s 897ms
Then
Check are advice values equals
2s 857ms
After
Hooks.deleteTransportAfterTest()
897ms
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 807ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
025ms
And
Add transport by SKApi in "MGW"
029ms
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 418ms
When
Click button advice in transport table "TRANSPORT_ORDER"
234ms
And
Set advice window in schedule
3s 342ms
And
Fill advice form
17s 713ms
And
Click advice save button and wait for advice form to disappear
33s 339ms
And
Go to "TRANSPORT_TABLE"
455ms
And
Go to transport details "TRANSPORT_ORDER"
2s 931ms
Then
Check are advice values equals
2s 876ms
After
Hooks.deleteTransportAfterTest()
905ms
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 729ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
026ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
22s 170ms
When
Click button advice in transport table "OWN_COLLECTION"
218ms
And
Set advice window in schedule
3s 406ms
And
Fill advice form
17s 692ms
And
Click advice save button and wait for advice form to disappear
33s 283ms
And
Go to "TRANSPORT_TABLE"
445ms
Then
Check advice data in SK API database "OWN_COLLECTION"
394ms
After
Hooks.deleteTransportAfterTest()
922ms
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 854ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
017ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 983ms
When
Click button advice in transport table "CONTAINER"
237ms
And
Set advice window in schedule
3s 395ms
And
Fill advice form
17s 802ms
And
Click advice save button and wait for advice form to disappear
33s 253ms
And
Go to "TRANSPORT_TABLE"
428ms
Then
Check advice data in SK API database "CONTAINER"
248ms
After
Hooks.deleteTransportAfterTest()
845ms
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 817ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW"
019ms
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
6s 653ms
When
Click button advice in transport table "TRANSPORT_ORDER"
237ms
And
Set advice window in schedule
3s 308ms
And
Fill advice form
17s 881ms
And
Click advice save button and wait for advice form to disappear
33s 295ms
And
Go to "TRANSPORT_TABLE"
466ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
088ms
After
Hooks.deleteTransportAfterTest()
887ms
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 784ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
014ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 955ms
When
Click button advice in transport table "CONTAINER"
252ms
And
Set advice window in schedule in the past
3s 312ms
And
Fill advice form
17s 783ms
And
Click advice save button to check error message
177ms
Then
Check if possible advice alert is displayed
066ms
After
Hooks.deleteTransportAfterTest()
619ms
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 716ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
024ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
015ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
10s 135ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
54s 543ms
And
Go to "TRANSPORT_TABLE"
421ms
When
Go to transport details "OWN_COLLECTION"
2s 968ms
And
Expand advice panel
250ms
And
Edit advice in transport details
16s 401ms
And
Fill arrival date field
2s 600ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 240ms
Then
Check advice data in database after edition "OWN_COLLECTION"
084ms
After
Hooks.deleteTransportAfterTest()
895ms
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 786ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
014ms
And
Check is transport "CONTAINER" created in transport table and set transport id
19s 019ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
54s 713ms
And
Go to "TRANSPORT_TABLE"
416ms
When
Go to transport details "CONTAINER"
2s 922ms
And
Expand advice panel
355ms
And
Edit advice in transport details
16s 427ms
And
Fill arrival date field
2s 576ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 190ms
Then
Check advice data in database after edition "CONTAINER"
092ms
After
Hooks.deleteTransportAfterTest()
856ms
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 801ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
017ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
015ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 665ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
54s 775ms
And
Go to "TRANSPORT_TABLE"
510ms
When
Go to transport details "TRANSPORT_ORDER"
2s 953ms
And
Expand advice panel
375ms
And
Edit advice in transport details
16s 454ms
And
Fill arrival date field
2s 593ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 199ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
095ms
After
Hooks.deleteTransportAfterTest()
892ms