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"
1s 195ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
54s 413ms
When
Click button advice in transport table "CONTAINER"
121ms
And
Set advice window in schedule
2s 628ms
And
Fill advice form
14s 893ms
And
Click advice save button and wait for advice form to disappear
30s 682ms
And
Go to "TRANSPORT_TABLE"
168ms
And
Go to transport details "CONTAINER"
4s 509ms
Then
Check are advice values equals
2s 337ms
After
Hooks.deleteTransportAfterTest()
118ms
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"
1s 276ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 381ms
When
Click button advice in transport table "OWN_COLLECTION"
129ms
And
Set advice window in schedule
2s 568ms
And
Fill advice form
14s 730ms
And
Click advice save button and wait for advice form to disappear
30s 737ms
And
Go to "TRANSPORT_TABLE"
176ms
And
Go to transport details "OWN_COLLECTION"
4s 450ms
Then
Check are advice values equals
2s 339ms
After
Hooks.deleteTransportAfterTest()
095ms
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"
1s 334ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
1s 142ms
When
Click button advice in transport table "TRANSPORT_ORDER"
127ms
And
Set advice window in schedule
2s 554ms
And
Fill advice form
14s 757ms
And
Click advice save button and wait for advice form to disappear
30s 794ms
And
Go to "TRANSPORT_TABLE"
225ms
And
Go to transport details "TRANSPORT_ORDER"
4s 513ms
Then
Check are advice values equals
2s 330ms
After
Hooks.deleteTransportAfterTest()
147ms
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"
1s 225ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
002ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 397ms
When
Click button advice in transport table "OWN_COLLECTION"
129ms
And
Set advice window in schedule
2s 531ms
And
Fill advice form
14s 728ms
And
Click advice save button and wait for advice form to disappear
30s 705ms
And
Go to "TRANSPORT_TABLE"
171ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 189ms
After
Hooks.deleteTransportAfterTest()
134ms
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"
1s 205ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
002ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 322ms
When
Click button advice in transport table "CONTAINER"
127ms
And
Set advice window in schedule
2s 569ms
And
Fill advice form
14s 783ms
And
Click advice save button and wait for advice form to disappear
30s 795ms
And
Go to "TRANSPORT_TABLE"
185ms
Then
Check advice data in SK API database "CONTAINER"
3s 101ms
After
Hooks.deleteTransportAfterTest()
098ms
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"
1s 270ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 829ms
When
Click button advice in transport table "TRANSPORT_ORDER"
109ms
And
Set advice window in schedule
2s 535ms
And
Fill advice form
14s 781ms
And
Click advice save button and wait for advice form to disappear
15s 776ms
And
Go to "TRANSPORT_TABLE"
188ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
18s 096ms
After
Hooks.deleteTransportAfterTest()
127ms
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"
1s 298ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 896ms
When
Click button advice in transport table "CONTAINER"
130ms
And
Set advice window in schedule in the past
2s 593ms
And
Fill advice form
14s 850ms
And
Click advice save button to check error message
108ms
Then
Check if possible advice alert is displayed
026ms
After
Hooks.deleteTransportAfterTest()
119ms
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"
1s 273ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
003ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
42s 495ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 266ms
And
Go to "TRANSPORT_TABLE"
184ms
When
Go to transport details "OWN_COLLECTION"
4s 496ms
And
Expand advice panel
116ms
And
Edit advice in transport details
14s 072ms
And
Fill arrival date field
2s 293ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 655ms
Then
Check advice data in database after edition "OWN_COLLECTION"
039ms
After
Hooks.deleteTransportAfterTest()
158ms
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"
1s 306ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
007ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
33s 411ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 249ms
And
Go to "TRANSPORT_TABLE"
176ms
When
Go to transport details "CONTAINER"
4s 491ms
And
Expand advice panel
125ms
And
Edit advice in transport details
14s 103ms
And
Fill arrival date field
2s 284ms
And
Click "save-transport-and-close" save button and wait for form to disappear
673ms
Then
Check advice data in database after edition "CONTAINER"
034ms
After
Hooks.deleteTransportAfterTest()
112ms
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"
1s 233ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
003ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
48s 326ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 271ms
And
Go to "TRANSPORT_TABLE"
228ms
When
Go to transport details "TRANSPORT_ORDER"
4s 510ms
And
Expand advice panel
114ms
And
Edit advice in transport details
14s 127ms
And
Fill arrival date field
2s 299ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 149ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
041ms
After
Hooks.deleteTransportAfterTest()
133ms