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"
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 413ms
When
Click button advice in transport table "CONTAINER"
110ms
And
Set advice window in schedule
2s 665ms
And
Fill advice form
14s 860ms
And
Click advice save button and wait for advice form to disappear
30s 780ms
And
Go to "TRANSPORT_TABLE"
215ms
And
Go to transport details "CONTAINER"
4s 514ms
Then
Check are advice values equals
2s 349ms
After
Hooks.deleteTransportAfterTest()
102ms
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"
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 395ms
When
Click button advice in transport table "OWN_COLLECTION"
119ms
And
Set advice window in schedule
2s 558ms
And
Fill advice form
14s 732ms
And
Click advice save button and wait for advice form to disappear
30s 792ms
And
Go to "TRANSPORT_TABLE"
212ms
And
Go to transport details "OWN_COLLECTION"
4s 487ms
Then
Check are advice values equals
2s 308ms
After
Hooks.deleteTransportAfterTest()
149ms
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 217ms
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 220ms
When
Click button advice in transport table "TRANSPORT_ORDER"
098ms
And
Set advice window in schedule
2s 569ms
And
Fill advice form
14s 771ms
And
Click advice save button and wait for advice form to disappear
30s 713ms
And
Go to "TRANSPORT_TABLE"
251ms
And
Go to transport details "TRANSPORT_ORDER"
4s 484ms
Then
Check are advice values equals
2s 367ms
After
Hooks.deleteTransportAfterTest()
112ms
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"
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 396ms
When
Click button advice in transport table "OWN_COLLECTION"
131ms
And
Set advice window in schedule
2s 547ms
And
Fill advice form
14s 758ms
And
Click advice save button and wait for advice form to disappear
30s 739ms
And
Go to "TRANSPORT_TABLE"
206ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 180ms
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 221ms
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 339ms
When
Click button advice in transport table "CONTAINER"
131ms
And
Set advice window in schedule
2s 560ms
And
Fill advice form
14s 823ms
And
Click advice save button and wait for advice form to disappear
30s 754ms
And
Go to "TRANSPORT_TABLE"
196ms
Then
Check advice data in SK API database "CONTAINER"
4s 104ms
After
Hooks.deleteTransportAfterTest()
101ms
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 303ms
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 241ms
When
Click button advice in transport table "TRANSPORT_ORDER"
124ms
And
Set advice window in schedule
2s 531ms
And
Fill advice form
14s 794ms
And
Click advice save button and wait for advice form to disappear
30s 738ms
And
Go to "TRANSPORT_TABLE"
254ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 043ms
After
Hooks.deleteTransportAfterTest()
092ms
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 210ms
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
9s 351ms
When
Click button advice in transport table "CONTAINER"
115ms
And
Set advice window in schedule in the past
2s 577ms
And
Fill advice form
14s 738ms
And
Click advice save button to check error message
089ms
Then
Check if possible advice alert is displayed
019ms
After
Hooks.deleteTransportAfterTest()
107ms
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 229ms
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
39s 480ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 173ms
And
Go to "TRANSPORT_TABLE"
202ms
When
Go to transport details "OWN_COLLECTION"
4s 523ms
And
Expand advice panel
116ms
And
Edit advice in transport details
14s 130ms
And
Fill arrival date field
2s 300ms
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"
037ms
After
Hooks.deleteTransportAfterTest()
124ms
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 233ms
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 418ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 258ms
And
Go to "TRANSPORT_TABLE"
219ms
When
Go to transport details "CONTAINER"
4s 564ms
And
Expand advice panel
122ms
And
Edit advice in transport details
14s 124ms
And
Fill arrival date field
2s 300ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 627ms
Then
Check advice data in database after edition "CONTAINER"
040ms
After
Hooks.deleteTransportAfterTest()
133ms
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 252ms
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"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 385ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 258ms
And
Go to "TRANSPORT_TABLE"
250ms
When
Go to transport details "TRANSPORT_ORDER"
4s 490ms
And
Expand advice panel
120ms
And
Edit advice in transport details
14s 073ms
And
Fill arrival date field
2s 296ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 652ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
041ms
After
Hooks.deleteTransportAfterTest()
133ms