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_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 380ms
When
Click button advice in transport table "CONTAINER"
098ms
And
Set advice window in schedule
2s 715ms
And
Fill advice form
14s 745ms
And
Click advice save button and wait for advice form to disappear
31s 277ms
And
Go to "TRANSPORT_TABLE"
173ms
And
Go to transport details "CONTAINER"
4s 473ms
Then
Check are advice values equals
2s 343ms
After
Hooks.deleteTransportAfterTest()
142ms
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 236ms
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
1m 504ms
When
Click button advice in transport table "OWN_COLLECTION"
113ms
And
Set advice window in schedule
2s 535ms
And
Fill advice form
14s 662ms
And
Click advice save button and wait for advice form to disappear
30s 690ms
And
Go to "TRANSPORT_TABLE"
184ms
And
Go to transport details "OWN_COLLECTION"
4s 485ms
Then
Check are advice values equals
2s 296ms
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 193ms
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
3s 816ms
When
Click button advice in transport table "TRANSPORT_ORDER"
139ms
And
Set advice window in schedule
2s 590ms
And
Fill advice form
14s 664ms
And
Click advice save button and wait for advice form to disappear
30s 742ms
And
Go to "TRANSPORT_TABLE"
231ms
And
Go to transport details "TRANSPORT_ORDER"
4s 479ms
Then
Check are advice values equals
2s 301ms
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 252ms
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 373ms
When
Click button advice in transport table "OWN_COLLECTION"
128ms
And
Set advice window in schedule
2s 499ms
And
Fill advice form
14s 561ms
And
Click advice save button and wait for advice form to disappear
30s 723ms
And
Go to "TRANSPORT_TABLE"
170ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 179ms
After
Hooks.deleteTransportAfterTest()
109ms
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 174ms
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 326ms
When
Click button advice in transport table "CONTAINER"
123ms
And
Set advice window in schedule
2s 490ms
And
Fill advice form
14s 611ms
And
Click advice save button and wait for advice form to disappear
30s 767ms
And
Go to "TRANSPORT_TABLE"
180ms
Then
Check advice data in SK API database "CONTAINER"
4s 112ms
After
Hooks.deleteTransportAfterTest()
203ms
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 143ms
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 830ms
When
Click button advice in transport table "TRANSPORT_ORDER"
096ms
And
Set advice window in schedule
6s 986ms
And
Fill advice form
14s 687ms
And
Click advice save button and wait for advice form to disappear
31s 275ms
And
Go to "TRANSPORT_TABLE"
197ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
029ms
After
Hooks.deleteTransportAfterTest()
107ms
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 212ms
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 297ms
When
Click button advice in transport table "CONTAINER"
124ms
And
Set advice window in schedule in the past
2s 534ms
And
Fill advice form
14s 605ms
And
Click advice save button to check error message
093ms
Then
Check if possible advice alert is displayed
140ms
After
Hooks.deleteTransportAfterTest()
100ms
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 239ms
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
42s 449ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 150ms
And
Go to "TRANSPORT_TABLE"
161ms
When
Go to transport details "OWN_COLLECTION"
4s 406ms
And
Expand advice panel
110ms
And
Edit advice in transport details
14s 072ms
And
Fill arrival date field
2s 322ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 151ms
Then
Check advice data in database after edition "OWN_COLLECTION"
039ms
After
Hooks.deleteTransportAfterTest()
152ms
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 202ms
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"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
33s 440ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 142ms
And
Go to "TRANSPORT_TABLE"
176ms
When
Go to transport details "CONTAINER"
4s 485ms
And
Expand advice panel
123ms
And
Edit advice in transport details
14s 060ms
And
Fill arrival date field
2s 274ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 626ms
Then
Check advice data in database after edition "CONTAINER"
041ms
After
Hooks.deleteTransportAfterTest()
120ms
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"
004ms
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
30s 916ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 269ms
And
Go to "TRANSPORT_TABLE"
202ms
When
Go to transport details "TRANSPORT_ORDER"
4s 464ms
And
Expand advice panel
086ms
And
Edit advice in transport details
14s 049ms
And
Fill arrival date field
2s 292ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 666ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
032ms
After
Hooks.deleteTransportAfterTest()
110ms