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 590ms
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 436ms
When
Click button advice in transport table "CONTAINER"
097ms
And
Set advice window in schedule
2s 761ms
And
Fill advice form
14s 853ms
And
Click advice save button and wait for advice form to disappear
31s 289ms
And
Go to "TRANSPORT_TABLE"
196ms
And
Go to transport details "CONTAINER"
4s 520ms
Then
Check are advice values equals
2s 341ms
After
Hooks.deleteTransportAfterTest()
167ms
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 277ms
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 376ms
When
Click button advice in transport table "OWN_COLLECTION"
129ms
And
Set advice window in schedule
2s 596ms
And
Fill advice form
14s 758ms
And
Click advice save button and wait for advice form to disappear
30s 716ms
And
Go to "TRANSPORT_TABLE"
173ms
And
Go to transport details "OWN_COLLECTION"
4s 466ms
Then
Check are advice values equals
2s 341ms
After
Hooks.deleteTransportAfterTest()
144ms
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 247ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
003ms
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
1s 141ms
When
Click button advice in transport table "TRANSPORT_ORDER"
117ms
And
Set advice window in schedule
2s 528ms
And
Fill advice form
14s 793ms
And
Click advice save button and wait for advice form to disappear
30s 684ms
And
Go to "TRANSPORT_TABLE"
232ms
And
Go to transport details "TRANSPORT_ORDER"
4s 513ms
Then
Check are advice values equals
2s 343ms
After
Hooks.deleteTransportAfterTest()
119ms
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 294ms
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 377ms
When
Click button advice in transport table "OWN_COLLECTION"
131ms
And
Set advice window in schedule
2s 488ms
And
Fill advice form
14s 765ms
And
Click advice save button and wait for advice form to disappear
30s 770ms
And
Go to "TRANSPORT_TABLE"
157ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 166ms
After
Hooks.deleteTransportAfterTest()
149ms
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 251ms
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 313ms
When
Click button advice in transport table "CONTAINER"
132ms
And
Set advice window in schedule
2s 492ms
And
Fill advice form
14s 718ms
And
Click advice save button and wait for advice form to disappear
30s 739ms
And
Go to "TRANSPORT_TABLE"
166ms
Then
Check advice data in SK API database "CONTAINER"
3s 100ms
After
Hooks.deleteTransportAfterTest()
120ms
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 199ms
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
6s 827ms
When
Click button advice in transport table "TRANSPORT_ORDER"
107ms
And
Set advice window in schedule
2s 511ms
And
Fill advice form
14s 814ms
And
Click advice save button and wait for advice form to disappear
30s 766ms
And
Go to "TRANSPORT_TABLE"
211ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 048ms
After
Hooks.deleteTransportAfterTest()
122ms
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 280ms
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 317ms
When
Click button advice in transport table "CONTAINER"
107ms
And
Set advice window in schedule in the past
2s 557ms
And
Fill advice form
14s 782ms
And
Click advice save button to check error message
086ms
Then
Check if possible advice alert is displayed
023ms
After
Hooks.deleteTransportAfterTest()
117ms
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 256ms
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
42s 488ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 787ms
And
Go to "TRANSPORT_TABLE"
182ms
When
Go to transport details "OWN_COLLECTION"
4s 498ms
And
Expand advice panel
110ms
And
Edit advice in transport details
14s 114ms
And
Fill arrival date field
2s 283ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 584ms
Then
Check advice data in database after edition "OWN_COLLECTION"
032ms
After
Hooks.deleteTransportAfterTest()
140ms
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_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
33s 393ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 294ms
And
Go to "TRANSPORT_TABLE"
167ms
When
Go to transport details "CONTAINER"
4s 496ms
And
Expand advice panel
113ms
And
Edit advice in transport details
14s 122ms
And
Fill arrival date field
2s 286ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 168ms
Then
Check advice data in database after edition "CONTAINER"
044ms
After
Hooks.deleteTransportAfterTest()
145ms
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 272ms
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
30s 866ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 319ms
And
Go to "TRANSPORT_TABLE"
236ms
When
Go to transport details "TRANSPORT_ORDER"
4s 469ms
And
Expand advice panel
109ms
And
Edit advice in transport details
14s 107ms
And
Fill arrival date field
2s 304ms
And
Click "save-transport-and-close" save button and wait for form to disappear
667ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
033ms
After
Hooks.deleteTransportAfterTest()
106ms