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 242ms
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 419ms
When
Click button advice in transport table "CONTAINER"
123ms
And
Set advice window in schedule
2s 707ms
And
Fill advice form
14s 631ms
And
Click advice save button and wait for advice form to disappear
31s 237ms
And
Go to "TRANSPORT_TABLE"
168ms
And
Go to transport details "CONTAINER"
4s 511ms
Then
Check are advice values equals
2s 314ms
After
Hooks.deleteTransportAfterTest()
126ms
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 300ms
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"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 364ms
When
Click button advice in transport table "OWN_COLLECTION"
133ms
And
Set advice window in schedule
2s 511ms
And
Fill advice form
14s 641ms
And
Click advice save button and wait for advice form to disappear
30s 747ms
And
Go to "TRANSPORT_TABLE"
185ms
And
Go to transport details "OWN_COLLECTION"
4s 487ms
Then
Check are advice values equals
2s 325ms
After
Hooks.deleteTransportAfterTest()
158ms
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 258ms
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"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 232ms
When
Click button advice in transport table "TRANSPORT_ORDER"
133ms
And
Set advice window in schedule
2s 492ms
And
Fill advice form
14s 631ms
And
Click advice save button and wait for advice form to disappear
30s 713ms
And
Go to "TRANSPORT_TABLE"
227ms
And
Go to transport details "TRANSPORT_ORDER"
4s 488ms
Then
Check are advice values equals
2s 351ms
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 420ms
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"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 385ms
When
Click button advice in transport table "OWN_COLLECTION"
116ms
And
Set advice window in schedule
2s 491ms
And
Fill advice form
14s 589ms
And
Click advice save button and wait for advice form to disappear
30s 751ms
And
Go to "TRANSPORT_TABLE"
186ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 168ms
After
Hooks.deleteTransportAfterTest()
090ms
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 216ms
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 310ms
When
Click button advice in transport table "CONTAINER"
129ms
And
Set advice window in schedule
2s 486ms
And
Fill advice form
14s 597ms
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 "CONTAINER"
4s 103ms
After
Hooks.deleteTransportAfterTest()
135ms
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 203ms
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"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 222ms
When
Click button advice in transport table "TRANSPORT_ORDER"
124ms
And
Set advice window in schedule
2s 490ms
And
Fill advice form
14s 677ms
And
Click advice save button and wait for advice form to disappear
30s 736ms
And
Go to "TRANSPORT_TABLE"
213ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 045ms
After
Hooks.deleteTransportAfterTest()
136ms
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 241ms
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"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 321ms
When
Click button advice in transport table "CONTAINER"
115ms
And
Set advice window in schedule in the past
2s 539ms
And
Fill advice form
14s 635ms
And
Click advice save button to check error message
092ms
Then
Check if possible advice alert is displayed
139ms
After
Hooks.deleteTransportAfterTest()
079ms
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 233ms
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 464ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 090ms
And
Go to "TRANSPORT_TABLE"
181ms
When
Go to transport details "OWN_COLLECTION"
4s 465ms
And
Expand advice panel
091ms
And
Edit advice in transport details
14s 134ms
And
Fill arrival date field
2s 320ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 171ms
Then
Check advice data in database after edition "OWN_COLLECTION"
035ms
After
Hooks.deleteTransportAfterTest()
137ms
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 182ms
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 420ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 109ms
And
Go to "TRANSPORT_TABLE"
183ms
When
Go to transport details "CONTAINER"
4s 553ms
And
Expand advice panel
091ms
And
Edit advice in transport details
14s 083ms
And
Fill arrival date field
2s 307ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 188ms
Then
Check advice data in database after edition "CONTAINER"
033ms
After
Hooks.deleteTransportAfterTest()
157ms
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 253ms
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 310ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 156ms
And
Go to "TRANSPORT_TABLE"
198ms
When
Go to transport details "TRANSPORT_ORDER"
4s 438ms
And
Expand advice panel
094ms
And
Edit advice in transport details
14s 077ms
And
Fill arrival date field
2s 292ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 633ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
038ms
After
Hooks.deleteTransportAfterTest()
124ms