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 216ms
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
54s 414ms
When
Click button advice in transport table "CONTAINER"
123ms
And
Set advice window in schedule
2s 642ms
And
Fill advice form
14s 831ms
And
Click advice save button and wait for advice form to disappear
30s 760ms
And
Go to "TRANSPORT_TABLE"
214ms
And
Go to transport details "CONTAINER"
4s 538ms
Then
Check are advice values equals
2s 340ms
After
Hooks.deleteTransportAfterTest()
122ms
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 252ms
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 391ms
When
Click button advice in transport table "OWN_COLLECTION"
109ms
And
Set advice window in schedule
2s 533ms
And
Fill advice form
14s 840ms
And
Click advice save button and wait for advice form to disappear
30s 763ms
And
Go to "TRANSPORT_TABLE"
172ms
And
Go to transport details "OWN_COLLECTION"
4s 481ms
Then
Check are advice values equals
2s 326ms
After
Hooks.deleteTransportAfterTest()
144ms
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 195ms
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 221ms
When
Click button advice in transport table "TRANSPORT_ORDER"
110ms
And
Set advice window in schedule
2s 568ms
And
Fill advice form
14s 787ms
And
Click advice save button and wait for advice form to disappear
30s 765ms
And
Go to "TRANSPORT_TABLE"
244ms
And
Go to transport details "TRANSPORT_ORDER"
4s 521ms
Then
Check are advice values equals
2s 322ms
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 189ms
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 394ms
When
Click button advice in transport table "OWN_COLLECTION"
127ms
And
Set advice window in schedule
2s 560ms
And
Fill advice form
14s 757ms
And
Click advice save button and wait for advice form to disappear
30s 738ms
And
Go to "TRANSPORT_TABLE"
200ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 157ms
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 246ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
9s 361ms
When
Click button advice in transport table "CONTAINER"
109ms
And
Set advice window in schedule
2s 573ms
And
Fill advice form
14s 739ms
And
Click advice save button and wait for advice form to disappear
30s 734ms
And
Go to "TRANSPORT_TABLE"
220ms
Then
Check advice data in SK API database "CONTAINER"
1s 113ms
After
Hooks.deleteTransportAfterTest()
132ms
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 198ms
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 265ms
When
Click button advice in transport table "TRANSPORT_ORDER"
124ms
And
Set advice window in schedule
2s 594ms
And
Fill advice form
14s 824ms
And
Click advice save button and wait for advice form to disappear
30s 690ms
And
Go to "TRANSPORT_TABLE"
232ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 045ms
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 192ms
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
6s 335ms
When
Click button advice in transport table "CONTAINER"
105ms
And
Set advice window in schedule in the past
2s 531ms
And
Fill advice form
14s 811ms
And
Click advice save button to check error message
092ms
Then
Check if possible advice alert is displayed
032ms
After
Hooks.deleteTransportAfterTest()
106ms
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 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 "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
42s 423ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 112ms
And
Go to "TRANSPORT_TABLE"
178ms
When
Go to transport details "OWN_COLLECTION"
4s 489ms
And
Expand advice panel
111ms
And
Edit advice in transport details
14s 091ms
And
Fill arrival date field
2s 292ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 665ms
Then
Check advice data in database after edition "OWN_COLLECTION"
034ms
After
Hooks.deleteTransportAfterTest()
124ms
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 732ms
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 436ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 263ms
And
Go to "TRANSPORT_TABLE"
204ms
When
Go to transport details "CONTAINER"
4s 514ms
And
Expand advice panel
110ms
And
Edit advice in transport details
14s 129ms
And
Fill arrival date field
2s 272ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 622ms
Then
Check advice data in database after edition "CONTAINER"
034ms
After
Hooks.deleteTransportAfterTest()
159ms
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 255ms
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"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 381ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 278ms
And
Go to "TRANSPORT_TABLE"
254ms
When
Go to transport details "TRANSPORT_ORDER"
4s 504ms
And
Expand advice panel
119ms
And
Edit advice in transport details
14s 091ms
And
Fill arrival date field
2s 292ms
And
Click "save-transport-and-close" save button and wait for form to disappear
689ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
029ms
After
Hooks.deleteTransportAfterTest()
109ms