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 263ms
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"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
54s 467ms
When
Click button advice in transport table "CONTAINER"
083ms
And
Set advice window in schedule
2s 736ms
And
Fill advice form
14s 706ms
And
Click advice save button and wait for advice form to disappear
30s 696ms
And
Go to "TRANSPORT_TABLE"
189ms
And
Go to transport details "CONTAINER"
4s 436ms
Then
Check are advice values equals
2s 334ms
After
Hooks.deleteTransportAfterTest()
168ms
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 261ms
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 990ms
When
Click button advice in transport table "OWN_COLLECTION"
103ms
And
Set advice window in schedule
2s 696ms
And
Fill advice form
14s 579ms
And
Click advice save button and wait for advice form to disappear
30s 685ms
And
Go to "TRANSPORT_TABLE"
162ms
And
Go to transport details "OWN_COLLECTION"
4s 452ms
Then
Check are advice values equals
2s 320ms
After
Hooks.deleteTransportAfterTest()
127ms
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 263ms
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 289ms
When
Click button advice in transport table "TRANSPORT_ORDER"
079ms
And
Set advice window in schedule
2s 656ms
And
Fill advice form
14s 615ms
And
Click advice save button and wait for advice form to disappear
30s 712ms
And
Go to "TRANSPORT_TABLE"
204ms
And
Go to transport details "TRANSPORT_ORDER"
4s 395ms
Then
Check are advice values equals
2s 324ms
After
Hooks.deleteTransportAfterTest()
167ms
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_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
3s 473ms
When
Click button advice in transport table "OWN_COLLECTION"
090ms
And
Set advice window in schedule
2s 702ms
And
Fill advice form
14s 609ms
And
Click advice save button and wait for advice form to disappear
30s 712ms
And
Go to "TRANSPORT_TABLE"
154ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 190ms
After
Hooks.deleteTransportAfterTest()
128ms
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 285ms
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 349ms
When
Click button advice in transport table "CONTAINER"
104ms
And
Set advice window in schedule
2s 616ms
And
Fill advice form
14s 605ms
And
Click advice save button and wait for advice form to disappear
30s 719ms
And
Go to "TRANSPORT_TABLE"
183ms
Then
Check advice data in SK API database "CONTAINER"
4s 113ms
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 250ms
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 872ms
When
Click button advice in transport table "TRANSPORT_ORDER"
083ms
And
Set advice window in schedule
2s 645ms
And
Fill advice form
14s 650ms
And
Click advice save button and wait for advice form to disappear
30s 745ms
And
Go to "TRANSPORT_TABLE"
214ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 037ms
After
Hooks.deleteTransportAfterTest()
131ms
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 245ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
9s 382ms
When
Click button advice in transport table "CONTAINER"
080ms
And
Set advice window in schedule in the past
2s 722ms
And
Fill advice form
14s 717ms
And
Click advice save button to check error message
095ms
Then
Check if possible advice alert is displayed
021ms
After
Hooks.deleteTransportAfterTest()
128ms
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 514ms
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 "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
39s 539ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 191ms
And
Go to "TRANSPORT_TABLE"
207ms
When
Go to transport details "OWN_COLLECTION"
4s 455ms
And
Expand advice panel
103ms
And
Edit advice in transport details
13s 921ms
And
Fill arrival date field
2s 265ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 636ms
Then
Check advice data in database after edition "OWN_COLLECTION"
035ms
After
Hooks.deleteTransportAfterTest()
166ms
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 308ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
33s 425ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 137ms
And
Go to "TRANSPORT_TABLE"
188ms
When
Go to transport details "CONTAINER"
4s 449ms
And
Expand advice panel
119ms
And
Edit advice in transport details
14s 021ms
And
Fill arrival date field
2s 261ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 170ms
Then
Check advice data in database after edition "CONTAINER"
034ms
After
Hooks.deleteTransportAfterTest()
142ms
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 321ms
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 379ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 154ms
And
Go to "TRANSPORT_TABLE"
247ms
When
Go to transport details "TRANSPORT_ORDER"
4s 503ms
And
Expand advice panel
109ms
And
Edit advice in transport details
13s 968ms
And
Fill arrival date field
2s 265ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 579ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
030ms
After
Hooks.deleteTransportAfterTest()
159ms