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 246ms
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
54s 435ms
When
Click button advice in transport table "CONTAINER"
111ms
And
Set advice window in schedule
2s 794ms
And
Fill advice form
14s 845ms
And
Click advice save button and wait for advice form to disappear
30s 753ms
And
Go to "TRANSPORT_TABLE"
216ms
And
Go to transport details "CONTAINER"
4s 514ms
Then
Check are advice values equals
2s 323ms
After
Hooks.deleteTransportAfterTest()
127ms
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 269ms
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
1m 1s 069ms
When
Click button advice in transport table "OWN_COLLECTION"
121ms
And
Set advice window in schedule
2s 602ms
And
Fill advice form
14s 753ms
And
Click advice save button and wait for advice form to disappear
30s 765ms
And
Go to "TRANSPORT_TABLE"
200ms
And
Go to transport details "OWN_COLLECTION"
4s 467ms
Then
Check are advice values equals
2s 361ms
After
Hooks.deleteTransportAfterTest()
151ms
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 275ms
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 234ms
When
Click button advice in transport table "TRANSPORT_ORDER"
115ms
And
Set advice window in schedule
2s 527ms
And
Fill advice form
14s 720ms
And
Click advice save button and wait for advice form to disappear
30s 700ms
And
Go to "TRANSPORT_TABLE"
244ms
And
Go to transport details "TRANSPORT_ORDER"
4s 471ms
Then
Check are advice values equals
2s 349ms
After
Hooks.deleteTransportAfterTest()
133ms
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 242ms
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 377ms
When
Click button advice in transport table "OWN_COLLECTION"
099ms
And
Set advice window in schedule
2s 565ms
And
Fill advice form
14s 714ms
And
Click advice save button and wait for advice form to disappear
30s 719ms
And
Go to "TRANSPORT_TABLE"
224ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 179ms
After
Hooks.deleteTransportAfterTest()
139ms
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 274ms
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
6s 336ms
When
Click button advice in transport table "CONTAINER"
118ms
And
Set advice window in schedule
2s 653ms
And
Fill advice form
14s 712ms
And
Click advice save button and wait for advice form to disappear
30s 762ms
And
Go to "TRANSPORT_TABLE"
184ms
Then
Check advice data in SK API database "CONTAINER"
3s 129ms
After
Hooks.deleteTransportAfterTest()
121ms
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 209ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
003ms
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 858ms
When
Click button advice in transport table "TRANSPORT_ORDER"
120ms
And
Set advice window in schedule
2s 531ms
And
Fill advice form
14s 672ms
And
Click advice save button and wait for advice form to disappear
30s 753ms
And
Go to "TRANSPORT_TABLE"
247ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 035ms
After
Hooks.deleteTransportAfterTest()
129ms
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 176ms
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
9s 349ms
When
Click button advice in transport table "CONTAINER"
107ms
And
Set advice window in schedule in the past
2s 599ms
And
Fill advice form
14s 722ms
And
Click advice save button to check error message
084ms
Then
Check if possible advice alert is displayed
017ms
After
Hooks.deleteTransportAfterTest()
085ms
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 219ms
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
39s 480ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 168ms
And
Go to "TRANSPORT_TABLE"
181ms
When
Go to transport details "OWN_COLLECTION"
4s 475ms
And
Expand advice panel
149ms
And
Edit advice in transport details
14s 129ms
And
Fill arrival date field
2s 300ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 632ms
Then
Check advice data in database after edition "OWN_COLLECTION"
036ms
After
Hooks.deleteTransportAfterTest()
162ms
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 254ms
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 444ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 156ms
And
Go to "TRANSPORT_TABLE"
214ms
When
Go to transport details "CONTAINER"
4s 527ms
And
Expand advice panel
108ms
And
Edit advice in transport details
14s 153ms
And
Fill arrival date field
2s 299ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 623ms
Then
Check advice data in database after edition "CONTAINER"
036ms
After
Hooks.deleteTransportAfterTest()
117ms
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"
001ms
And
Add transport by SKApi in "MGW"
002ms
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 334ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 302ms
And
Go to "TRANSPORT_TABLE"
249ms
When
Go to transport details "TRANSPORT_ORDER"
4s 486ms
And
Expand advice panel
113ms
And
Edit advice in transport details
14s 154ms
And
Fill arrival date field
2s 294ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 661ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
042ms
After
Hooks.deleteTransportAfterTest()
174ms