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 264ms
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"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
54s 429ms
When
Click button advice in transport table "CONTAINER"
130ms
And
Set advice window in schedule
2s 615ms
And
Fill advice form
14s 728ms
And
Click advice save button and wait for advice form to disappear
30s 745ms
And
Go to "TRANSPORT_TABLE"
155ms
And
Go to transport details "CONTAINER"
4s 481ms
Then
Check are advice values equals
2s 331ms
After
Hooks.deleteTransportAfterTest()
176ms
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 244ms
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 381ms
When
Click button advice in transport table "OWN_COLLECTION"
141ms
And
Set advice window in schedule
2s 657ms
And
Fill advice form
14s 616ms
And
Click advice save button and wait for advice form to disappear
30s 782ms
And
Go to "TRANSPORT_TABLE"
191ms
And
Go to transport details "OWN_COLLECTION"
4s 458ms
Then
Check are advice values equals
2s 323ms
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 183ms
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 205ms
When
Click button advice in transport table "TRANSPORT_ORDER"
108ms
And
Set advice window in schedule
2s 509ms
And
Fill advice form
14s 607ms
And
Click advice save button and wait for advice form to disappear
30s 777ms
And
Go to "TRANSPORT_TABLE"
233ms
And
Go to transport details "TRANSPORT_ORDER"
4s 479ms
Then
Check are advice values equals
2s 334ms
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 845ms
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 356ms
When
Click button advice in transport table "OWN_COLLECTION"
122ms
And
Set advice window in schedule
2s 537ms
And
Fill advice form
14s 647ms
And
Click advice save button and wait for advice form to disappear
30s 806ms
And
Go to "TRANSPORT_TABLE"
175ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 164ms
After
Hooks.deleteTransportAfterTest()
126ms
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_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
004ms
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 335ms
When
Click button advice in transport table "CONTAINER"
124ms
And
Set advice window in schedule
2s 494ms
And
Fill advice form
14s 604ms
And
Click advice save button and wait for advice form to disappear
30s 770ms
And
Go to "TRANSPORT_TABLE"
183ms
Then
Check advice data in SK API database "CONTAINER"
4s 104ms
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 220ms
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 "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 225ms
When
Click button advice in transport table "TRANSPORT_ORDER"
131ms
And
Set advice window in schedule
2s 498ms
And
Fill advice form
14s 622ms
And
Click advice save button and wait for advice form to disappear
30s 782ms
And
Go to "TRANSPORT_TABLE"
229ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 044ms
After
Hooks.deleteTransportAfterTest()
144ms
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 228ms
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"
131ms
And
Set advice window in schedule in the past
2s 543ms
And
Fill advice form
14s 614ms
And
Click advice save button to check error message
103ms
Then
Check if possible advice alert is displayed
145ms
After
Hooks.deleteTransportAfterTest()
107ms
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 275ms
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 472ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 077ms
And
Go to "TRANSPORT_TABLE"
181ms
When
Go to transport details "OWN_COLLECTION"
4s 482ms
And
Expand advice panel
121ms
And
Edit advice in transport details
14s 115ms
And
Fill arrival date field
2s 288ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 623ms
Then
Check advice data in database after edition "OWN_COLLECTION"
039ms
After
Hooks.deleteTransportAfterTest()
167ms
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 223ms
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 384ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 078ms
And
Go to "TRANSPORT_TABLE"
163ms
When
Go to transport details "CONTAINER"
4s 471ms
And
Expand advice panel
110ms
And
Edit advice in transport details
14s 133ms
And
Fill arrival date field
2s 288ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 191ms
Then
Check advice data in database after edition "CONTAINER"
034ms
After
Hooks.deleteTransportAfterTest()
139ms
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_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
33s 305ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 218ms
And
Go to "TRANSPORT_TABLE"
206ms
When
Go to transport details "TRANSPORT_ORDER"
4s 478ms
And
Expand advice panel
124ms
And
Edit advice in transport details
14s 055ms
And
Fill arrival date field
2s 306ms
And
Click "save-transport-and-close" save button and wait for form to disappear
676ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
023ms
After
Hooks.deleteTransportAfterTest()
107ms