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 255ms
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 426ms
When
Click button advice in transport table "CONTAINER"
115ms
And
Set advice window in schedule
2s 749ms
And
Fill advice form
14s 718ms
And
Click advice save button and wait for advice form to disappear
30s 740ms
And
Go to "TRANSPORT_TABLE"
219ms
And
Go to transport details "CONTAINER"
4s 543ms
Then
Check are advice values equals
2s 339ms
After
Hooks.deleteTransportAfterTest()
132ms
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 248ms
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 421ms
When
Click button advice in transport table "OWN_COLLECTION"
119ms
And
Set advice window in schedule
2s 549ms
And
Fill advice form
14s 711ms
And
Click advice save button and wait for advice form to disappear
30s 753ms
And
Go to "TRANSPORT_TABLE"
184ms
And
Go to transport details "OWN_COLLECTION"
4s 458ms
Then
Check are advice values equals
2s 348ms
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 241ms
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 223ms
When
Click button advice in transport table "TRANSPORT_ORDER"
119ms
And
Set advice window in schedule
2s 518ms
And
Fill advice form
14s 725ms
And
Click advice save button and wait for advice form to disappear
30s 703ms
And
Go to "TRANSPORT_TABLE"
253ms
And
Go to transport details "TRANSPORT_ORDER"
4s 491ms
Then
Check are advice values equals
2s 331ms
After
Hooks.deleteTransportAfterTest()
120ms
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 233ms
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"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 402ms
When
Click button advice in transport table "OWN_COLLECTION"
129ms
And
Set advice window in schedule
2s 521ms
And
Fill advice form
14s 721ms
And
Click advice save button and wait for advice form to disappear
30s 740ms
And
Go to "TRANSPORT_TABLE"
194ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 188ms
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 175ms
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"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 339ms
When
Click button advice in transport table "CONTAINER"
118ms
And
Set advice window in schedule
2s 529ms
And
Fill advice form
14s 751ms
And
Click advice save button and wait for advice form to disappear
30s 737ms
And
Go to "TRANSPORT_TABLE"
196ms
Then
Check advice data in SK API database "CONTAINER"
4s 104ms
After
Hooks.deleteTransportAfterTest()
130ms
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 218ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id
6s 229ms
When
Click button advice in transport table "TRANSPORT_ORDER"
118ms
And
Set advice window in schedule
2s 552ms
And
Fill advice form
14s 708ms
And
Click advice save button and wait for advice form to disappear
30s 752ms
And
Go to "TRANSPORT_TABLE"
259ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 042ms
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 196ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
005ms
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"
118ms
And
Set advice window in schedule in the past
2s 553ms
And
Fill advice form
14s 743ms
And
Click advice save button to check error message
093ms
Then
Check if possible advice alert is displayed
021ms
After
Hooks.deleteTransportAfterTest()
128ms
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 247ms
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
42s 457ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 224ms
And
Go to "TRANSPORT_TABLE"
212ms
When
Go to transport details "OWN_COLLECTION"
4s 473ms
And
Expand advice panel
092ms
And
Edit advice in transport details
14s 125ms
And
Fill arrival date field
2s 308ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 647ms
Then
Check advice data in database after edition "OWN_COLLECTION"
036ms
After
Hooks.deleteTransportAfterTest()
145ms
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 842ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
33s 426ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 220ms
And
Go to "TRANSPORT_TABLE"
212ms
When
Go to transport details "CONTAINER"
4s 517ms
And
Expand advice panel
091ms
And
Edit advice in transport details
14s 173ms
And
Fill arrival date field
2s 315ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 656ms
Then
Check advice data in database after edition "CONTAINER"
039ms
After
Hooks.deleteTransportAfterTest()
169ms
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 263ms
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 "EDIT_ADVICE" "super-admin-skz"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 325ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 312ms
And
Go to "TRANSPORT_TABLE"
230ms
When
Go to transport details "TRANSPORT_ORDER"
4s 497ms
And
Expand advice panel
096ms
And
Edit advice in transport details
14s 155ms
And
Fill arrival date field
2s 308ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 652ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
039ms
After
Hooks.deleteTransportAfterTest()
166ms