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 199ms
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 391ms
When
Click button advice in transport table "CONTAINER"
111ms
And
Set advice window in schedule
2s 671ms
And
Fill advice form
14s 709ms
And
Click advice save button and wait for advice form to disappear
30s 691ms
And
Go to "TRANSPORT_TABLE"
233ms
And
Go to transport details "CONTAINER"
4s 533ms
Then
Check are advice values equals
2s 352ms
After
Hooks.deleteTransportAfterTest()
136ms
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 236ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
3s 363ms
When
Click button advice in transport table "OWN_COLLECTION"
094ms
And
Set advice window in schedule
2s 535ms
And
Fill advice form
14s 673ms
And
Click advice save button and wait for advice form to disappear
30s 726ms
And
Go to "TRANSPORT_TABLE"
219ms
And
Go to transport details "OWN_COLLECTION"
4s 471ms
Then
Check are advice values equals
2s 338ms
After
Hooks.deleteTransportAfterTest()
145ms
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 236ms
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"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 192ms
When
Click button advice in transport table "TRANSPORT_ORDER"
109ms
And
Set advice window in schedule
2s 605ms
And
Fill advice form
14s 725ms
And
Click advice save button and wait for advice form to disappear
30s 767ms
And
Go to "TRANSPORT_TABLE"
243ms
And
Go to transport details "TRANSPORT_ORDER"
4s 461ms
Then
Check are advice values equals
2s 336ms
After
Hooks.deleteTransportAfterTest()
108ms
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 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 "CREATE_ADVICE" "super-admin-skz"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 378ms
When
Click button advice in transport table "OWN_COLLECTION"
107ms
And
Set advice window in schedule
2s 566ms
And
Fill advice form
14s 651ms
And
Click advice save button and wait for advice form to disappear
30s 722ms
And
Go to "TRANSPORT_TABLE"
186ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 176ms
After
Hooks.deleteTransportAfterTest()
083ms
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 250ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
001ms
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
6s 295ms
When
Click button advice in transport table "CONTAINER"
117ms
And
Set advice window in schedule
2s 532ms
And
Fill advice form
14s 736ms
And
Click advice save button and wait for advice form to disappear
30s 748ms
And
Go to "TRANSPORT_TABLE"
190ms
Then
Check advice data in SK API database "CONTAINER"
4s 105ms
After
Hooks.deleteTransportAfterTest()
147ms
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 269ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
005ms
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
6s 206ms
When
Click button advice in transport table "TRANSPORT_ORDER"
112ms
And
Set advice window in schedule
2s 532ms
And
Fill advice form
14s 671ms
And
Click advice save button and wait for advice form to disappear
30s 767ms
And
Go to "TRANSPORT_TABLE"
241ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 047ms
After
Hooks.deleteTransportAfterTest()
114ms
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 229ms
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
9s 328ms
When
Click button advice in transport table "CONTAINER"
125ms
And
Set advice window in schedule in the past
2s 636ms
And
Fill advice form
14s 685ms
And
Click advice save button to check error message
082ms
Then
Check if possible advice alert is displayed
017ms
After
Hooks.deleteTransportAfterTest()
094ms
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 252ms
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
39s 422ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 219ms
And
Go to "TRANSPORT_TABLE"
214ms
When
Go to transport details "OWN_COLLECTION"
4s 495ms
And
Expand advice panel
120ms
And
Edit advice in transport details
14s 123ms
And
Fill arrival date field
2s 323ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 595ms
Then
Check advice data in database after edition "OWN_COLLECTION"
040ms
After
Hooks.deleteTransportAfterTest()
151ms
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 284ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
001ms
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 385ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 130ms
And
Go to "TRANSPORT_TABLE"
197ms
When
Go to transport details "CONTAINER"
4s 545ms
And
Expand advice panel
118ms
And
Edit advice in transport details
14s 142ms
And
Fill arrival date field
2s 291ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 648ms
Then
Check advice data in database after edition "CONTAINER"
039ms
After
Hooks.deleteTransportAfterTest()
119ms
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 298ms
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"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 280ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 162ms
And
Go to "TRANSPORT_TABLE"
257ms
When
Go to transport details "TRANSPORT_ORDER"
4s 507ms
And
Expand advice panel
119ms
And
Edit advice in transport details
14s 151ms
And
Fill arrival date field
2s 299ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 653ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
038ms
After
Hooks.deleteTransportAfterTest()
127ms