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"
001ms
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 446ms
When
Click button advice in transport table "CONTAINER"
105ms
And
Set advice window in schedule
2s 653ms
And
Fill advice form
14s 829ms
And
Click advice save button and wait for advice form to disappear
30s 725ms
And
Go to "TRANSPORT_TABLE"
213ms
And
Go to transport details "CONTAINER"
4s 517ms
Then
Check are advice values equals
2s 323ms
After
Hooks.deleteTransportAfterTest()
137ms
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 245ms
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 401ms
When
Click button advice in transport table "OWN_COLLECTION"
118ms
And
Set advice window in schedule
2s 567ms
And
Fill advice form
14s 768ms
And
Click advice save button and wait for advice form to disappear
30s 776ms
And
Go to "TRANSPORT_TABLE"
192ms
And
Go to transport details "OWN_COLLECTION"
4s 454ms
Then
Check are advice values equals
2s 320ms
After
Hooks.deleteTransportAfterTest()
133ms
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 203ms
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 248ms
When
Click button advice in transport table "TRANSPORT_ORDER"
109ms
And
Set advice window in schedule
2s 527ms
And
Fill advice form
14s 792ms
And
Click advice save button and wait for advice form to disappear
30s 758ms
And
Go to "TRANSPORT_TABLE"
245ms
And
Go to transport details "TRANSPORT_ORDER"
4s 483ms
Then
Check are advice values equals
2s 324ms
After
Hooks.deleteTransportAfterTest()
126ms
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 245ms
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 387ms
When
Click button advice in transport table "OWN_COLLECTION"
120ms
And
Set advice window in schedule
2s 543ms
And
Fill advice form
14s 741ms
And
Click advice save button and wait for advice form to disappear
30s 758ms
And
Go to "TRANSPORT_TABLE"
190ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 170ms
After
Hooks.deleteTransportAfterTest()
127ms
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 756ms
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
6s 335ms
When
Click button advice in transport table "CONTAINER"
117ms
And
Set advice window in schedule
2s 532ms
And
Fill advice form
14s 769ms
And
Click advice save button and wait for advice form to disappear
30s 771ms
And
Go to "TRANSPORT_TABLE"
178ms
Then
Check advice data in SK API database "CONTAINER"
3s 116ms
After
Hooks.deleteTransportAfterTest()
144ms
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_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 225ms
When
Click button advice in transport table "TRANSPORT_ORDER"
112ms
And
Set advice window in schedule
2s 521ms
And
Fill advice form
14s 730ms
And
Click advice save button and wait for advice form to disappear
30s 772ms
And
Go to "TRANSPORT_TABLE"
253ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 049ms
After
Hooks.deleteTransportAfterTest()
107ms
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 172ms
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 326ms
When
Click button advice in transport table "CONTAINER"
123ms
And
Set advice window in schedule in the past
2s 535ms
And
Fill advice form
14s 753ms
And
Click advice save button to check error message
106ms
Then
Check if possible advice alert is displayed
025ms
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 207ms
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
42s 476ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 304ms
And
Go to "TRANSPORT_TABLE"
199ms
When
Go to transport details "OWN_COLLECTION"
4s 450ms
And
Expand advice panel
098ms
And
Edit advice in transport details
14s 048ms
And
Fill arrival date field
2s 282ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 596ms
Then
Check advice data in database after edition "OWN_COLLECTION"
039ms
After
Hooks.deleteTransportAfterTest()
115ms
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 268ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
001ms
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 424ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 287ms
And
Go to "TRANSPORT_TABLE"
207ms
When
Go to transport details "CONTAINER"
4s 490ms
And
Expand advice panel
102ms
And
Edit advice in transport details
14s 069ms
And
Fill arrival date field
2s 273ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 635ms
Then
Check advice data in database after edition "CONTAINER"
037ms
After
Hooks.deleteTransportAfterTest()
111ms
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 279ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id
33s 321ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 273ms
And
Go to "TRANSPORT_TABLE"
235ms
When
Go to transport details "TRANSPORT_ORDER"
4s 484ms
And
Expand advice panel
127ms
And
Edit advice in transport details
14s 111ms
And
Fill arrival date field
2s 298ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 653ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
039ms
After
Hooks.deleteTransportAfterTest()
133ms