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 264ms
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
54s 418ms
When
Click button advice in transport table "CONTAINER"
128ms
And
Set advice window in schedule
2s 739ms
And
Fill advice form
14s 579ms
And
Click advice save button and wait for advice form to disappear
31s 311ms
And
Go to "TRANSPORT_TABLE"
172ms
And
Go to transport details "CONTAINER"
4s 482ms
Then
Check are advice values equals
2s 335ms
After
Hooks.deleteTransportAfterTest()
189ms
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 300ms
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"
002ms
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"
112ms
And
Set advice window in schedule
2s 513ms
And
Fill advice form
14s 496ms
And
Click advice save button and wait for advice form to disappear
30s 727ms
And
Go to "TRANSPORT_TABLE"
182ms
And
Go to transport details "OWN_COLLECTION"
4s 505ms
Then
Check are advice values equals
2s 317ms
After
Hooks.deleteTransportAfterTest()
141ms
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 214ms
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 240ms
When
Click button advice in transport table "TRANSPORT_ORDER"
117ms
And
Set advice window in schedule
2s 504ms
And
Fill advice form
14s 633ms
And
Click advice save button and wait for advice form to disappear
30s 721ms
And
Go to "TRANSPORT_TABLE"
207ms
And
Go to transport details "TRANSPORT_ORDER"
4s 468ms
Then
Check are advice values equals
2s 326ms
After
Hooks.deleteTransportAfterTest()
125ms
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 218ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
3s 392ms
When
Click button advice in transport table "OWN_COLLECTION"
121ms
And
Set advice window in schedule
2s 526ms
And
Fill advice form
14s 546ms
And
Click advice save button and wait for advice form to disappear
30s 815ms
And
Go to "TRANSPORT_TABLE"
203ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 171ms
After
Hooks.deleteTransportAfterTest()
118ms
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 224ms
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 319ms
When
Click button advice in transport table "CONTAINER"
123ms
And
Set advice window in schedule
2s 508ms
And
Fill advice form
14s 632ms
And
Click advice save button and wait for advice form to disappear
31s 290ms
And
Go to "TRANSPORT_TABLE"
169ms
Then
Check advice data in SK API database "CONTAINER"
3s 156ms
After
Hooks.deleteTransportAfterTest()
163ms
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 223ms
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
6s 212ms
When
Click button advice in transport table "TRANSPORT_ORDER"
115ms
And
Set advice window in schedule
2s 582ms
And
Fill advice form
14s 652ms
And
Click advice save button and wait for advice form to disappear
30s 694ms
And
Go to "TRANSPORT_TABLE"
193ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 045ms
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 233ms
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"
110ms
And
Set advice window in schedule in the past
2s 526ms
And
Fill advice form
14s 624ms
And
Click advice save button to check error message
087ms
Then
Check if possible advice alert is displayed
143ms
After
Hooks.deleteTransportAfterTest()
106ms
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 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 "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
42s 468ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 149ms
And
Go to "TRANSPORT_TABLE"
182ms
When
Go to transport details "OWN_COLLECTION"
4s 479ms
And
Expand advice panel
099ms
And
Edit advice in transport details
14s 023ms
And
Fill arrival date field
2s 284ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 623ms
Then
Check advice data in database after edition "OWN_COLLECTION"
043ms
After
Hooks.deleteTransportAfterTest()
5s 046ms
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 275ms
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
30s 361ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 769ms
And
Go to "TRANSPORT_TABLE"
145ms
When
Go to transport details "CONTAINER"
4s 478ms
And
Expand advice panel
115ms
And
Edit advice in transport details
14s 052ms
And
Fill arrival date field
2s 280ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 154ms
Then
Check advice data in database after edition "CONTAINER"
035ms
After
Hooks.deleteTransportAfterTest()
162ms
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 285ms
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
30s 310ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 698ms
And
Go to "TRANSPORT_TABLE"
204ms
When
Go to transport details "TRANSPORT_ORDER"
4s 498ms
And
Expand advice panel
117ms
And
Edit advice in transport details
14s 061ms
And
Fill arrival date field
2s 269ms
And
Click "save-transport-and-close" save button and wait for form to disappear
20s 882ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
036ms
After
Hooks.deleteTransportAfterTest()
200ms