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 262ms
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
54s 427ms
When
Click button advice in transport table "CONTAINER"
088ms
And
Set advice window in schedule
2s 700ms
And
Fill advice form
14s 607ms
And
Click advice save button and wait for advice form to disappear
30s 681ms
And
Go to "TRANSPORT_TABLE"
213ms
And
Go to transport details "CONTAINER"
4s 505ms
Then
Check are advice values equals
2s 306ms
After
Hooks.deleteTransportAfterTest()
128ms
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_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 429ms
When
Click button advice in transport table "OWN_COLLECTION"
098ms
And
Set advice window in schedule
2s 568ms
And
Fill advice form
14s 641ms
And
Click advice save button and wait for advice form to disappear
30s 732ms
And
Go to "TRANSPORT_TABLE"
199ms
And
Go to transport details "OWN_COLLECTION"
4s 435ms
Then
Check are advice values equals
2s 334ms
After
Hooks.deleteTransportAfterTest()
121ms
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 462ms
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 285ms
When
Click button advice in transport table "TRANSPORT_ORDER"
090ms
And
Set advice window in schedule
2s 613ms
And
Fill advice form
14s 613ms
And
Click advice save button and wait for advice form to disappear
30s 697ms
And
Go to "TRANSPORT_TABLE"
253ms
And
Go to transport details "TRANSPORT_ORDER"
4s 383ms
Then
Check are advice values equals
2s 317ms
After
Hooks.deleteTransportAfterTest()
107ms
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 455ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
3s 390ms
When
Click button advice in transport table "OWN_COLLECTION"
132ms
And
Set advice window in schedule
2s 600ms
And
Fill advice form
14s 593ms
And
Click advice save button and wait for advice form to disappear
30s 720ms
And
Go to "TRANSPORT_TABLE"
219ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 186ms
After
Hooks.deleteTransportAfterTest()
126ms
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 366ms
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 345ms
When
Click button advice in transport table "CONTAINER"
107ms
And
Set advice window in schedule
2s 617ms
And
Fill advice form
14s 629ms
And
Click advice save button and wait for advice form to disappear
30s 728ms
And
Go to "TRANSPORT_TABLE"
190ms
Then
Check advice data in SK API database "CONTAINER"
4s 138ms
After
Hooks.deleteTransportAfterTest()
142ms
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 257ms
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 233ms
When
Click button advice in transport table "TRANSPORT_ORDER"
102ms
And
Set advice window in schedule
2s 642ms
And
Fill advice form
14s 543ms
And
Click advice save button and wait for advice form to disappear
30s 731ms
And
Go to "TRANSPORT_TABLE"
228ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 043ms
After
Hooks.deleteTransportAfterTest()
133ms
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 288ms
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 375ms
When
Click button advice in transport table "CONTAINER"
080ms
And
Set advice window in schedule in the past
2s 644ms
And
Fill advice form
14s 650ms
And
Click advice save button to check error message
098ms
Then
Check if possible advice alert is displayed
016ms
After
Hooks.deleteTransportAfterTest()
109ms
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 280ms
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
39s 519ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 080ms
And
Go to "TRANSPORT_TABLE"
198ms
When
Go to transport details "OWN_COLLECTION"
4s 492ms
And
Expand advice panel
107ms
And
Edit advice in transport details
14s 109ms
And
Fill arrival date field
2s 301ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 123ms
Then
Check advice data in database after edition "OWN_COLLECTION"
022ms
After
Hooks.deleteTransportAfterTest()
116ms
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 127ms
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
33s 451ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 117ms
And
Go to "TRANSPORT_TABLE"
214ms
When
Go to transport details "CONTAINER"
4s 528ms
And
Expand advice panel
107ms
And
Edit advice in transport details
13s 990ms
And
Fill arrival date field
2s 287ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 597ms
Then
Check advice data in database after edition "CONTAINER"
035ms
After
Hooks.deleteTransportAfterTest()
132ms
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 155ms
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 "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 356ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 103ms
And
Go to "TRANSPORT_TABLE"
237ms
When
Go to transport details "TRANSPORT_ORDER"
4s 474ms
And
Expand advice panel
111ms
And
Edit advice in transport details
14s 005ms
And
Fill arrival date field
2s 296ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 661ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
041ms
After
Hooks.deleteTransportAfterTest()
131ms