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 249ms
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"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
54s 373ms
When
Click button advice in transport table "CONTAINER"
104ms
And
Set advice window in schedule
2s 630ms
And
Fill advice form
14s 820ms
And
Click advice save button and wait for advice form to disappear
30s 758ms
And
Go to "TRANSPORT_TABLE"
193ms
And
Go to transport details "CONTAINER"
4s 519ms
Then
Check are advice values equals
2s 337ms
After
Hooks.deleteTransportAfterTest()
143ms
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 218ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
3s 445ms
When
Click button advice in transport table "OWN_COLLECTION"
120ms
And
Set advice window in schedule
2s 498ms
And
Fill advice form
14s 764ms
And
Click advice save button and wait for advice form to disappear
30s 825ms
And
Go to "TRANSPORT_TABLE"
159ms
And
Go to transport details "OWN_COLLECTION"
4s 472ms
Then
Check are advice values equals
2s 349ms
After
Hooks.deleteTransportAfterTest()
114ms
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 276ms
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
1s 138ms
When
Click button advice in transport table "TRANSPORT_ORDER"
138ms
And
Set advice window in schedule
2s 511ms
And
Fill advice form
14s 731ms
And
Click advice save button and wait for advice form to disappear
30s 665ms
And
Go to "TRANSPORT_TABLE"
240ms
And
Go to transport details "TRANSPORT_ORDER"
4s 491ms
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 249ms
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 380ms
When
Click button advice in transport table "OWN_COLLECTION"
117ms
And
Set advice window in schedule
2s 510ms
And
Fill advice form
14s 721ms
And
Click advice save button and wait for advice form to disappear
30s 779ms
And
Go to "TRANSPORT_TABLE"
178ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 170ms
After
Hooks.deleteTransportAfterTest()
131ms
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 247ms
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 298ms
When
Click button advice in transport table "CONTAINER"
116ms
And
Set advice window in schedule
2s 502ms
And
Fill advice form
14s 740ms
And
Click advice save button and wait for advice form to disappear
30s 744ms
And
Go to "TRANSPORT_TABLE"
159ms
Then
Check advice data in SK API database "CONTAINER"
4s 121ms
After
Hooks.deleteTransportAfterTest()
132ms
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 333ms
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 219ms
When
Click button advice in transport table "TRANSPORT_ORDER"
124ms
And
Set advice window in schedule
2s 533ms
And
Fill advice form
14s 744ms
And
Click advice save button and wait for advice form to disappear
30s 711ms
And
Go to "TRANSPORT_TABLE"
213ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 042ms
After
Hooks.deleteTransportAfterTest()
100ms
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 206ms
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
9s 325ms
When
Click button advice in transport table "CONTAINER"
102ms
And
Set advice window in schedule in the past
2s 609ms
And
Fill advice form
14s 829ms
And
Click advice save button to check error message
107ms
Then
Check if possible advice alert is displayed
025ms
After
Hooks.deleteTransportAfterTest()
110ms
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 188ms
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 493ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 218ms
And
Go to "TRANSPORT_TABLE"
186ms
When
Go to transport details "OWN_COLLECTION"
4s 495ms
And
Expand advice panel
118ms
And
Edit advice in transport details
14s 150ms
And
Fill arrival date field
2s 322ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 650ms
Then
Check advice data in database after edition "OWN_COLLECTION"
038ms
After
Hooks.deleteTransportAfterTest()
156ms
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 224ms
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 408ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 314ms
And
Go to "TRANSPORT_TABLE"
180ms
When
Go to transport details "CONTAINER"
4s 518ms
And
Expand advice panel
112ms
And
Edit advice in transport details
14s 146ms
And
Fill arrival date field
2s 307ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 644ms
Then
Check advice data in database after edition "CONTAINER"
034ms
After
Hooks.deleteTransportAfterTest()
163ms
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 260ms
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 "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 333ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 325ms
And
Go to "TRANSPORT_TABLE"
203ms
When
Go to transport details "TRANSPORT_ORDER"
4s 443ms
And
Expand advice panel
121ms
And
Edit advice in transport details
14s 132ms
And
Fill arrival date field
2s 290ms
And
Click "save-transport-and-close" save button and wait for form to disappear
675ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
036ms
After
Hooks.deleteTransportAfterTest()
123ms