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 230ms
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 424ms
When
Click button advice in transport table "CONTAINER"
114ms
And
Set advice window in schedule
2s 623ms
And
Fill advice form
14s 667ms
And
Click advice save button and wait for advice form to disappear
30s 781ms
And
Go to "TRANSPORT_TABLE"
166ms
And
Go to transport details "CONTAINER"
4s 477ms
Then
Check are advice values equals
2s 324ms
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 356ms
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"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 334ms
When
Click button advice in transport table "OWN_COLLECTION"
105ms
And
Set advice window in schedule
2s 511ms
And
Fill advice form
14s 677ms
And
Click advice save button and wait for advice form to disappear
30s 816ms
And
Go to "TRANSPORT_TABLE"
169ms
And
Go to transport details "OWN_COLLECTION"
4s 484ms
Then
Check are advice values equals
2s 333ms
After
Hooks.deleteTransportAfterTest()
143ms
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 208ms
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"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 233ms
When
Click button advice in transport table "TRANSPORT_ORDER"
127ms
And
Set advice window in schedule
2s 485ms
And
Fill advice form
14s 686ms
And
Click advice save button and wait for advice form to disappear
30s 802ms
And
Go to "TRANSPORT_TABLE"
215ms
And
Go to transport details "TRANSPORT_ORDER"
4s 470ms
Then
Check are advice values equals
2s 346ms
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 243ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
004ms
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 389ms
When
Click button advice in transport table "OWN_COLLECTION"
132ms
And
Set advice window in schedule
2s 530ms
And
Fill advice form
14s 642ms
And
Click advice save button and wait for advice form to disappear
30s 754ms
And
Go to "TRANSPORT_TABLE"
173ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 195ms
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 205ms
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"
119ms
And
Set advice window in schedule
2s 498ms
And
Fill advice form
14s 641ms
And
Click advice save button and wait for advice form to disappear
30s 717ms
And
Go to "TRANSPORT_TABLE"
191ms
Then
Check advice data in SK API database "CONTAINER"
4s 131ms
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 265ms
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 185ms
When
Click button advice in transport table "TRANSPORT_ORDER"
141ms
And
Set advice window in schedule
2s 480ms
And
Fill advice form
14s 583ms
And
Click advice save button and wait for advice form to disappear
30s 770ms
And
Go to "TRANSPORT_TABLE"
216ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 050ms
After
Hooks.deleteTransportAfterTest()
106ms
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 185ms
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"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 315ms
When
Click button advice in transport table "CONTAINER"
129ms
And
Set advice window in schedule in the past
2s 500ms
And
Fill advice form
14s 646ms
And
Click advice save button to check error message
102ms
Then
Check if possible advice alert is displayed
158ms
After
Hooks.deleteTransportAfterTest()
080ms
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 279ms
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"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
42s 502ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 048ms
And
Go to "TRANSPORT_TABLE"
193ms
When
Go to transport details "OWN_COLLECTION"
4s 456ms
And
Expand advice panel
109ms
And
Edit advice in transport details
14s 098ms
And
Fill arrival date field
2s 304ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 661ms
Then
Check advice data in database after edition "OWN_COLLECTION"
044ms
After
Hooks.deleteTransportAfterTest()
139ms
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_CONTAINER" "super-admin-skz"
001ms
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 398ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 211ms
And
Go to "TRANSPORT_TABLE"
193ms
When
Go to transport details "CONTAINER"
4s 506ms
And
Expand advice panel
113ms
And
Edit advice in transport details
14s 244ms
And
Fill arrival date field
2s 288ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 155ms
Then
Check advice data in database after edition "CONTAINER"
039ms
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_TRANSPORT_ORDER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
005ms
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 323ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 125ms
And
Go to "TRANSPORT_TABLE"
229ms
When
Go to transport details "TRANSPORT_ORDER"
4s 446ms
And
Expand advice panel
117ms
And
Edit advice in transport details
14s 094ms
And
Fill arrival date field
2s 307ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 635ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
039ms
After
Hooks.deleteTransportAfterTest()
120ms