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 251ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
002ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
003ms
And
Check is transport "CONTAINER" created in transport table and set transport id
54s 383ms
When
Click button advice in transport table "CONTAINER"
086ms
And
Set advice window in schedule
2s 766ms
And
Fill advice form
14s 568ms
And
Click advice save button and wait for advice form to disappear
30s 755ms
And
Go to "TRANSPORT_TABLE"
210ms
And
Go to transport details "CONTAINER"
4s 479ms
Then
Check are advice values equals
2s 473ms
After
Hooks.deleteTransportAfterTest()
126ms
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 249ms
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 361ms
When
Click button advice in transport table "OWN_COLLECTION"
099ms
And
Set advice window in schedule
2s 603ms
And
Fill advice form
14s 542ms
And
Click advice save button and wait for advice form to disappear
30s 713ms
And
Go to "TRANSPORT_TABLE"
148ms
And
Go to transport details "OWN_COLLECTION"
4s 449ms
Then
Check are advice values equals
2s 303ms
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 217ms
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 "CREATE_ADVICE" "super-admin-skz"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 237ms
When
Click button advice in transport table "TRANSPORT_ORDER"
086ms
And
Set advice window in schedule
2s 585ms
And
Fill advice form
14s 663ms
And
Click advice save button and wait for advice form to disappear
30s 678ms
And
Go to "TRANSPORT_TABLE"
191ms
And
Go to transport details "TRANSPORT_ORDER"
4s 441ms
Then
Check are advice values equals
2s 306ms
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 227ms
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
6s 380ms
When
Click button advice in transport table "OWN_COLLECTION"
088ms
And
Set advice window in schedule
2s 708ms
And
Fill advice form
14s 620ms
And
Click advice save button and wait for advice form to disappear
30s 766ms
And
Go to "TRANSPORT_TABLE"
181ms
Then
Check advice data in SK API database "OWN_COLLECTION"
1s 144ms
After
Hooks.deleteTransportAfterTest()
079ms
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 271ms
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 307ms
When
Click button advice in transport table "CONTAINER"
096ms
And
Set advice window in schedule
2s 617ms
And
Fill advice form
14s 513ms
And
Click advice save button and wait for advice form to disappear
30s 686ms
And
Go to "TRANSPORT_TABLE"
176ms
Then
Check advice data in SK API database "CONTAINER"
4s 122ms
After
Hooks.deleteTransportAfterTest()
099ms
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 211ms
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
6s 840ms
When
Click button advice in transport table "TRANSPORT_ORDER"
072ms
And
Set advice window in schedule
2s 592ms
And
Fill advice form
14s 622ms
And
Click advice save button and wait for advice form to disappear
30s 722ms
And
Go to "TRANSPORT_TABLE"
259ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 053ms
After
Hooks.deleteTransportAfterTest()
100ms
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 147ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
003ms
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 307ms
When
Click button advice in transport table "CONTAINER"
094ms
And
Set advice window in schedule in the past
2s 602ms
And
Fill advice form
14s 611ms
And
Click advice save button to check error message
088ms
Then
Check if possible advice alert is displayed
019ms
After
Hooks.deleteTransportAfterTest()
086ms
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 305ms
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"
47s 969ms
And
Go to "TRANSPORT_TABLE"
187ms
When
Go to transport details "OWN_COLLECTION"
4s 457ms
And
Expand advice panel
080ms
And
Edit advice in transport details
13s 936ms
And
Fill arrival date field
2s 263ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 624ms
Then
Check advice data in database after edition "OWN_COLLECTION"
036ms
After
Hooks.deleteTransportAfterTest()
145ms
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_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
003ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
33s 396ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
47s 975ms
And
Go to "TRANSPORT_TABLE"
173ms
When
Go to transport details "CONTAINER"
4s 474ms
And
Expand advice panel
075ms
And
Edit advice in transport details
14s 028ms
And
Fill arrival date field
2s 268ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 621ms
Then
Check advice data in database after edition "CONTAINER"
036ms
After
Hooks.deleteTransportAfterTest()
125ms
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 282ms
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"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 318ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
47s 986ms
And
Go to "TRANSPORT_TABLE"
205ms
When
Go to transport details "TRANSPORT_ORDER"
4s 435ms
And
Expand advice panel
201ms
And
Edit advice in transport details
13s 954ms
And
Fill arrival date field
2s 281ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 676ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
036ms
After
Hooks.deleteTransportAfterTest()
133ms