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 217ms
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
54s 417ms
When
Click button advice in transport table "CONTAINER"
109ms
And
Set advice window in schedule
2s 628ms
And
Fill advice form
14s 800ms
And
Click advice save button and wait for advice form to disappear
30s 689ms
And
Go to "TRANSPORT_TABLE"
220ms
And
Go to transport details "CONTAINER"
4s 524ms
Then
Check are advice values equals
2s 346ms
After
Hooks.deleteTransportAfterTest()
146ms
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 235ms
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 383ms
When
Click button advice in transport table "OWN_COLLECTION"
099ms
And
Set advice window in schedule
2s 572ms
And
Fill advice form
14s 734ms
And
Click advice save button and wait for advice form to disappear
30s 748ms
And
Go to "TRANSPORT_TABLE"
199ms
And
Go to transport details "OWN_COLLECTION"
4s 462ms
Then
Check are advice values equals
2s 341ms
After
Hooks.deleteTransportAfterTest()
132ms
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 237ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
004ms
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 246ms
When
Click button advice in transport table "TRANSPORT_ORDER"
109ms
And
Set advice window in schedule
2s 547ms
And
Fill advice form
14s 744ms
And
Click advice save button and wait for advice form to disappear
30s 723ms
And
Go to "TRANSPORT_TABLE"
222ms
And
Go to transport details "TRANSPORT_ORDER"
4s 468ms
Then
Check are advice values equals
2s 349ms
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 174ms
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 398ms
When
Click button advice in transport table "OWN_COLLECTION"
118ms
And
Set advice window in schedule
2s 555ms
And
Fill advice form
14s 657ms
And
Click advice save button and wait for advice form to disappear
30s 714ms
And
Go to "TRANSPORT_TABLE"
228ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 165ms
After
Hooks.deleteTransportAfterTest()
122ms
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 190ms
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 325ms
When
Click button advice in transport table "CONTAINER"
127ms
And
Set advice window in schedule
2s 508ms
And
Fill advice form
14s 738ms
And
Click advice save button and wait for advice form to disappear
30s 712ms
And
Go to "TRANSPORT_TABLE"
191ms
Then
Check advice data in SK API database "CONTAINER"
4s 126ms
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 248ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
003ms
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 233ms
When
Click button advice in transport table "TRANSPORT_ORDER"
127ms
And
Set advice window in schedule
2s 502ms
And
Fill advice form
14s 649ms
And
Click advice save button and wait for advice form to disappear
30s 749ms
And
Go to "TRANSPORT_TABLE"
239ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 045ms
After
Hooks.deleteTransportAfterTest()
129ms
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 220ms
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 321ms
When
Click button advice in transport table "CONTAINER"
091ms
And
Set advice window in schedule in the past
2s 535ms
And
Fill advice form
14s 682ms
And
Click advice save button to check error message
096ms
Then
Check if possible advice alert is displayed
019ms
After
Hooks.deleteTransportAfterTest()
108ms
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 224ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
010ms
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 489ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 150ms
And
Go to "TRANSPORT_TABLE"
180ms
When
Go to transport details "OWN_COLLECTION"
4s 481ms
And
Expand advice panel
119ms
And
Edit advice in transport details
14s 123ms
And
Fill arrival date field
2s 308ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 616ms
Then
Check advice data in database after edition "OWN_COLLECTION"
042ms
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 218ms
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 404ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 242ms
And
Go to "TRANSPORT_TABLE"
187ms
When
Go to transport details "CONTAINER"
4s 553ms
And
Expand advice panel
120ms
And
Edit advice in transport details
14s 163ms
And
Fill arrival date field
2s 292ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 672ms
Then
Check advice data in database after edition "CONTAINER"
041ms
After
Hooks.deleteTransportAfterTest()
144ms
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 225ms
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 329ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 226ms
And
Go to "TRANSPORT_TABLE"
189ms
When
Go to transport details "TRANSPORT_ORDER"
4s 493ms
And
Expand advice panel
123ms
And
Edit advice in transport details
14s 073ms
And
Fill arrival date field
2s 304ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 597ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
036ms
After
Hooks.deleteTransportAfterTest()
122ms