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_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 376ms
When
Click button advice in transport table "CONTAINER"
131ms
And
Set advice window in schedule
2s 608ms
And
Fill advice form
14s 824ms
And
Click advice save button and wait for advice form to disappear
30s 748ms
And
Go to "TRANSPORT_TABLE"
186ms
And
Go to transport details "CONTAINER"
4s 528ms
Then
Check are advice values equals
2s 319ms
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 241ms
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 387ms
When
Click button advice in transport table "OWN_COLLECTION"
123ms
And
Set advice window in schedule
2s 523ms
And
Fill advice form
14s 679ms
And
Click advice save button and wait for advice form to disappear
30s 731ms
And
Go to "TRANSPORT_TABLE"
185ms
And
Go to transport details "OWN_COLLECTION"
4s 494ms
Then
Check are advice values equals
2s 324ms
After
Hooks.deleteTransportAfterTest()
113ms
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 241ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id
3s 213ms
When
Click button advice in transport table "TRANSPORT_ORDER"
127ms
And
Set advice window in schedule
2s 540ms
And
Fill advice form
14s 763ms
And
Click advice save button and wait for advice form to disappear
30s 746ms
And
Go to "TRANSPORT_TABLE"
201ms
And
Go to transport details "TRANSPORT_ORDER"
4s 480ms
Then
Check are advice values equals
2s 322ms
After
Hooks.deleteTransportAfterTest()
115ms
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 226ms
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 339ms
When
Click button advice in transport table "OWN_COLLECTION"
132ms
And
Set advice window in schedule
2s 510ms
And
Fill advice form
14s 721ms
And
Click advice save button and wait for advice form to disappear
30s 756ms
And
Go to "TRANSPORT_TABLE"
179ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 168ms
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 386ms
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 297ms
When
Click button advice in transport table "CONTAINER"
128ms
And
Set advice window in schedule
2s 505ms
And
Fill advice form
14s 817ms
And
Click advice save button and wait for advice form to disappear
30s 801ms
And
Go to "TRANSPORT_TABLE"
168ms
Then
Check advice data in SK API database "CONTAINER"
3s 101ms
After
Hooks.deleteTransportAfterTest()
098ms
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 302ms
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"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 795ms
When
Click button advice in transport table "TRANSPORT_ORDER"
132ms
And
Set advice window in schedule
2s 526ms
And
Fill advice form
14s 873ms
And
Click advice save button and wait for advice form to disappear
30s 762ms
And
Go to "TRANSPORT_TABLE"
207ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 048ms
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 205ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
9s 306ms
When
Click button advice in transport table "CONTAINER"
128ms
And
Set advice window in schedule in the past
2s 544ms
And
Fill advice form
14s 785ms
And
Click advice save button to check error message
100ms
Then
Check if possible advice alert is displayed
022ms
After
Hooks.deleteTransportAfterTest()
112ms
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 248ms
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 435ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 236ms
And
Go to "TRANSPORT_TABLE"
193ms
When
Go to transport details "OWN_COLLECTION"
4s 540ms
And
Expand advice panel
117ms
And
Edit advice in transport details
14s 107ms
And
Fill arrival date field
2s 310ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 628ms
Then
Check advice data in database after edition "OWN_COLLECTION"
036ms
After
Hooks.deleteTransportAfterTest()
123ms
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 204ms
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"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
33s 337ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 150ms
And
Go to "TRANSPORT_TABLE"
193ms
When
Go to transport details "CONTAINER"
4s 547ms
And
Expand advice panel
110ms
And
Edit advice in transport details
14s 094ms
And
Fill arrival date field
2s 306ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 631ms
Then
Check advice data in database after edition "CONTAINER"
036ms
After
Hooks.deleteTransportAfterTest()
131ms
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 278ms
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 307ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 188ms
And
Go to "TRANSPORT_TABLE"
204ms
When
Go to transport details "TRANSPORT_ORDER"
4s 476ms
And
Expand advice panel
112ms
And
Edit advice in transport details
14s 087ms
And
Fill arrival date field
2s 312ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 631ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
039ms
After
Hooks.deleteTransportAfterTest()
121ms