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"
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
55s 047ms
When
Click button advice in transport table "CONTAINER"
089ms
And
Set advice window in schedule
2s 840ms
And
Fill advice form
14s 669ms
And
Click advice save button and wait for advice form to disappear
31s 265ms
And
Go to "TRANSPORT_TABLE"
217ms
And
Go to transport details "CONTAINER"
4s 462ms
Then
Check are advice values equals
2s 320ms
After
Hooks.deleteTransportAfterTest()
154ms
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 287ms
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
1m 571ms
When
Click button advice in transport table "OWN_COLLECTION"
114ms
And
Set advice window in schedule
2s 664ms
And
Fill advice form
14s 652ms
And
Click advice save button and wait for advice form to disappear
30s 709ms
And
Go to "TRANSPORT_TABLE"
208ms
And
Go to transport details "OWN_COLLECTION"
4s 478ms
Then
Check are advice values equals
2s 277ms
After
Hooks.deleteTransportAfterTest()
174ms
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 309ms
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"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 864ms
When
Click button advice in transport table "TRANSPORT_ORDER"
087ms
And
Set advice window in schedule
2s 651ms
And
Fill advice form
14s 668ms
And
Click advice save button and wait for advice form to disappear
30s 715ms
And
Go to "TRANSPORT_TABLE"
226ms
And
Go to transport details "TRANSPORT_ORDER"
4s 464ms
Then
Check are advice values equals
2s 343ms
After
Hooks.deleteTransportAfterTest()
133ms
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 323ms
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 461ms
When
Click button advice in transport table "OWN_COLLECTION"
069ms
And
Set advice window in schedule
2s 679ms
And
Fill advice form
14s 614ms
And
Click advice save button and wait for advice form to disappear
30s 784ms
And
Go to "TRANSPORT_TABLE"
200ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 219ms
After
Hooks.deleteTransportAfterTest()
155ms
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 627ms
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 372ms
When
Click button advice in transport table "CONTAINER"
099ms
And
Set advice window in schedule
2s 612ms
And
Fill advice form
14s 702ms
And
Click advice save button and wait for advice form to disappear
30s 727ms
And
Go to "TRANSPORT_TABLE"
195ms
Then
Check advice data in SK API database "CONTAINER"
3s 122ms
After
Hooks.deleteTransportAfterTest()
158ms
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 268ms
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 281ms
When
Click button advice in transport table "TRANSPORT_ORDER"
085ms
And
Set advice window in schedule
2s 637ms
And
Fill advice form
14s 690ms
And
Click advice save button and wait for advice form to disappear
30s 713ms
And
Go to "TRANSPORT_TABLE"
234ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 037ms
After
Hooks.deleteTransportAfterTest()
218ms
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 298ms
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 949ms
When
Click button advice in transport table "CONTAINER"
079ms
And
Set advice window in schedule in the past
2s 675ms
And
Fill advice form
14s 654ms
And
Click advice save button to check error message
092ms
Then
Check if possible advice alert is displayed
019ms
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 269ms
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
42s 561ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 197ms
And
Go to "TRANSPORT_TABLE"
216ms
When
Go to transport details "OWN_COLLECTION"
4s 440ms
And
Expand advice panel
116ms
And
Edit advice in transport details
13s 995ms
And
Fill arrival date field
2s 273ms
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"
032ms
After
Hooks.deleteTransportAfterTest()
155ms
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 429ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
001ms
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 987ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 142ms
And
Go to "TRANSPORT_TABLE"
215ms
When
Go to transport details "CONTAINER"
4s 509ms
And
Expand advice panel
107ms
And
Edit advice in transport details
13s 998ms
And
Fill arrival date field
2s 262ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 631ms
Then
Check advice data in database after edition "CONTAINER"
033ms
After
Hooks.deleteTransportAfterTest()
148ms
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 435ms
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"
005ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
30s 965ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 090ms
And
Go to "TRANSPORT_TABLE"
247ms
When
Go to transport details "TRANSPORT_ORDER"
4s 464ms
And
Expand advice panel
099ms
And
Edit advice in transport details
13s 977ms
And
Fill arrival date field
2s 291ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 597ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
029ms
After
Hooks.deleteTransportAfterTest()
122ms