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 776ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
027ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
059ms
And
Check is transport "CONTAINER" created in transport table and set transport id
52s 014ms
When
Click button advice in transport table "CONTAINER"
232ms
And
Set advice window in schedule
3s 565ms
And
Fill advice form
18s 310ms
And
Click advice save button and wait for advice form to disappear
33s 303ms
And
Go to "TRANSPORT_TABLE"
560ms
And
Go to transport details "CONTAINER"
4s 959ms
Then
Check are advice values equals
2s 840ms
After
Hooks.deleteTransportAfterTest()
929ms
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 713ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
52s 234ms
When
Click button advice in transport table "OWN_COLLECTION"
223ms
And
Set advice window in schedule
3s 560ms
And
Fill advice form
18s 211ms
And
Click advice save button and wait for advice form to disappear
33s 380ms
And
Go to "TRANSPORT_TABLE"
469ms
And
Go to transport details "OWN_COLLECTION"
4s 915ms
Then
Check are advice values equals
2s 832ms
After
Hooks.deleteTransportAfterTest()
946ms
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 823ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
024ms
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 669ms
When
Click button advice in transport table "TRANSPORT_ORDER"
238ms
And
Set advice window in schedule
3s 556ms
And
Fill advice form
18s 203ms
And
Click advice save button and wait for advice form to disappear
33s 227ms
And
Go to "TRANSPORT_TABLE"
446ms
And
Go to transport details "TRANSPORT_ORDER"
4s 898ms
Then
Check are advice values equals
2s 864ms
After
Hooks.deleteTransportAfterTest()
853ms
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 719ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
020ms
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
52s 221ms
When
Click button advice in transport table "OWN_COLLECTION"
236ms
And
Set advice window in schedule
3s 501ms
And
Fill advice form
18s 200ms
And
Click advice save button and wait for advice form to disappear
33s 270ms
And
Go to "TRANSPORT_TABLE"
415ms
Then
Check advice data in SK API database "OWN_COLLECTION"
416ms
After
Hooks.deleteTransportAfterTest()
1s 066ms
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 802ms
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 037ms
When
Click button advice in transport table "CONTAINER"
228ms
And
Set advice window in schedule
3s 523ms
And
Fill advice form
18s 154ms
And
Click advice save button and wait for advice form to disappear
33s 290ms
And
Go to "TRANSPORT_TABLE"
414ms
Then
Check advice data in SK API database "CONTAINER"
237ms
After
Hooks.deleteTransportAfterTest()
977ms
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 663ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id
1m 666ms
When
Click button advice in transport table "TRANSPORT_ORDER"
239ms
And
Set advice window in schedule
3s 770ms
And
Fill advice form
18s 208ms
And
Click advice save button and wait for advice form to disappear
18s 339ms
And
Go to "TRANSPORT_TABLE"
494ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
10s 239ms
After
Hooks.deleteTransportAfterTest()
892ms
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 647ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
035ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 932ms
When
Click button advice in transport table "CONTAINER"
238ms
And
Set advice window in schedule in the past
3s 498ms
And
Fill advice form
18s 225ms
And
Click advice save button to check error message
203ms
Then
Check if possible advice alert is displayed
063ms
After
Hooks.deleteTransportAfterTest()
616ms
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 710ms
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 "EDIT_ADVICE" "super-admin-skz"
033ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
34s 218ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
55s 637ms
And
Go to "TRANSPORT_TABLE"
392ms
When
Go to transport details "OWN_COLLECTION"
4s 874ms
And
Expand advice panel
262ms
And
Edit advice in transport details
16s 681ms
And
Fill arrival date field
2s 614ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 467ms
Then
Check advice data in database after edition "OWN_COLLECTION"
097ms
After
Hooks.deleteTransportAfterTest()
969ms
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 806ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
033ms
And
Add transport by SKApi in "MGW"
026ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
033ms
And
Check is transport "CONTAINER" created in transport table and set transport id
19s 002ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
55s 398ms
And
Go to "TRANSPORT_TABLE"
450ms
When
Go to transport details "CONTAINER"
4s 912ms
And
Expand advice panel
252ms
And
Edit advice in transport details
16s 642ms
And
Fill arrival date field
2s 633ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 538ms
Then
Check advice data in database after edition "CONTAINER"
099ms
After
Hooks.deleteTransportAfterTest()
930ms
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"
034ms
And
Add transport by SKApi in "MGW"
024ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
035ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
18s 632ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
40s 458ms
And
Go to "TRANSPORT_TABLE"
458ms
When
Go to transport details "TRANSPORT_ORDER"
4s 906ms
And
Expand advice panel
268ms
And
Edit advice in transport details
16s 345ms
And
Fill arrival date field
2s 591ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 466ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
104ms
After
Hooks.deleteTransportAfterTest()
927ms