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 221ms
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 986ms
When
Click button advice in transport table "CONTAINER"
091ms
And
Set advice window in schedule
2s 790ms
And
Fill advice form
14s 887ms
And
Click advice save button and wait for advice form to disappear
31s 238ms
And
Go to "TRANSPORT_TABLE"
207ms
And
Go to transport details "CONTAINER"
4s 511ms
Then
Check are advice values equals
2s 285ms
After
Hooks.deleteTransportAfterTest()
125ms
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 213ms
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 365ms
When
Click button advice in transport table "OWN_COLLECTION"
120ms
And
Set advice window in schedule
2s 589ms
And
Fill advice form
14s 707ms
And
Click advice save button and wait for advice form to disappear
30s 749ms
And
Go to "TRANSPORT_TABLE"
227ms
And
Go to transport details "OWN_COLLECTION"
4s 497ms
Then
Check are advice values equals
2s 302ms
After
Hooks.deleteTransportAfterTest()
138ms
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 228ms
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 261ms
When
Click button advice in transport table "TRANSPORT_ORDER"
114ms
And
Set advice window in schedule
2s 513ms
And
Fill advice form
14s 725ms
And
Click advice save button and wait for advice form to disappear
30s 740ms
And
Go to "TRANSPORT_TABLE"
228ms
And
Go to transport details "TRANSPORT_ORDER"
4s 475ms
Then
Check are advice values equals
2s 280ms
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 209ms
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 383ms
When
Click button advice in transport table "OWN_COLLECTION"
112ms
And
Set advice window in schedule
2s 533ms
And
Fill advice form
14s 703ms
And
Click advice save button and wait for advice form to disappear
30s 728ms
And
Go to "TRANSPORT_TABLE"
191ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 174ms
After
Hooks.deleteTransportAfterTest()
115ms
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 221ms
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 322ms
When
Click button advice in transport table "CONTAINER"
115ms
And
Set advice window in schedule
2s 539ms
And
Fill advice form
14s 737ms
And
Click advice save button and wait for advice form to disappear
30s 689ms
And
Go to "TRANSPORT_TABLE"
226ms
Then
Check advice data in SK API database "CONTAINER"
4s 104ms
After
Hooks.deleteTransportAfterTest()
131ms
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 253ms
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 205ms
When
Click button advice in transport table "TRANSPORT_ORDER"
105ms
And
Set advice window in schedule
2s 533ms
And
Fill advice form
14s 707ms
And
Click advice save button and wait for advice form to disappear
30s 724ms
And
Go to "TRANSPORT_TABLE"
251ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 042ms
After
Hooks.deleteTransportAfterTest()
109ms
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 225ms
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 312ms
When
Click button advice in transport table "CONTAINER"
115ms
And
Set advice window in schedule in the past
2s 526ms
And
Fill advice form
14s 756ms
And
Click advice save button to check error message
098ms
Then
Check if possible advice alert is displayed
027ms
After
Hooks.deleteTransportAfterTest()
082ms
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 248ms
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 540ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 203ms
And
Go to "TRANSPORT_TABLE"
226ms
When
Go to transport details "OWN_COLLECTION"
4s 490ms
And
Expand advice panel
098ms
And
Edit advice in transport details
14s 130ms
And
Fill arrival date field
2s 299ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 643ms
Then
Check advice data in database after edition "OWN_COLLECTION"
039ms
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 286ms
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 423ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 211ms
And
Go to "TRANSPORT_TABLE"
222ms
When
Go to transport details "CONTAINER"
4s 518ms
And
Expand advice panel
104ms
And
Edit advice in transport details
14s 159ms
And
Fill arrival date field
2s 298ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 164ms
Then
Check advice data in database after edition "CONTAINER"
040ms
After
Hooks.deleteTransportAfterTest()
230ms
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 272ms
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 341ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 292ms
And
Go to "TRANSPORT_TABLE"
244ms
When
Go to transport details "TRANSPORT_ORDER"
4s 453ms
And
Expand advice panel
103ms
And
Edit advice in transport details
14s 159ms
And
Fill arrival date field
2s 278ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 639ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
043ms
After
Hooks.deleteTransportAfterTest()
155ms