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 555ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
019ms
And
Add transport by SKApi in "MGW"
021ms
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 906ms
When
Click button advice in transport table "CONTAINER"
246ms
And
Set advice window in schedule
3s 414ms
And
Fill advice form
17s 703ms
And
Click advice save button and wait for advice form to disappear
33s 283ms
And
Go to "TRANSPORT_TABLE"
418ms
And
Go to transport details "CONTAINER"
2s 898ms
Then
Check are advice values equals
2s 926ms
After
Hooks.deleteTransportAfterTest()
841ms
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 794ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
7s 220ms
When
Click button advice in transport table "OWN_COLLECTION"
247ms
And
Set advice window in schedule
3s 311ms
And
Fill advice form
17s 565ms
And
Click advice save button and wait for advice form to disappear
33s 197ms
And
Go to "TRANSPORT_TABLE"
408ms
And
Go to transport details "OWN_COLLECTION"
2s 906ms
Then
Check are advice values equals
2s 865ms
After
Hooks.deleteTransportAfterTest()
762ms
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 746ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
024ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
014ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 642ms
When
Click button advice in transport table "TRANSPORT_ORDER"
223ms
And
Set advice window in schedule
3s 578ms
And
Fill advice form
17s 699ms
And
Click advice save button and wait for advice form to disappear
33s 286ms
And
Go to "TRANSPORT_TABLE"
471ms
And
Go to transport details "TRANSPORT_ORDER"
2s 916ms
Then
Check are advice values equals
2s 914ms
After
Hooks.deleteTransportAfterTest()
1s 062ms
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 810ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
017ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 140ms
When
Click button advice in transport table "OWN_COLLECTION"
221ms
And
Set advice window in schedule
3s 311ms
And
Fill advice form
17s 876ms
And
Click advice save button and wait for advice form to disappear
33s 223ms
And
Go to "TRANSPORT_TABLE"
392ms
Then
Check advice data in SK API database "OWN_COLLECTION"
429ms
After
Hooks.deleteTransportAfterTest()
952ms
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 659ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
027ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
014ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 969ms
When
Click button advice in transport table "CONTAINER"
225ms
And
Set advice window in schedule
3s 311ms
And
Fill advice form
17s 717ms
And
Click advice save button and wait for advice form to disappear
33s 258ms
And
Go to "TRANSPORT_TABLE"
405ms
Then
Check advice data in SK API database "CONTAINER"
188ms
After
Hooks.deleteTransportAfterTest()
969ms
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 770ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
019ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
015ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 664ms
When
Click button advice in transport table "TRANSPORT_ORDER"
245ms
And
Set advice window in schedule
3s 443ms
And
Fill advice form
17s 653ms
And
Click advice save button and wait for advice form to disappear
33s 159ms
And
Go to "TRANSPORT_TABLE"
521ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
118ms
After
Hooks.deleteTransportAfterTest()
1s 011ms
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 661ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
019ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
015ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 913ms
When
Click button advice in transport table "CONTAINER"
227ms
And
Set advice window in schedule in the past
3s 327ms
And
Fill advice form
17s 710ms
And
Click advice save button to check error message
190ms
Then
Check if possible advice alert is displayed
067ms
After
Hooks.deleteTransportAfterTest()
680ms
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 733ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW"
020ms
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
4s 088ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
54s 475ms
And
Go to "TRANSPORT_TABLE"
448ms
When
Go to transport details "OWN_COLLECTION"
3s
And
Expand advice panel
228ms
And
Edit advice in transport details
16s 264ms
And
Fill arrival date field
2s 559ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 244ms
Then
Check advice data in database after edition "OWN_COLLECTION"
089ms
After
Hooks.deleteTransportAfterTest()
818ms
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 725ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
020ms
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 958ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
54s 560ms
And
Go to "TRANSPORT_TABLE"
457ms
When
Go to transport details "CONTAINER"
2s 933ms
And
Expand advice panel
370ms
And
Edit advice in transport details
16s 289ms
And
Fill arrival date field
2s 586ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 206ms
Then
Check advice data in database after edition "CONTAINER"
080ms
After
Hooks.deleteTransportAfterTest()
697ms
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 660ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
016ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
017ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
9s 661ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
54s 550ms
And
Go to "TRANSPORT_TABLE"
498ms
When
Go to transport details "TRANSPORT_ORDER"
3s 153ms
And
Expand advice panel
351ms
And
Edit advice in transport details
16s 474ms
And
Fill arrival date field
2s 571ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 215ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
081ms
After
Hooks.deleteTransportAfterTest()
839ms