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 775ms
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
52s 016ms
When
Click button advice in transport table "CONTAINER"
225ms
And
Set advice window in schedule
3s 548ms
And
Fill advice form
17s 885ms
And
Click advice save button and wait for advice form to disappear
33s 221ms
And
Go to "TRANSPORT_TABLE"
445ms
And
Go to transport details "CONTAINER"
4s 931ms
Then
Check are advice values equals
2s 897ms
After
Hooks.deleteTransportAfterTest()
850ms
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 700ms
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"
034ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
55s 295ms
When
Click button advice in transport table "OWN_COLLECTION"
233ms
And
Set advice window in schedule
3s 538ms
And
Fill advice form
17s 877ms
And
Click advice save button and wait for advice form to disappear
33s 282ms
And
Go to "TRANSPORT_TABLE"
457ms
And
Go to transport details "OWN_COLLECTION"
4s 969ms
Then
Check are advice values equals
2s 915ms
After
Hooks.deleteTransportAfterTest()
886ms
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 759ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id
51s 684ms
When
Click button advice in transport table "TRANSPORT_ORDER"
247ms
And
Set advice window in schedule
3s 508ms
And
Fill advice form
17s 912ms
And
Click advice save button and wait for advice form to disappear
33s 246ms
And
Go to "TRANSPORT_TABLE"
452ms
And
Go to transport details "TRANSPORT_ORDER"
4s 918ms
Then
Check are advice values equals
2s 936ms
After
Hooks.deleteTransportAfterTest()
1s 005ms
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 781ms
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 "CREATE_ADVICE" "super-admin-skz"
035ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
52s 300ms
When
Click button advice in transport table "OWN_COLLECTION"
232ms
And
Set advice window in schedule
3s 729ms
And
Fill advice form
17s 882ms
And
Click advice save button and wait for advice form to disappear
33s 314ms
And
Go to "TRANSPORT_TABLE"
442ms
Then
Check advice data in SK API database "OWN_COLLECTION"
458ms
After
Hooks.deleteTransportAfterTest()
999ms
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 685ms
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"
038ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 1s 004ms
When
Click button advice in transport table "CONTAINER"
226ms
And
Set advice window in schedule
3s 545ms
And
Fill advice form
17s 911ms
And
Click advice save button and wait for advice form to disappear
33s 378ms
And
Go to "TRANSPORT_TABLE"
445ms
Then
Check advice data in SK API database "CONTAINER"
242ms
After
Hooks.deleteTransportAfterTest()
1s 005ms
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 786ms
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
58s 567ms
When
Click button advice in transport table "TRANSPORT_ORDER"
245ms
And
Set advice window in schedule
3s 594ms
And
Fill advice form
17s 960ms
And
Click advice save button and wait for advice form to disappear
33s 340ms
And
Go to "TRANSPORT_TABLE"
463ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
092ms
After
Hooks.deleteTransportAfterTest()
1s 018ms
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 760ms
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 039ms
When
Click button advice in transport table "CONTAINER"
235ms
And
Set advice window in schedule in the past
3s 510ms
And
Fill advice form
17s 885ms
And
Click advice save button to check error message
169ms
Then
Check if possible advice alert is displayed
064ms
After
Hooks.deleteTransportAfterTest()
625ms
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 546ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
037ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
035ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
34s 108ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
54s 940ms
And
Go to "TRANSPORT_TABLE"
426ms
When
Go to transport details "OWN_COLLECTION"
4s 856ms
And
Expand advice panel
262ms
And
Edit advice in transport details
16s 715ms
And
Fill arrival date field
2s 572ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 428ms
Then
Check advice data in database after edition "OWN_COLLECTION"
102ms
After
Hooks.deleteTransportAfterTest()
944ms
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 721ms
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"
036ms
And
Check is transport "CONTAINER" created in transport table and set transport id
18s 984ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
54s 899ms
And
Go to "TRANSPORT_TABLE"
460ms
When
Go to transport details "CONTAINER"
4s 947ms
And
Expand advice panel
269ms
And
Edit advice in transport details
16s 664ms
And
Fill arrival date field
2s 543ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 427ms
Then
Check advice data in database after edition "CONTAINER"
098ms
After
Hooks.deleteTransportAfterTest()
915ms
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 779ms
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 "EDIT_ADVICE" "super-admin-skz"
036ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
19s 455ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
55s 117ms
And
Go to "TRANSPORT_TABLE"
517ms
When
Go to transport details "TRANSPORT_ORDER"
4s 936ms
And
Expand advice panel
262ms
And
Edit advice in transport details
16s 586ms
And
Fill arrival date field
2s 562ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 447ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
105ms
After
Hooks.deleteTransportAfterTest()
1s 019ms