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 614ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
018ms
And
Check is transport "CONTAINER" created in transport table and set transport id
54s 961ms
When
Click button advice in transport table "CONTAINER"
216ms
And
Set advice window in schedule
3s 316ms
And
Fill advice form
17s 970ms
And
Click advice save button and wait for advice form to disappear
33s 868ms
And
Go to "TRANSPORT_TABLE"
444ms
And
Go to transport details "CONTAINER"
2s 929ms
Then
Check are advice values equals
2s 901ms
After
Hooks.deleteTransportAfterTest()
973ms
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 751ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
019ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
52s 222ms
When
Click button advice in transport table "OWN_COLLECTION"
246ms
And
Set advice window in schedule
3s 377ms
And
Fill advice form
18s 053ms
And
Click advice save button and wait for advice form to disappear
33s 844ms
And
Go to "TRANSPORT_TABLE"
399ms
And
Go to transport details "OWN_COLLECTION"
2s 808ms
Then
Check are advice values equals
2s 820ms
After
Hooks.deleteTransportAfterTest()
1s 097ms
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 709ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
023ms
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
54s 736ms
When
Click button advice in transport table "TRANSPORT_ORDER"
246ms
And
Set advice window in schedule
3s 397ms
And
Fill advice form
17s 998ms
And
Click advice save button and wait for advice form to disappear
33s 840ms
And
Go to "TRANSPORT_TABLE"
455ms
And
Go to transport details "TRANSPORT_ORDER"
2s 850ms
Then
Check are advice values equals
2s 888ms
After
Hooks.deleteTransportAfterTest()
1s 096ms
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 743ms
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"
016ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
55s 254ms
When
Click button advice in transport table "OWN_COLLECTION"
240ms
And
Set advice window in schedule
3s 459ms
And
Fill advice form
17s 935ms
And
Click advice save button and wait for advice form to disappear
33s 835ms
And
Go to "TRANSPORT_TABLE"
437ms
Then
Check advice data in SK API database "OWN_COLLECTION"
413ms
After
Hooks.deleteTransportAfterTest()
996ms
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 736ms
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
1m 1s 060ms
When
Click button advice in transport table "CONTAINER"
218ms
And
Set advice window in schedule
3s 332ms
And
Fill advice form
17s 931ms
And
Click advice save button and wait for advice form to disappear
33s 832ms
And
Go to "TRANSPORT_TABLE"
462ms
Then
Check advice data in SK API database "CONTAINER"
208ms
After
Hooks.deleteTransportAfterTest()
1s 088ms
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 723ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
018ms
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
58s 510ms
When
Click button advice in transport table "TRANSPORT_ORDER"
240ms
And
Set advice window in schedule
3s 344ms
And
Fill advice form
18s 170ms
And
Click advice save button and wait for advice form to disappear
33s 846ms
And
Go to "TRANSPORT_TABLE"
488ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
093ms
After
Hooks.deleteTransportAfterTest()
1s 081ms
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 612ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
017ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 1s 019ms
When
Click button advice in transport table "CONTAINER"
225ms
And
Set advice window in schedule in the past
3s 303ms
And
Fill advice form
18s 030ms
And
Click advice save button to check error message
191ms
Then
Check if possible advice alert is displayed
068ms
After
Hooks.deleteTransportAfterTest()
787ms
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 676ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
022ms
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
34s 228ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
55s 507ms
And
Go to "TRANSPORT_TABLE"
478ms
When
Go to transport details "OWN_COLLECTION"
2s 885ms
And
Expand advice panel
291ms
And
Edit advice in transport details
16s 679ms
And
Fill arrival date field
2s 593ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 416ms
Then
Check advice data in database after edition "OWN_COLLECTION"
108ms
After
Hooks.deleteTransportAfterTest()
1s 068ms
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 679ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
017ms
And
Check is transport "CONTAINER" created in transport table and set transport id
22s 012ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
55s 564ms
And
Go to "TRANSPORT_TABLE"
459ms
When
Go to transport details "CONTAINER"
2s 926ms
And
Expand advice panel
264ms
And
Edit advice in transport details
16s 763ms
And
Fill arrival date field
2s 601ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 431ms
Then
Check advice data in database after edition "CONTAINER"
092ms
After
Hooks.deleteTransportAfterTest()
1s 137ms
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_TRANSPORT_ORDER" "super-admin-skz"
019ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
018ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
18s 671ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
55s 496ms
And
Go to "TRANSPORT_TABLE"
500ms
When
Go to transport details "TRANSPORT_ORDER"
2s 907ms
And
Expand advice panel
303ms
And
Edit advice in transport details
16s 613ms
And
Fill arrival date field
2s 558ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 458ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
107ms
After
Hooks.deleteTransportAfterTest()
1s 027ms