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_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 376ms
When
Click button advice in transport table "CONTAINER"
129ms
And
Set advice window in schedule
2s 653ms
And
Fill advice form
14s 765ms
And
Click advice save button and wait for advice form to disappear
30s 766ms
And
Go to "TRANSPORT_TABLE"
214ms
And
Go to transport details "CONTAINER"
4s 528ms
Then
Check are advice values equals
2s 344ms
After
Hooks.deleteTransportAfterTest()
110ms
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 220ms
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 357ms
When
Click button advice in transport table "OWN_COLLECTION"
140ms
And
Set advice window in schedule
2s 532ms
And
Fill advice form
14s 778ms
And
Click advice save button and wait for advice form to disappear
30s 764ms
And
Go to "TRANSPORT_TABLE"
197ms
And
Go to transport details "OWN_COLLECTION"
4s 451ms
Then
Check are advice values equals
2s 340ms
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 176ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
003ms
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 201ms
When
Click button advice in transport table "TRANSPORT_ORDER"
129ms
And
Set advice window in schedule
2s 566ms
And
Fill advice form
14s 764ms
And
Click advice save button and wait for advice form to disappear
30s 725ms
And
Go to "TRANSPORT_TABLE"
226ms
And
Go to transport details "TRANSPORT_ORDER"
4s 476ms
Then
Check are advice values equals
2s 329ms
After
Hooks.deleteTransportAfterTest()
135ms
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 204ms
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 374ms
When
Click button advice in transport table "OWN_COLLECTION"
110ms
And
Set advice window in schedule
2s 517ms
And
Fill advice form
14s 778ms
And
Click advice save button and wait for advice form to disappear
30s 741ms
And
Go to "TRANSPORT_TABLE"
223ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 178ms
After
Hooks.deleteTransportAfterTest()
134ms
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 201ms
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
6s 313ms
When
Click button advice in transport table "CONTAINER"
120ms
And
Set advice window in schedule
2s 575ms
And
Fill advice form
14s 764ms
And
Click advice save button and wait for advice form to disappear
30s 790ms
And
Go to "TRANSPORT_TABLE"
193ms
Then
Check advice data in SK API database "CONTAINER"
4s 105ms
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 407ms
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 222ms
When
Click button advice in transport table "TRANSPORT_ORDER"
107ms
And
Set advice window in schedule
2s 524ms
And
Fill advice form
14s 788ms
And
Click advice save button and wait for advice form to disappear
30s 741ms
And
Go to "TRANSPORT_TABLE"
248ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 036ms
After
Hooks.deleteTransportAfterTest()
105ms
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 194ms
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
9s 330ms
When
Click button advice in transport table "CONTAINER"
139ms
And
Set advice window in schedule in the past
2s 568ms
And
Fill advice form
14s 753ms
And
Click advice save button to check error message
085ms
Then
Check if possible advice alert is displayed
021ms
After
Hooks.deleteTransportAfterTest()
122ms
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 244ms
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"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
39s 441ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 371ms
And
Go to "TRANSPORT_TABLE"
201ms
When
Go to transport details "OWN_COLLECTION"
4s 475ms
And
Expand advice panel
116ms
And
Edit advice in transport details
14s 151ms
And
Fill arrival date field
2s 300ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 620ms
Then
Check advice data in database after edition "OWN_COLLECTION"
037ms
After
Hooks.deleteTransportAfterTest()
144ms
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 175ms
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 372ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 324ms
And
Go to "TRANSPORT_TABLE"
214ms
When
Go to transport details "CONTAINER"
4s 523ms
And
Expand advice panel
115ms
And
Edit advice in transport details
14s 130ms
And
Fill arrival date field
2s 322ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 658ms
Then
Check advice data in database after edition "CONTAINER"
039ms
After
Hooks.deleteTransportAfterTest()
141ms
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 238ms
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 "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 297ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 222ms
And
Go to "TRANSPORT_TABLE"
237ms
When
Go to transport details "TRANSPORT_ORDER"
4s 487ms
And
Expand advice panel
123ms
And
Edit advice in transport details
14s 109ms
And
Fill arrival date field
2s 308ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 585ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
037ms
After
Hooks.deleteTransportAfterTest()
117ms