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 282ms
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 442ms
When
Click button advice in transport table "CONTAINER"
111ms
And
Set advice window in schedule
2s 663ms
And
Fill advice form
14s 890ms
And
Click advice save button and wait for advice form to disappear
30s 780ms
And
Go to "TRANSPORT_TABLE"
171ms
And
Go to transport details "CONTAINER"
4s 515ms
Then
Check are advice values equals
2s 310ms
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 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 "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 390ms
When
Click button advice in transport table "OWN_COLLECTION"
139ms
And
Set advice window in schedule
2s 535ms
And
Fill advice form
14s 779ms
And
Click advice save button and wait for advice form to disappear
30s 759ms
And
Go to "TRANSPORT_TABLE"
193ms
And
Go to transport details "OWN_COLLECTION"
4s 482ms
Then
Check are advice values equals
2s 323ms
After
Hooks.deleteTransportAfterTest()
114ms
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 229ms
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
1s 145ms
When
Click button advice in transport table "TRANSPORT_ORDER"
122ms
And
Set advice window in schedule
2s 512ms
And
Fill advice form
14s 766ms
And
Click advice save button and wait for advice form to disappear
30s 683ms
And
Go to "TRANSPORT_TABLE"
201ms
And
Go to transport details "TRANSPORT_ORDER"
4s 476ms
Then
Check are advice values equals
2s 335ms
After
Hooks.deleteTransportAfterTest()
117ms
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 226ms
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 366ms
When
Click button advice in transport table "OWN_COLLECTION"
134ms
And
Set advice window in schedule
2s 547ms
And
Fill advice form
14s 790ms
And
Click advice save button and wait for advice form to disappear
30s 742ms
And
Go to "TRANSPORT_TABLE"
183ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 179ms
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 261ms
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"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 324ms
When
Click button advice in transport table "CONTAINER"
120ms
And
Set advice window in schedule
2s 501ms
And
Fill advice form
14s 787ms
And
Click advice save button and wait for advice form to disappear
30s 760ms
And
Go to "TRANSPORT_TABLE"
194ms
Then
Check advice data in SK API database "CONTAINER"
3s 110ms
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 229ms
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 843ms
When
Click button advice in transport table "TRANSPORT_ORDER"
125ms
And
Set advice window in schedule
2s 531ms
And
Fill advice form
14s 793ms
And
Click advice save button and wait for advice form to disappear
30s 773ms
And
Go to "TRANSPORT_TABLE"
201ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 046ms
After
Hooks.deleteTransportAfterTest()
112ms
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 519ms
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
9s 346ms
When
Click button advice in transport table "CONTAINER"
124ms
And
Set advice window in schedule in the past
2s 591ms
And
Fill advice form
14s 839ms
And
Click advice save button to check error message
091ms
Then
Check if possible advice alert is displayed
023ms
After
Hooks.deleteTransportAfterTest()
081ms
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 277ms
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 "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
39s 487ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 232ms
And
Go to "TRANSPORT_TABLE"
184ms
When
Go to transport details "OWN_COLLECTION"
4s 489ms
And
Expand advice panel
111ms
And
Edit advice in transport details
14s 081ms
And
Fill arrival date field
2s 297ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 607ms
Then
Check advice data in database after edition "OWN_COLLECTION"
034ms
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"
003ms
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 383ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 265ms
And
Go to "TRANSPORT_TABLE"
155ms
When
Go to transport details "CONTAINER"
4s 513ms
And
Expand advice panel
123ms
And
Edit advice in transport details
14s 040ms
And
Fill arrival date field
2s 305ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 664ms
Then
Check advice data in database after edition "CONTAINER"
033ms
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 310ms
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 334ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 329ms
And
Go to "TRANSPORT_TABLE"
185ms
When
Go to transport details "TRANSPORT_ORDER"
4s 423ms
And
Expand advice panel
127ms
And
Edit advice in transport details
14s 065ms
And
Fill arrival date field
2s 303ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 621ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
041ms
After
Hooks.deleteTransportAfterTest()
161ms