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 278ms
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"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
51s 484ms
When
Click button advice in transport table "CONTAINER"
087ms
And
Set advice window in schedule
2s 675ms
And
Fill advice form
14s 582ms
And
Click advice save button and wait for advice form to disappear
30s 701ms
And
Go to "TRANSPORT_TABLE"
190ms
And
Go to transport details "CONTAINER"
4s 471ms
Then
Check are advice values equals
2s 340ms
After
Hooks.deleteTransportAfterTest()
166ms
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 241ms
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 453ms
When
Click button advice in transport table "OWN_COLLECTION"
068ms
And
Set advice window in schedule
2s 657ms
And
Fill advice form
14s 587ms
And
Click advice save button and wait for advice form to disappear
30s 696ms
And
Go to "TRANSPORT_TABLE"
190ms
And
Go to transport details "OWN_COLLECTION"
4s 449ms
Then
Check are advice values equals
2s 320ms
After
Hooks.deleteTransportAfterTest()
160ms
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 316ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
004ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 879ms
When
Click button advice in transport table "TRANSPORT_ORDER"
076ms
And
Set advice window in schedule
2s 653ms
And
Fill advice form
14s 697ms
And
Click advice save button and wait for advice form to disappear
30s 730ms
And
Go to "TRANSPORT_TABLE"
191ms
And
Go to transport details "TRANSPORT_ORDER"
4s 441ms
Then
Check are advice values equals
2s 315ms
After
Hooks.deleteTransportAfterTest()
162ms
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 352ms
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"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
4s 051ms
When
Click button advice in transport table "OWN_COLLECTION"
089ms
And
Set advice window in schedule
2s 654ms
And
Fill advice form
14s 708ms
And
Click advice save button and wait for advice form to disappear
30s 756ms
And
Go to "TRANSPORT_TABLE"
160ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 228ms
After
Hooks.deleteTransportAfterTest()
144ms
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 259ms
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"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 961ms
When
Click button advice in transport table "CONTAINER"
073ms
And
Set advice window in schedule
2s 659ms
And
Fill advice form
14s 628ms
And
Click advice save button and wait for advice form to disappear
30s 694ms
And
Go to "TRANSPORT_TABLE"
161ms
Then
Check advice data in SK API database "CONTAINER"
3s 114ms
After
Hooks.deleteTransportAfterTest()
151ms
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 242ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
002ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
003ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 950ms
When
Click button advice in transport table "TRANSPORT_ORDER"
081ms
And
Set advice window in schedule
2s 615ms
And
Fill advice form
14s 584ms
And
Click advice save button and wait for advice form to disappear
30s 757ms
And
Go to "TRANSPORT_TABLE"
213ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 038ms
After
Hooks.deleteTransportAfterTest()
167ms
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 234ms
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 975ms
When
Click button advice in transport table "CONTAINER"
077ms
And
Set advice window in schedule in the past
2s 697ms
And
Fill advice form
14s 577ms
And
Click advice save button to check error message
094ms
Then
Check if possible advice alert is displayed
015ms
After
Hooks.deleteTransportAfterTest()
116ms
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 252ms
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 "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
43s 152ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 124ms
And
Go to "TRANSPORT_TABLE"
215ms
When
Go to transport details "OWN_COLLECTION"
4s 459ms
And
Expand advice panel
098ms
And
Edit advice in transport details
13s 931ms
And
Fill arrival date field
2s 312ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 622ms
Then
Check advice data in database after edition "OWN_COLLECTION"
034ms
After
Hooks.deleteTransportAfterTest()
149ms
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 212ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
002ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
33s 468ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 219ms
And
Go to "TRANSPORT_TABLE"
216ms
When
Go to transport details "CONTAINER"
4s 473ms
And
Expand advice panel
106ms
And
Edit advice in transport details
14s
And
Fill arrival date field
2s 276ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 652ms
Then
Check advice data in database after edition "CONTAINER"
024ms
After
Hooks.deleteTransportAfterTest()
107ms
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 249ms
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"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 418ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 032ms
And
Go to "TRANSPORT_TABLE"
242ms
When
Go to transport details "TRANSPORT_ORDER"
4s 433ms
And
Expand advice panel
113ms
And
Edit advice in transport details
14s 035ms
And
Fill arrival date field
2s 281ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 181ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
037ms
After
Hooks.deleteTransportAfterTest()
114ms