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 259ms
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 400ms
When
Click button advice in transport table "CONTAINER"
130ms
And
Set advice window in schedule
2s 802ms
And
Fill advice form
14s 892ms
And
Click advice save button and wait for advice form to disappear
31s 262ms
And
Go to "TRANSPORT_TABLE"
179ms
And
Go to transport details "CONTAINER"
4s 507ms
Then
Check are advice values equals
2s 345ms
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 237ms
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 343ms
When
Click button advice in transport table "OWN_COLLECTION"
139ms
And
Set advice window in schedule
2s 557ms
And
Fill advice form
14s 705ms
And
Click advice save button and wait for advice form to disappear
30s 764ms
And
Go to "TRANSPORT_TABLE"
147ms
And
Go to transport details "OWN_COLLECTION"
4s 470ms
Then
Check are advice values equals
2s 332ms
After
Hooks.deleteTransportAfterTest()
139ms
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 229ms
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
3s 206ms
When
Click button advice in transport table "TRANSPORT_ORDER"
116ms
And
Set advice window in schedule
2s 501ms
And
Fill advice form
14s 806ms
And
Click advice save button and wait for advice form to disappear
15s 788ms
And
Go to "TRANSPORT_TABLE"
195ms
And
Go to transport details "TRANSPORT_ORDER"
4s 479ms
Then
Check are advice values equals
2s 329ms
After
Hooks.deleteTransportAfterTest()
128ms
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 246ms
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
18s 398ms
When
Click button advice in transport table "OWN_COLLECTION"
128ms
And
Set advice window in schedule
2s 492ms
And
Fill advice form
14s 801ms
And
Click advice save button and wait for advice form to disappear
30s 731ms
And
Go to "TRANSPORT_TABLE"
171ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 164ms
After
Hooks.deleteTransportAfterTest()
141ms
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 242ms
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"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 276ms
When
Click button advice in transport table "CONTAINER"
122ms
And
Set advice window in schedule
2s 492ms
And
Fill advice form
14s 713ms
And
Click advice save button and wait for advice form to disappear
30s 768ms
And
Go to "TRANSPORT_TABLE"
187ms
Then
Check advice data in SK API database "CONTAINER"
4s 104ms
After
Hooks.deleteTransportAfterTest()
129ms
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 228ms
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
6s 184ms
When
Click button advice in transport table "TRANSPORT_ORDER"
126ms
And
Set advice window in schedule
2s 524ms
And
Fill advice form
14s 774ms
And
Click advice save button and wait for advice form to disappear
30s 768ms
And
Go to "TRANSPORT_TABLE"
209ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 055ms
After
Hooks.deleteTransportAfterTest()
135ms
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 257ms
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"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 311ms
When
Click button advice in transport table "CONTAINER"
143ms
And
Set advice window in schedule in the past
2s 545ms
And
Fill advice form
14s 785ms
And
Click advice save button to check error message
092ms
Then
Check if possible advice alert is displayed
020ms
After
Hooks.deleteTransportAfterTest()
090ms
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 268ms
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 439ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 294ms
And
Go to "TRANSPORT_TABLE"
187ms
When
Go to transport details "OWN_COLLECTION"
4s 485ms
And
Expand advice panel
120ms
And
Edit advice in transport details
14s 210ms
And
Fill arrival date field
2s 310ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 149ms
Then
Check advice data in database after edition "OWN_COLLECTION"
035ms
After
Hooks.deleteTransportAfterTest()
140ms
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 318ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
33s 371ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 288ms
And
Go to "TRANSPORT_TABLE"
194ms
When
Go to transport details "CONTAINER"
4s 497ms
And
Expand advice panel
115ms
And
Edit advice in transport details
14s 153ms
And
Fill arrival date field
2s 311ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 610ms
Then
Check advice data in database after edition "CONTAINER"
044ms
After
Hooks.deleteTransportAfterTest()
149ms
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 291ms
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 "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 327ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 200ms
And
Go to "TRANSPORT_TABLE"
224ms
When
Go to transport details "TRANSPORT_ORDER"
4s 476ms
And
Expand advice panel
100ms
And
Edit advice in transport details
14s 119ms
And
Fill arrival date field
2s 288ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 150ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
038ms
After
Hooks.deleteTransportAfterTest()
141ms