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 280ms
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
55s 015ms
When
Click button advice in transport table "CONTAINER"
087ms
And
Set advice window in schedule
2s 742ms
And
Fill advice form
14s 724ms
And
Click advice save button and wait for advice form to disappear
30s 715ms
And
Go to "TRANSPORT_TABLE"
186ms
And
Go to transport details "CONTAINER"
4s 449ms
Then
Check are advice values equals
2s 331ms
After
Hooks.deleteTransportAfterTest()
119ms
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 283ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
001ms
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 449ms
When
Click button advice in transport table "OWN_COLLECTION"
085ms
And
Set advice window in schedule
2s 641ms
And
Fill advice form
14s 625ms
And
Click advice save button and wait for advice form to disappear
30s 710ms
And
Go to "TRANSPORT_TABLE"
159ms
And
Go to transport details "OWN_COLLECTION"
4s 398ms
Then
Check are advice values equals
2s 306ms
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 297ms
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 878ms
When
Click button advice in transport table "TRANSPORT_ORDER"
085ms
And
Set advice window in schedule
2s 616ms
And
Fill advice form
14s 655ms
And
Click advice save button and wait for advice form to disappear
30s 742ms
And
Go to "TRANSPORT_TABLE"
210ms
And
Go to transport details "TRANSPORT_ORDER"
4s 443ms
Then
Check are advice values equals
2s 313ms
After
Hooks.deleteTransportAfterTest()
157ms
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 275ms
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
4s 077ms
When
Click button advice in transport table "OWN_COLLECTION"
078ms
And
Set advice window in schedule
2s 639ms
And
Fill advice form
14s 586ms
And
Click advice save button and wait for advice form to disappear
30s 710ms
And
Go to "TRANSPORT_TABLE"
185ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 174ms
After
Hooks.deleteTransportAfterTest()
146ms
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 264ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
003ms
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 982ms
When
Click button advice in transport table "CONTAINER"
077ms
And
Set advice window in schedule
2s 647ms
And
Fill advice form
14s 583ms
And
Click advice save button and wait for advice form to disappear
30s 743ms
And
Go to "TRANSPORT_TABLE"
194ms
Then
Check advice data in SK API database "CONTAINER"
3s 119ms
After
Hooks.deleteTransportAfterTest()
137ms
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 272ms
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"
003ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 884ms
When
Click button advice in transport table "TRANSPORT_ORDER"
081ms
And
Set advice window in schedule
2s 629ms
And
Fill advice form
14s 696ms
And
Click advice save button and wait for advice form to disappear
30s 751ms
And
Go to "TRANSPORT_TABLE"
238ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 039ms
After
Hooks.deleteTransportAfterTest()
132ms
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 282ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
003ms
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 958ms
When
Click button advice in transport table "CONTAINER"
078ms
And
Set advice window in schedule in the past
2s 676ms
And
Fill advice form
14s 673ms
And
Click advice save button to check error message
086ms
Then
Check if possible advice alert is displayed
021ms
After
Hooks.deleteTransportAfterTest()
134ms
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"
002ms
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
43s 147ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 122ms
And
Go to "TRANSPORT_TABLE"
206ms
When
Go to transport details "OWN_COLLECTION"
4s 433ms
And
Expand advice panel
110ms
And
Edit advice in transport details
13s 934ms
And
Fill arrival date field
2s 287ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 142ms
Then
Check advice data in database after edition "OWN_COLLECTION"
036ms
After
Hooks.deleteTransportAfterTest()
133ms
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 278ms
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 466ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 176ms
And
Go to "TRANSPORT_TABLE"
181ms
When
Go to transport details "CONTAINER"
4s 432ms
And
Expand advice panel
102ms
And
Edit advice in transport details
13s 958ms
And
Fill arrival date field
2s 283ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 119ms
Then
Check advice data in database after edition "CONTAINER"
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 274ms
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
30s 941ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 065ms
And
Go to "TRANSPORT_TABLE"
241ms
When
Go to transport details "TRANSPORT_ORDER"
4s 448ms
And
Expand advice panel
101ms
And
Edit advice in transport details
13s 978ms
And
Fill arrival date field
2s 265ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 636ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
026ms
After
Hooks.deleteTransportAfterTest()
136ms