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_CONTAINER" "super-admin-skz"
037ms
And
Add transport by SKApi in "MGW"
026ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "CONTAINER" created in transport table and set transport id
49s 096ms
When
Click button advice in transport table "CONTAINER"
222ms
And
Set advice window in schedule
3s 837ms
And
Fill advice form
17s 987ms
And
Click advice save button and wait for advice form to disappear
33s 193ms
And
Go to "TRANSPORT_TABLE"
436ms
And
Go to transport details "CONTAINER"
4s 904ms
Then
Check are advice values equals
2s 925ms
After
Hooks.deleteTransportAfterTest()
956ms
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 871ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
038ms
And
Add transport by SKApi in "MGW"
021ms
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 339ms
When
Click button advice in transport table "OWN_COLLECTION"
230ms
And
Set advice window in schedule
3s 598ms
And
Fill advice form
17s 983ms
And
Click advice save button and wait for advice form to disappear
33s 799ms
And
Go to "TRANSPORT_TABLE"
463ms
And
Go to transport details "OWN_COLLECTION"
4s 879ms
Then
Check are advice values equals
2s 905ms
After
Hooks.deleteTransportAfterTest()
960ms
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 696ms
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"
037ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
51s 758ms
When
Click button advice in transport table "TRANSPORT_ORDER"
236ms
And
Set advice window in schedule
3s 586ms
And
Fill advice form
17s 969ms
And
Click advice save button and wait for advice form to disappear
33s 767ms
And
Go to "TRANSPORT_TABLE"
486ms
And
Go to transport details "TRANSPORT_ORDER"
4s 883ms
Then
Check are advice values equals
2s 891ms
After
Hooks.deleteTransportAfterTest()
990ms
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 834ms
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"
034ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
52s 332ms
When
Click button advice in transport table "OWN_COLLECTION"
218ms
And
Set advice window in schedule
3s 734ms
And
Fill advice form
17s 826ms
And
Click advice save button and wait for advice form to disappear
33s 191ms
And
Go to "TRANSPORT_TABLE"
406ms
Then
Check advice data in SK API database "OWN_COLLECTION"
529ms
After
Hooks.deleteTransportAfterTest()
949ms
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 599ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
1m 1s 011ms
When
Click button advice in transport table "CONTAINER"
486ms
And
Set advice window in schedule
3s 722ms
And
Fill advice form
18s 681ms
And
Click advice save button and wait for advice form to disappear
33s 884ms
And
Go to "TRANSPORT_TABLE"
477ms
Then
Check advice data in SK API database "CONTAINER"
484ms
After
Hooks.deleteTransportAfterTest()
1s 145ms
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 759ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id
55s 595ms
When
Click button advice in transport table "TRANSPORT_ORDER"
231ms
And
Set advice window in schedule
3s 670ms
And
Fill advice form
18s 066ms
And
Click advice save button and wait for advice form to disappear
18s 325ms
And
Go to "TRANSPORT_TABLE"
465ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
10s 257ms
After
Hooks.deleteTransportAfterTest()
886ms
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 788ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
7s 051ms
When
Click button advice in transport table "CONTAINER"
223ms
And
Set advice window in schedule in the past
3s 582ms
And
Fill advice form
17s 982ms
And
Click advice save button to check error message
157ms
Then
Check if possible advice alert is displayed
066ms
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 589ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
028ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
034ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
34s 416ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
40s 047ms
And
Go to "TRANSPORT_TABLE"
456ms
When
Go to transport details "OWN_COLLECTION"
4s 908ms
And
Expand advice panel
263ms
And
Edit advice in transport details
16s 631ms
And
Fill arrival date field
2s 654ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 457ms
Then
Check advice data in database after edition "OWN_COLLECTION"
076ms
After
Hooks.deleteTransportAfterTest()
1s 110ms
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 718ms
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"
034ms
And
Check is transport "CONTAINER" created in transport table and set transport id
34s 067ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
55s 471ms
And
Go to "TRANSPORT_TABLE"
466ms
When
Go to transport details "CONTAINER"
4s 846ms
And
Expand advice panel
262ms
And
Edit advice in transport details
16s 596ms
And
Fill arrival date field
2s 539ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 491ms
Then
Check advice data in database after edition "CONTAINER"
109ms
After
Hooks.deleteTransportAfterTest()
1s 067ms
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 768ms
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"
035ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
16s 524ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
55s 095ms
And
Go to "TRANSPORT_TABLE"
468ms
When
Go to transport details "TRANSPORT_ORDER"
4s 869ms
And
Expand advice panel
260ms
And
Edit advice in transport details
16s 614ms
And
Fill arrival date field
2s 569ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 436ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
109ms
After
Hooks.deleteTransportAfterTest()
1s 050ms