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_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 415ms
When
Click button advice in transport table "CONTAINER"
108ms
And
Set advice window in schedule
2s 773ms
And
Fill advice form
14s 784ms
And
Click advice save button and wait for advice form to disappear
30s 663ms
And
Go to "TRANSPORT_TABLE"
188ms
And
Go to transport details "CONTAINER"
4s 535ms
Then
Check are advice values equals
2s 351ms
After
Hooks.deleteTransportAfterTest()
119ms
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 225ms
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 405ms
When
Click button advice in transport table "OWN_COLLECTION"
127ms
And
Set advice window in schedule
2s 557ms
And
Fill advice form
14s 761ms
And
Click advice save button and wait for advice form to disappear
30s 719ms
And
Go to "TRANSPORT_TABLE"
186ms
And
Go to transport details "OWN_COLLECTION"
4s 466ms
Then
Check are advice values equals
2s 329ms
After
Hooks.deleteTransportAfterTest()
154ms
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 231ms
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 237ms
When
Click button advice in transport table "TRANSPORT_ORDER"
112ms
And
Set advice window in schedule
2s 557ms
And
Fill advice form
14s 686ms
And
Click advice save button and wait for advice form to disappear
30s 713ms
And
Go to "TRANSPORT_TABLE"
256ms
And
Go to transport details "TRANSPORT_ORDER"
4s 483ms
Then
Check are advice values equals
2s 322ms
After
Hooks.deleteTransportAfterTest()
131ms
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 214ms
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"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
6s 430ms
When
Click button advice in transport table "OWN_COLLECTION"
112ms
And
Set advice window in schedule
2s 620ms
And
Fill advice form
14s 852ms
And
Click advice save button and wait for advice form to disappear
31s 237ms
And
Go to "TRANSPORT_TABLE"
185ms
Then
Check advice data in SK API database "OWN_COLLECTION"
147ms
After
Hooks.deleteTransportAfterTest()
111ms
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_CONTAINER" "super-admin-skz"
001ms
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 357ms
When
Click button advice in transport table "CONTAINER"
116ms
And
Set advice window in schedule
2s 513ms
And
Fill advice form
14s 760ms
And
Click advice save button and wait for advice form to disappear
30s 692ms
And
Go to "TRANSPORT_TABLE"
204ms
Then
Check advice data in SK API database "CONTAINER"
2s 111ms
After
Hooks.deleteTransportAfterTest()
136ms
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 234ms
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 819ms
When
Click button advice in transport table "TRANSPORT_ORDER"
112ms
And
Set advice window in schedule
2s 534ms
And
Fill advice form
14s 757ms
And
Click advice save button and wait for advice form to disappear
30s 731ms
And
Go to "TRANSPORT_TABLE"
241ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 047ms
After
Hooks.deleteTransportAfterTest()
110ms
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 194ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
011ms
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 356ms
When
Click button advice in transport table "CONTAINER"
104ms
And
Set advice window in schedule in the past
2s 580ms
And
Fill advice form
14s 757ms
And
Click advice save button to check error message
069ms
Then
Check if possible advice alert is displayed
016ms
After
Hooks.deleteTransportAfterTest()
101ms
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 168ms
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
39s 497ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 200ms
And
Go to "TRANSPORT_TABLE"
205ms
When
Go to transport details "OWN_COLLECTION"
4s 491ms
And
Expand advice panel
151ms
And
Edit advice in transport details
14s 084ms
And
Fill arrival date field
2s 296ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 647ms
Then
Check advice data in database after edition "OWN_COLLECTION"
043ms
After
Hooks.deleteTransportAfterTest()
138ms
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 237ms
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"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
39s 447ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 944ms
And
Go to "TRANSPORT_TABLE"
221ms
When
Go to transport details "CONTAINER"
4s 536ms
And
Expand advice panel
118ms
And
Edit advice in transport details
14s 143ms
And
Fill arrival date field
2s 311ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 610ms
Then
Check advice data in database after edition "CONTAINER"
035ms
After
Hooks.deleteTransportAfterTest()
200ms
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 306ms
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
27s 323ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 148ms
And
Go to "TRANSPORT_TABLE"
250ms
When
Go to transport details "TRANSPORT_ORDER"
4s 483ms
And
Expand advice panel
100ms
And
Edit advice in transport details
14s 110ms
And
Fill arrival date field
2s 289ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 606ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
037ms
After
Hooks.deleteTransportAfterTest()
119ms