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 269ms
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
54s 380ms
When
Click button advice in transport table "CONTAINER"
117ms
And
Set advice window in schedule
2s 596ms
And
Fill advice form
14s 815ms
And
Click advice save button and wait for advice form to disappear
30s 698ms
And
Go to "TRANSPORT_TABLE"
201ms
And
Go to transport details "CONTAINER"
4s 503ms
Then
Check are advice values equals
2s 321ms
After
Hooks.deleteTransportAfterTest()
150ms
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 234ms
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"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 359ms
When
Click button advice in transport table "OWN_COLLECTION"
113ms
And
Set advice window in schedule
2s 574ms
And
Fill advice form
14s 763ms
And
Click advice save button and wait for advice form to disappear
30s 732ms
And
Go to "TRANSPORT_TABLE"
188ms
And
Go to transport details "OWN_COLLECTION"
4s 494ms
Then
Check are advice values equals
2s 328ms
After
Hooks.deleteTransportAfterTest()
121ms
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 174ms
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"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 222ms
When
Click button advice in transport table "TRANSPORT_ORDER"
107ms
And
Set advice window in schedule
2s 545ms
And
Fill advice form
14s 865ms
And
Click advice save button and wait for advice form to disappear
30s 708ms
And
Go to "TRANSPORT_TABLE"
217ms
And
Go to transport details "TRANSPORT_ORDER"
4s 467ms
Then
Check are advice values equals
2s 325ms
After
Hooks.deleteTransportAfterTest()
126ms
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 241ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
3s 391ms
When
Click button advice in transport table "OWN_COLLECTION"
118ms
And
Set advice window in schedule
2s 517ms
And
Fill advice form
14s 806ms
And
Click advice save button and wait for advice form to disappear
30s 690ms
And
Go to "TRANSPORT_TABLE"
180ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 161ms
After
Hooks.deleteTransportAfterTest()
142ms
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 218ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
005ms
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 327ms
When
Click button advice in transport table "CONTAINER"
132ms
And
Set advice window in schedule
2s 538ms
And
Fill advice form
14s 809ms
And
Click advice save button and wait for advice form to disappear
30s 755ms
And
Go to "TRANSPORT_TABLE"
179ms
Then
Check advice data in SK API database "CONTAINER"
4s 132ms
After
Hooks.deleteTransportAfterTest()
132ms
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 227ms
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"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 212ms
When
Click button advice in transport table "TRANSPORT_ORDER"
132ms
And
Set advice window in schedule
2s 493ms
And
Fill advice form
14s 753ms
And
Click advice save button and wait for advice form to disappear
30s 794ms
And
Go to "TRANSPORT_TABLE"
200ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 046ms
After
Hooks.deleteTransportAfterTest()
128ms
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 247ms
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 334ms
When
Click button advice in transport table "CONTAINER"
116ms
And
Set advice window in schedule in the past
2s 511ms
And
Fill advice form
14s 843ms
And
Click advice save button to check error message
101ms
Then
Check if possible advice alert is displayed
020ms
After
Hooks.deleteTransportAfterTest()
120ms
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 238ms
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 456ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 330ms
And
Go to "TRANSPORT_TABLE"
191ms
When
Go to transport details "OWN_COLLECTION"
4s 485ms
And
Expand advice panel
122ms
And
Edit advice in transport details
14s 080ms
And
Fill arrival date field
2s 313ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 688ms
Then
Check advice data in database after edition "OWN_COLLECTION"
037ms
After
Hooks.deleteTransportAfterTest()
152ms
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 270ms
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"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
33s 395ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 289ms
And
Go to "TRANSPORT_TABLE"
163ms
When
Go to transport details "CONTAINER"
4s 517ms
And
Expand advice panel
124ms
And
Edit advice in transport details
14s 148ms
And
Fill arrival date field
2s 286ms
And
Click "save-transport-and-close" save button and wait for form to disappear
668ms
Then
Check advice data in database after edition "CONTAINER"
032ms
After
Hooks.deleteTransportAfterTest()
125ms
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 221ms
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 "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
48s 307ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 167ms
And
Go to "TRANSPORT_TABLE"
227ms
When
Go to transport details "TRANSPORT_ORDER"
4s 462ms
And
Expand advice panel
111ms
And
Edit advice in transport details
14s 136ms
And
Fill arrival date field
2s 307ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 645ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
028ms
After
Hooks.deleteTransportAfterTest()
149ms