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 263ms
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 447ms
When
Click button advice in transport table "CONTAINER"
093ms
And
Set advice window in schedule
2s 922ms
And
Fill advice form
14s 684ms
And
Click advice save button and wait for advice form to disappear
34s 401ms
And
Go to "TRANSPORT_TABLE"
172ms
And
Go to transport details "CONTAINER"
4s 478ms
Then
Check are advice values equals
2s 331ms
After
Hooks.deleteTransportAfterTest()
223ms
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 223ms
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
1m 565ms
When
Click button advice in transport table "OWN_COLLECTION"
092ms
And
Set advice window in schedule
2s 645ms
And
Fill advice form
14s 599ms
And
Click advice save button and wait for advice form to disappear
30s 738ms
And
Go to "TRANSPORT_TABLE"
196ms
And
Go to transport details "OWN_COLLECTION"
4s 429ms
Then
Check are advice values equals
2s 315ms
After
Hooks.deleteTransportAfterTest()
132ms
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 284ms
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
3s 277ms
When
Click button advice in transport table "TRANSPORT_ORDER"
076ms
And
Set advice window in schedule
2s 615ms
And
Fill advice form
14s 678ms
And
Click advice save button and wait for advice form to disappear
33s 912ms
And
Go to "TRANSPORT_TABLE"
211ms
And
Go to transport details "TRANSPORT_ORDER"
4s 483ms
Then
Check are advice values equals
2s 312ms
After
Hooks.deleteTransportAfterTest()
137ms
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 267ms
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
1m 547ms
When
Click button advice in transport table "OWN_COLLECTION"
080ms
And
Set advice window in schedule
2s 636ms
And
Fill advice form
14s 676ms
And
Click advice save button and wait for advice form to disappear
30s 698ms
And
Go to "TRANSPORT_TABLE"
205ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 175ms
After
Hooks.deleteTransportAfterTest()
128ms
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 276ms
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 342ms
When
Click button advice in transport table "CONTAINER"
079ms
And
Set advice window in schedule
2s 576ms
And
Fill advice form
14s 644ms
And
Click advice save button and wait for advice form to disappear
34s 413ms
And
Go to "TRANSPORT_TABLE"
185ms
Then
Check advice data in SK API database "CONTAINER"
100ms
After
Hooks.deleteTransportAfterTest()
114ms
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 337ms
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 845ms
When
Click button advice in transport table "TRANSPORT_ORDER"
066ms
And
Set advice window in schedule
2s 640ms
And
Fill advice form
14s 582ms
And
Click advice save button and wait for advice form to disappear
30s 707ms
And
Go to "TRANSPORT_TABLE"
271ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 038ms
After
Hooks.deleteTransportAfterTest()
179ms
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 222ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
001ms
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 911ms
When
Click button advice in transport table "CONTAINER"
086ms
And
Set advice window in schedule in the past
2s 655ms
And
Fill advice form
17s 849ms
And
Click advice save button to check error message
093ms
Then
Check if possible advice alert is displayed
023ms
After
Hooks.deleteTransportAfterTest()
122ms
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 264ms
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"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
39s 564ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 648ms
And
Go to "TRANSPORT_TABLE"
190ms
When
Go to transport details "OWN_COLLECTION"
4s 449ms
And
Expand advice panel
111ms
And
Edit advice in transport details
14s 001ms
And
Fill arrival date field
2s 275ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 587ms
Then
Check advice data in database after edition "OWN_COLLECTION"
034ms
After
Hooks.deleteTransportAfterTest()
176ms
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 278ms
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 444ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 212ms
And
Go to "TRANSPORT_TABLE"
195ms
When
Go to transport details "CONTAINER"
4s 503ms
And
Expand advice panel
116ms
And
Edit advice in transport details
14s 012ms
And
Fill arrival date field
2s 294ms
And
Click "save-transport-and-close" save button and wait for form to disappear
670ms
Then
Check advice data in database after edition "CONTAINER"
039ms
After
Hooks.deleteTransportAfterTest()
133ms
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 236ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
001ms
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
48s 389ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
51s 247ms
And
Go to "TRANSPORT_TABLE"
241ms
When
Go to transport details "TRANSPORT_ORDER"
4s 398ms
And
Expand advice panel
114ms
And
Edit advice in transport details
14s 043ms
And
Fill arrival date field
2s 277ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 171ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
036ms
After
Hooks.deleteTransportAfterTest()
203ms