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 758ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "CONTAINER" created in transport table and set transport id
55s 016ms
When
Click button advice in transport table "CONTAINER"
227ms
And
Set advice window in schedule
3s 373ms
And
Fill advice form
17s 941ms
And
Click advice save button and wait for advice form to disappear
33s 883ms
And
Go to "TRANSPORT_TABLE"
445ms
And
Go to transport details "CONTAINER"
2s 914ms
Then
Check are advice values equals
2s 931ms
After
Hooks.deleteTransportAfterTest()
1s 070ms
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 670ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
55s 210ms
When
Click button advice in transport table "OWN_COLLECTION"
223ms
And
Set advice window in schedule
3s 373ms
And
Fill advice form
17s 942ms
And
Click advice save button and wait for advice form to disappear
33s 850ms
And
Go to "TRANSPORT_TABLE"
480ms
And
Go to transport details "OWN_COLLECTION"
2s 910ms
Then
Check are advice values equals
2s 936ms
After
Hooks.deleteTransportAfterTest()
1s 104ms
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 734ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
025ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
019ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
51s 713ms
When
Click button advice in transport table "TRANSPORT_ORDER"
201ms
And
Set advice window in schedule
3s 338ms
And
Fill advice form
18s 057ms
And
Click advice save button and wait for advice form to disappear
33s 892ms
And
Go to "TRANSPORT_TABLE"
483ms
And
Go to transport details "TRANSPORT_ORDER"
2s 903ms
Then
Check are advice values equals
2s 903ms
After
Hooks.deleteTransportAfterTest()
1s 029ms
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 639ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
018ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
55s 228ms
When
Click button advice in transport table "OWN_COLLECTION"
228ms
And
Set advice window in schedule
3s 379ms
And
Fill advice form
18s 071ms
And
Click advice save button and wait for advice form to disappear
33s 826ms
And
Go to "TRANSPORT_TABLE"
457ms
Then
Check advice data in SK API database "OWN_COLLECTION"
410ms
After
Hooks.deleteTransportAfterTest()
1s 110ms
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 687ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 1s 020ms
When
Click button advice in transport table "CONTAINER"
235ms
And
Set advice window in schedule
3s 433ms
And
Fill advice form
17s 835ms
And
Click advice save button and wait for advice form to disappear
33s 837ms
And
Go to "TRANSPORT_TABLE"
460ms
Then
Check advice data in SK API database "CONTAINER"
201ms
After
Hooks.deleteTransportAfterTest()
1s 026ms
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 624ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id
58s 535ms
When
Click button advice in transport table "TRANSPORT_ORDER"
240ms
And
Set advice window in schedule
3s 376ms
And
Fill advice form
18s 088ms
And
Click advice save button and wait for advice form to disappear
33s 911ms
And
Go to "TRANSPORT_TABLE"
485ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
094ms
After
Hooks.deleteTransportAfterTest()
1s 087ms
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 706ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
019ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
018ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 1s 031ms
When
Click button advice in transport table "CONTAINER"
241ms
And
Set advice window in schedule in the past
3s 332ms
And
Fill advice form
17s 872ms
And
Click advice save button to check error message
162ms
Then
Check if possible advice alert is displayed
073ms
After
Hooks.deleteTransportAfterTest()
667ms
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 621ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
024ms
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 278ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
55s 329ms
And
Go to "TRANSPORT_TABLE"
456ms
When
Go to transport details "OWN_COLLECTION"
2s 912ms
And
Expand advice panel
305ms
And
Edit advice in transport details
16s 670ms
And
Fill arrival date field
2s 546ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 483ms
Then
Check advice data in database after edition "OWN_COLLECTION"
102ms
After
Hooks.deleteTransportAfterTest()
1s 036ms
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"
020ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
016ms
And
Check is transport "CONTAINER" created in transport table and set transport id
21s 981ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
55s 415ms
And
Go to "TRANSPORT_TABLE"
459ms
When
Go to transport details "CONTAINER"
2s 924ms
And
Expand advice panel
304ms
And
Edit advice in transport details
16s 624ms
And
Fill arrival date field
2s 546ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 451ms
Then
Check advice data in database after edition "CONTAINER"
102ms
After
Hooks.deleteTransportAfterTest()
1s 086ms
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 816ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
016ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
18s 690ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
55s 353ms
And
Go to "TRANSPORT_TABLE"
505ms
When
Go to transport details "TRANSPORT_ORDER"
2s 869ms
And
Expand advice panel
316ms
And
Edit advice in transport details
16s 701ms
And
Fill arrival date field
2s 549ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 476ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
090ms
After
Hooks.deleteTransportAfterTest()
1s 048ms