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 778ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
022ms
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 043ms
When
Click button advice in transport table "CONTAINER"
212ms
And
Set advice window in schedule
3s 648ms
And
Fill advice form
18s 314ms
And
Click advice save button and wait for advice form to disappear
33s 190ms
And
Go to "TRANSPORT_TABLE"
398ms
And
Go to transport details "CONTAINER"
4s 985ms
Then
Check are advice values equals
2s 896ms
After
Hooks.deleteTransportAfterTest()
944ms
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 749ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
067ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
52s 240ms
When
Click button advice in transport table "OWN_COLLECTION"
228ms
And
Set advice window in schedule
3s 544ms
And
Fill advice form
18s 240ms
And
Click advice save button and wait for advice form to disappear
33s 855ms
And
Go to "TRANSPORT_TABLE"
398ms
And
Go to transport details "OWN_COLLECTION"
4s 911ms
Then
Check are advice values equals
2s 898ms
After
Hooks.deleteTransportAfterTest()
881ms
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 849ms
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 "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
51s 675ms
When
Click button advice in transport table "TRANSPORT_ORDER"
239ms
And
Set advice window in schedule
3s 489ms
And
Fill advice form
18s 285ms
And
Click advice save button and wait for advice form to disappear
33s 797ms
And
Go to "TRANSPORT_TABLE"
473ms
And
Go to transport details "TRANSPORT_ORDER"
4s 994ms
Then
Check are advice values equals
2s 868ms
After
Hooks.deleteTransportAfterTest()
916ms
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 660ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
52s 249ms
When
Click button advice in transport table "OWN_COLLECTION"
231ms
And
Set advice window in schedule
3s 522ms
And
Fill advice form
18s 235ms
And
Click advice save button and wait for advice form to disappear
33s 744ms
And
Go to "TRANSPORT_TABLE"
405ms
Then
Check advice data in SK API database "OWN_COLLECTION"
401ms
After
Hooks.deleteTransportAfterTest()
911ms
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 876ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 1s 020ms
When
Click button advice in transport table "CONTAINER"
223ms
And
Set advice window in schedule
3s 538ms
And
Fill advice form
18s 369ms
And
Click advice save button and wait for advice form to disappear
33s 835ms
And
Go to "TRANSPORT_TABLE"
428ms
Then
Check advice data in SK API database "CONTAINER"
203ms
After
Hooks.deleteTransportAfterTest()
1s 127ms
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_TRANSPORT_ORDER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
019ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
58s 626ms
When
Click button advice in transport table "TRANSPORT_ORDER"
255ms
And
Set advice window in schedule
3s 678ms
And
Fill advice form
18s 576ms
And
Click advice save button and wait for advice form to disappear
18s 395ms
And
Go to "TRANSPORT_TABLE"
497ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
9s 234ms
After
Hooks.deleteTransportAfterTest()
962ms
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 693ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
043ms
And
Add transport by SKApi in "MGW"
019ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 882ms
When
Click button advice in transport table "CONTAINER"
232ms
And
Set advice window in schedule in the past
3s 634ms
And
Fill advice form
18s 314ms
And
Click advice save button to check error message
179ms
Then
Check if possible advice alert is displayed
065ms
After
Hooks.deleteTransportAfterTest()
724ms
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 592ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
024ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
033ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
34s 174ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
55s 538ms
And
Go to "TRANSPORT_TABLE"
467ms
When
Go to transport details "OWN_COLLECTION"
4s 888ms
And
Expand advice panel
261ms
And
Edit advice in transport details
16s 802ms
And
Fill arrival date field
2s 670ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 477ms
Then
Check advice data in database after edition "OWN_COLLECTION"
096ms
After
Hooks.deleteTransportAfterTest()
934ms
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 681ms
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"
033ms
And
Check is transport "CONTAINER" created in transport table and set transport id
16s 010ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
55s 859ms
And
Go to "TRANSPORT_TABLE"
381ms
When
Go to transport details "CONTAINER"
4s 968ms
And
Expand advice panel
277ms
And
Edit advice in transport details
16s 782ms
And
Fill arrival date field
2s 647ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 503ms
Then
Check advice data in database after edition "CONTAINER"
108ms
After
Hooks.deleteTransportAfterTest()
929ms
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 695ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
033ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
18s 622ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
56s 190ms
And
Go to "TRANSPORT_TABLE"
401ms
When
Go to transport details "TRANSPORT_ORDER"
4s 868ms
And
Expand advice panel
259ms
And
Edit advice in transport details
16s 630ms
And
Fill arrival date field
2s 625ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 576ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
100ms
After
Hooks.deleteTransportAfterTest()
1s 065ms