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 298ms
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
54s 405ms
When
Click button advice in transport table "CONTAINER"
138ms
And
Set advice window in schedule
2s 914ms
And
Fill advice form
14s 857ms
And
Click advice save button and wait for advice form to disappear
31s 315ms
And
Go to "TRANSPORT_TABLE"
150ms
And
Go to transport details "CONTAINER"
4s 487ms
Then
Check are advice values equals
2s 340ms
After
Hooks.deleteTransportAfterTest()
146ms
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 237ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
001ms
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
1m 506ms
When
Click button advice in transport table "OWN_COLLECTION"
118ms
And
Set advice window in schedule
2s 564ms
And
Fill advice form
14s 725ms
And
Click advice save button and wait for advice form to disappear
30s 742ms
And
Go to "TRANSPORT_TABLE"
187ms
And
Go to transport details "OWN_COLLECTION"
4s 482ms
Then
Check are advice values equals
2s 311ms
After
Hooks.deleteTransportAfterTest()
147ms
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 238ms
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"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 235ms
When
Click button advice in transport table "TRANSPORT_ORDER"
126ms
And
Set advice window in schedule
2s 511ms
And
Fill advice form
14s 791ms
And
Click advice save button and wait for advice form to disappear
30s 744ms
And
Go to "TRANSPORT_TABLE"
222ms
And
Go to transport details "TRANSPORT_ORDER"
4s 457ms
Then
Check are advice values equals
2s 323ms
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 340ms
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 367ms
When
Click button advice in transport table "OWN_COLLECTION"
106ms
And
Set advice window in schedule
2s 525ms
And
Fill advice form
14s 770ms
And
Click advice save button and wait for advice form to disappear
30s 684ms
And
Go to "TRANSPORT_TABLE"
181ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 167ms
After
Hooks.deleteTransportAfterTest()
136ms
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 257ms
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 309ms
When
Click button advice in transport table "CONTAINER"
132ms
And
Set advice window in schedule
2s 517ms
And
Fill advice form
14s 811ms
And
Click advice save button and wait for advice form to disappear
30s 715ms
And
Go to "TRANSPORT_TABLE"
182ms
Then
Check advice data in SK API database "CONTAINER"
3s 109ms
After
Hooks.deleteTransportAfterTest()
118ms
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 214ms
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 802ms
When
Click button advice in transport table "TRANSPORT_ORDER"
106ms
And
Set advice window in schedule
2s 525ms
And
Fill advice form
14s 815ms
And
Click advice save button and wait for advice form to disappear
30s 719ms
And
Go to "TRANSPORT_TABLE"
201ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 041ms
After
Hooks.deleteTransportAfterTest()
136ms
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 196ms
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 311ms
When
Click button advice in transport table "CONTAINER"
127ms
And
Set advice window in schedule in the past
2s 545ms
And
Fill advice form
14s 787ms
And
Click advice save button to check error message
113ms
Then
Check if possible advice alert is displayed
029ms
After
Hooks.deleteTransportAfterTest()
111ms
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 239ms
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 458ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 276ms
And
Go to "TRANSPORT_TABLE"
185ms
When
Go to transport details "OWN_COLLECTION"
4s 489ms
And
Expand advice panel
122ms
And
Edit advice in transport details
14s 100ms
And
Fill arrival date field
2s 313ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 139ms
Then
Check advice data in database after edition "OWN_COLLECTION"
039ms
After
Hooks.deleteTransportAfterTest()
162ms
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 229ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
009ms
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 388ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 285ms
And
Go to "TRANSPORT_TABLE"
179ms
When
Go to transport details "CONTAINER"
4s 513ms
And
Expand advice panel
119ms
And
Edit advice in transport details
14s 091ms
And
Fill arrival date field
2s 298ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 142ms
Then
Check advice data in database after edition "CONTAINER"
030ms
After
Hooks.deleteTransportAfterTest()
130ms
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 230ms
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
31s 011ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 249ms
And
Go to "TRANSPORT_TABLE"
239ms
When
Go to transport details "TRANSPORT_ORDER"
4s 489ms
And
Expand advice panel
100ms
And
Edit advice in transport details
14s 078ms
And
Fill arrival date field
2s 300ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 668ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
032ms
After
Hooks.deleteTransportAfterTest()
131ms