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 809ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
036ms
And
Add transport by SKApi in "MGW"
025ms
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 023ms
When
Click button advice in transport table "CONTAINER"
237ms
And
Set advice window in schedule
3s 663ms
And
Fill advice form
18s 073ms
And
Click advice save button and wait for advice form to disappear
33s 874ms
And
Go to "TRANSPORT_TABLE"
467ms
And
Go to transport details "CONTAINER"
4s 924ms
Then
Check are advice values equals
2s 916ms
After
Hooks.deleteTransportAfterTest()
925ms
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 756ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
038ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
52s 234ms
When
Click button advice in transport table "OWN_COLLECTION"
224ms
And
Set advice window in schedule
3s 570ms
And
Fill advice form
18s 074ms
And
Click advice save button and wait for advice form to disappear
33s 878ms
And
Go to "TRANSPORT_TABLE"
491ms
And
Go to transport details "OWN_COLLECTION"
4s 902ms
Then
Check are advice values equals
2s 893ms
After
Hooks.deleteTransportAfterTest()
1s 036ms
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 836ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
027ms
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 667ms
When
Click button advice in transport table "TRANSPORT_ORDER"
233ms
And
Set advice window in schedule
3s 537ms
And
Fill advice form
18s 171ms
And
Click advice save button and wait for advice form to disappear
33s 780ms
And
Go to "TRANSPORT_TABLE"
482ms
And
Go to transport details "TRANSPORT_ORDER"
4s 906ms
Then
Check are advice values equals
2s 917ms
After
Hooks.deleteTransportAfterTest()
985ms
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 761ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
020ms
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 237ms
When
Click button advice in transport table "OWN_COLLECTION"
230ms
And
Set advice window in schedule
3s 537ms
And
Fill advice form
18s 100ms
And
Click advice save button and wait for advice form to disappear
33s 788ms
And
Go to "TRANSPORT_TABLE"
449ms
Then
Check advice data in SK API database "OWN_COLLECTION"
456ms
After
Hooks.deleteTransportAfterTest()
1s 022ms
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 768ms
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"
034ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 1s 006ms
When
Click button advice in transport table "CONTAINER"
241ms
And
Set advice window in schedule
3s 495ms
And
Fill advice form
18s 120ms
And
Click advice save button and wait for advice form to disappear
33s 787ms
And
Go to "TRANSPORT_TABLE"
485ms
Then
Check advice data in SK API database "CONTAINER"
248ms
After
Hooks.deleteTransportAfterTest()
1s 011ms
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 739ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id
57s 683ms
When
Click button advice in transport table "TRANSPORT_ORDER"
250ms
And
Set advice window in schedule
3s 451ms
And
Fill advice form
18s 144ms
And
Click advice save button and wait for advice form to disappear
33s 873ms
And
Go to "TRANSPORT_TABLE"
480ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
092ms
After
Hooks.deleteTransportAfterTest()
1s 109ms
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 731ms
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 023ms
When
Click button advice in transport table "CONTAINER"
224ms
And
Set advice window in schedule in the past
3s 633ms
And
Fill advice form
18s 227ms
And
Click advice save button to check error message
191ms
Then
Check if possible advice alert is displayed
078ms
After
Hooks.deleteTransportAfterTest()
804ms
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 760ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
023ms
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 246ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
55s 593ms
And
Go to "TRANSPORT_TABLE"
456ms
When
Go to transport details "OWN_COLLECTION"
4s 874ms
And
Expand advice panel
265ms
And
Edit advice in transport details
16s 780ms
And
Fill arrival date field
2s 618ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 511ms
Then
Check advice data in database after edition "OWN_COLLECTION"
115ms
After
Hooks.deleteTransportAfterTest()
1s 028ms
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 752ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
034ms
And
Check is transport "CONTAINER" created in transport table and set transport id
15s 962ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
55s 786ms
And
Go to "TRANSPORT_TABLE"
444ms
When
Go to transport details "CONTAINER"
4s 914ms
And
Expand advice panel
266ms
And
Edit advice in transport details
16s 568ms
And
Fill arrival date field
2s 600ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 471ms
Then
Check advice data in database after edition "CONTAINER"
108ms
After
Hooks.deleteTransportAfterTest()
1s 107ms
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 952ms
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 683ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
55s 875ms
And
Go to "TRANSPORT_TABLE"
486ms
When
Go to transport details "TRANSPORT_ORDER"
4s 845ms
And
Expand advice panel
266ms
And
Edit advice in transport details
16s 620ms
And
Fill arrival date field
2s 647ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 483ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
098ms
After
Hooks.deleteTransportAfterTest()
1s 110ms