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 187ms
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 422ms
When
Click button advice in transport table "CONTAINER"
137ms
And
Set advice window in schedule
2s 627ms
And
Fill advice form
14s 689ms
And
Click advice save button and wait for advice form to disappear
30s 768ms
And
Go to "TRANSPORT_TABLE"
174ms
And
Go to transport details "CONTAINER"
4s 514ms
Then
Check are advice values equals
2s 343ms
After
Hooks.deleteTransportAfterTest()
146ms
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 210ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
3s 380ms
When
Click button advice in transport table "OWN_COLLECTION"
137ms
And
Set advice window in schedule
2s 512ms
And
Fill advice form
14s 660ms
And
Click advice save button and wait for advice form to disappear
30s 779ms
And
Go to "TRANSPORT_TABLE"
167ms
And
Go to transport details "OWN_COLLECTION"
4s 473ms
Then
Check are advice values equals
2s 318ms
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 207ms
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 218ms
When
Click button advice in transport table "TRANSPORT_ORDER"
124ms
And
Set advice window in schedule
2s 531ms
And
Fill advice form
14s 635ms
And
Click advice save button and wait for advice form to disappear
30s 771ms
And
Go to "TRANSPORT_TABLE"
222ms
And
Go to transport details "TRANSPORT_ORDER"
4s 489ms
Then
Check are advice values equals
2s 356ms
After
Hooks.deleteTransportAfterTest()
119ms
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 213ms
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"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 382ms
When
Click button advice in transport table "OWN_COLLECTION"
130ms
And
Set advice window in schedule
2s 543ms
And
Fill advice form
14s 618ms
And
Click advice save button and wait for advice form to disappear
30s 679ms
And
Go to "TRANSPORT_TABLE"
175ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 184ms
After
Hooks.deleteTransportAfterTest()
147ms
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 216ms
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 340ms
When
Click button advice in transport table "CONTAINER"
111ms
And
Set advice window in schedule
2s 494ms
And
Fill advice form
14s 609ms
And
Click advice save button and wait for advice form to disappear
30s 730ms
And
Go to "TRANSPORT_TABLE"
191ms
Then
Check advice data in SK API database "CONTAINER"
4s 123ms
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 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 231ms
When
Click button advice in transport table "TRANSPORT_ORDER"
126ms
And
Set advice window in schedule
2s 498ms
And
Fill advice form
14s 633ms
And
Click advice save button and wait for advice form to disappear
30s 775ms
And
Go to "TRANSPORT_TABLE"
200ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 053ms
After
Hooks.deleteTransportAfterTest()
197ms
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 229ms
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
6s 308ms
When
Click button advice in transport table "CONTAINER"
125ms
And
Set advice window in schedule in the past
2s 496ms
And
Fill advice form
14s 527ms
And
Click advice save button to check error message
093ms
Then
Check if possible advice alert is displayed
084ms
After
Hooks.deleteTransportAfterTest()
091ms
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_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
42s 480ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 049ms
And
Go to "TRANSPORT_TABLE"
201ms
When
Go to transport details "OWN_COLLECTION"
4s 472ms
And
Expand advice panel
109ms
And
Edit advice in transport details
14s 097ms
And
Fill arrival date field
2s 307ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 619ms
Then
Check advice data in database after edition "OWN_COLLECTION"
041ms
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 192ms
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"
002ms
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 127ms
And
Go to "TRANSPORT_TABLE"
163ms
When
Go to transport details "CONTAINER"
4s 491ms
And
Expand advice panel
117ms
And
Edit advice in transport details
14s 087ms
And
Fill arrival date field
2s 288ms
And
Click "save-transport-and-close" save button and wait for form to disappear
664ms
Then
Check advice data in database after edition "CONTAINER"
027ms
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 214ms
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"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
48s 337ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 166ms
And
Go to "TRANSPORT_TABLE"
223ms
When
Go to transport details "TRANSPORT_ORDER"
4s 502ms
And
Expand advice panel
122ms
And
Edit advice in transport details
14s 039ms
And
Fill arrival date field
2s 303ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 109ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
032ms
After
Hooks.deleteTransportAfterTest()
142ms