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 176ms
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 421ms
When
Click button advice in transport table "CONTAINER"
110ms
And
Set advice window in schedule
2s 747ms
And
Fill advice form
14s 822ms
And
Click advice save button and wait for advice form to disappear
31s 232ms
And
Go to "TRANSPORT_TABLE"
190ms
And
Go to transport details "CONTAINER"
4s 523ms
Then
Check are advice values equals
2s 325ms
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 253ms
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 364ms
When
Click button advice in transport table "OWN_COLLECTION"
117ms
And
Set advice window in schedule
2s 551ms
And
Fill advice form
14s 656ms
And
Click advice save button and wait for advice form to disappear
30s 733ms
And
Go to "TRANSPORT_TABLE"
206ms
And
Go to transport details "OWN_COLLECTION"
4s 499ms
Then
Check are advice values equals
2s 295ms
After
Hooks.deleteTransportAfterTest()
160ms
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 231ms
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 "CREATE_ADVICE" "super-admin-skz"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 254ms
When
Click button advice in transport table "TRANSPORT_ORDER"
120ms
And
Set advice window in schedule
2s 547ms
And
Fill advice form
14s 690ms
And
Click advice save button and wait for advice form to disappear
30s 704ms
And
Go to "TRANSPORT_TABLE"
238ms
And
Go to transport details "TRANSPORT_ORDER"
4s 441ms
Then
Check are advice values equals
2s 341ms
After
Hooks.deleteTransportAfterTest()
129ms
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 223ms
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 370ms
When
Click button advice in transport table "OWN_COLLECTION"
114ms
And
Set advice window in schedule
2s 543ms
And
Fill advice form
14s 680ms
And
Click advice save button and wait for advice form to disappear
30s 715ms
And
Go to "TRANSPORT_TABLE"
205ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 161ms
After
Hooks.deleteTransportAfterTest()
140ms
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 214ms
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
6s 342ms
When
Click button advice in transport table "CONTAINER"
113ms
And
Set advice window in schedule
2s 522ms
And
Fill advice form
14s 738ms
And
Click advice save button and wait for advice form to disappear
30s 716ms
And
Go to "TRANSPORT_TABLE"
216ms
Then
Check advice data in SK API database "CONTAINER"
4s 113ms
After
Hooks.deleteTransportAfterTest()
148ms
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_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 227ms
When
Click button advice in transport table "TRANSPORT_ORDER"
103ms
And
Set advice window in schedule
2s 518ms
And
Fill advice form
14s 701ms
And
Click advice save button and wait for advice form to disappear
30s 732ms
And
Go to "TRANSPORT_TABLE"
253ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 039ms
After
Hooks.deleteTransportAfterTest()
108ms
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 188ms
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"
111ms
And
Set advice window in schedule in the past
2s 568ms
And
Fill advice form
14s 670ms
And
Click advice save button to check error message
096ms
Then
Check if possible advice alert is displayed
018ms
After
Hooks.deleteTransportAfterTest()
119ms
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 192ms
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"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
45s 496ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 916ms
And
Go to "TRANSPORT_TABLE"
221ms
When
Go to transport details "OWN_COLLECTION"
4s 484ms
And
Expand advice panel
102ms
And
Edit advice in transport details
14s 045ms
And
Fill arrival date field
2s 285ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 652ms
Then
Check advice data in database after edition "OWN_COLLECTION"
040ms
After
Hooks.deleteTransportAfterTest()
166ms
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 261ms
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
27s 426ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 157ms
And
Go to "TRANSPORT_TABLE"
196ms
When
Go to transport details "CONTAINER"
4s 508ms
And
Expand advice panel
111ms
And
Edit advice in transport details
14s 129ms
And
Fill arrival date field
2s 298ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 155ms
Then
Check advice data in database after edition "CONTAINER"
039ms
After
Hooks.deleteTransportAfterTest()
217ms
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"
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 400ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 214ms
And
Go to "TRANSPORT_TABLE"
239ms
When
Go to transport details "TRANSPORT_ORDER"
4s 471ms
And
Expand advice panel
096ms
And
Edit advice in transport details
14s 097ms
And
Fill arrival date field
2s 299ms
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()
136ms