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 217ms
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 414ms
When
Click button advice in transport table "CONTAINER"
115ms
And
Set advice window in schedule
2s 722ms
And
Fill advice form
14s 903ms
And
Click advice save button and wait for advice form to disappear
30s 720ms
And
Go to "TRANSPORT_TABLE"
173ms
And
Go to transport details "CONTAINER"
4s 528ms
Then
Check are advice values equals
2s 354ms
After
Hooks.deleteTransportAfterTest()
137ms
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 290ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
008ms
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 405ms
When
Click button advice in transport table "OWN_COLLECTION"
132ms
And
Set advice window in schedule
2s 522ms
And
Fill advice form
14s 758ms
And
Click advice save button and wait for advice form to disappear
30s 743ms
And
Go to "TRANSPORT_TABLE"
191ms
And
Go to transport details "OWN_COLLECTION"
4s 493ms
Then
Check are advice values equals
2s 316ms
After
Hooks.deleteTransportAfterTest()
160ms
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 232ms
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 259ms
When
Click button advice in transport table "TRANSPORT_ORDER"
114ms
And
Set advice window in schedule
2s 533ms
And
Fill advice form
14s 773ms
And
Click advice save button and wait for advice form to disappear
30s 718ms
And
Go to "TRANSPORT_TABLE"
230ms
And
Go to transport details "TRANSPORT_ORDER"
4s 494ms
Then
Check are advice values equals
2s 335ms
After
Hooks.deleteTransportAfterTest()
150ms
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 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"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 383ms
When
Click button advice in transport table "OWN_COLLECTION"
107ms
And
Set advice window in schedule
2s 537ms
And
Fill advice form
14s 719ms
And
Click advice save button and wait for advice form to disappear
30s 729ms
And
Go to "TRANSPORT_TABLE"
189ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 186ms
After
Hooks.deleteTransportAfterTest()
111ms
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 236ms
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 332ms
When
Click button advice in transport table "CONTAINER"
121ms
And
Set advice window in schedule
2s 526ms
And
Fill advice form
14s 804ms
And
Click advice save button and wait for advice form to disappear
30s 733ms
And
Go to "TRANSPORT_TABLE"
206ms
Then
Check advice data in SK API database "CONTAINER"
4s 113ms
After
Hooks.deleteTransportAfterTest()
127ms
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 211ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id
6s 227ms
When
Click button advice in transport table "TRANSPORT_ORDER"
126ms
And
Set advice window in schedule
2s 557ms
And
Fill advice form
14s 818ms
And
Click advice save button and wait for advice form to disappear
30s 806ms
And
Go to "TRANSPORT_TABLE"
227ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 042ms
After
Hooks.deleteTransportAfterTest()
132ms
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 204ms
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 365ms
When
Click button advice in transport table "CONTAINER"
102ms
And
Set advice window in schedule in the past
2s 581ms
And
Fill advice form
14s 828ms
And
Click advice save button to check error message
097ms
Then
Check if possible advice alert is displayed
020ms
After
Hooks.deleteTransportAfterTest()
108ms
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_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 498ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 288ms
And
Go to "TRANSPORT_TABLE"
195ms
When
Go to transport details "OWN_COLLECTION"
4s 481ms
And
Expand advice panel
111ms
And
Edit advice in transport details
14s 157ms
And
Fill arrival date field
2s 291ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 625ms
Then
Check advice data in database after edition "OWN_COLLECTION"
035ms
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 250ms
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 411ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 231ms
And
Go to "TRANSPORT_TABLE"
217ms
When
Go to transport details "CONTAINER"
4s 522ms
And
Expand advice panel
116ms
And
Edit advice in transport details
14s 121ms
And
Fill arrival date field
2s 288ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 602ms
Then
Check advice data in database after edition "CONTAINER"
041ms
After
Hooks.deleteTransportAfterTest()
154ms
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 266ms
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"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 332ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 246ms
And
Go to "TRANSPORT_TABLE"
251ms
When
Go to transport details "TRANSPORT_ORDER"
4s 482ms
And
Expand advice panel
108ms
And
Edit advice in transport details
14s 090ms
And
Fill arrival date field
2s 293ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 639ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
038ms
After
Hooks.deleteTransportAfterTest()
172ms