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 222ms
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
55s
When
Click button advice in transport table "CONTAINER"
089ms
And
Set advice window in schedule
2s 651ms
And
Fill advice form
14s 689ms
And
Click advice save button and wait for advice form to disappear
30s 670ms
And
Go to "TRANSPORT_TABLE"
206ms
And
Go to transport details "CONTAINER"
4s 477ms
Then
Check are advice values equals
2s 307ms
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 316ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
003ms
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 473ms
When
Click button advice in transport table "OWN_COLLECTION"
095ms
And
Set advice window in schedule
2s 653ms
And
Fill advice form
14s 632ms
And
Click advice save button and wait for advice form to disappear
30s 728ms
And
Go to "TRANSPORT_TABLE"
194ms
And
Go to transport details "OWN_COLLECTION"
4s 448ms
Then
Check are advice values equals
2s 310ms
After
Hooks.deleteTransportAfterTest()
144ms
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 283ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
001ms
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 278ms
When
Click button advice in transport table "TRANSPORT_ORDER"
084ms
And
Set advice window in schedule
2s 587ms
And
Fill advice form
14s 649ms
And
Click advice save button and wait for advice form to disappear
30s 694ms
And
Go to "TRANSPORT_TABLE"
216ms
And
Go to transport details "TRANSPORT_ORDER"
4s 443ms
Then
Check are advice values equals
2s 324ms
After
Hooks.deleteTransportAfterTest()
146ms
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 275ms
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 450ms
When
Click button advice in transport table "OWN_COLLECTION"
086ms
And
Set advice window in schedule
2s 620ms
And
Fill advice form
14s 597ms
And
Click advice save button and wait for advice form to disappear
30s 694ms
And
Go to "TRANSPORT_TABLE"
186ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 220ms
After
Hooks.deleteTransportAfterTest()
139ms
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 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 949ms
When
Click button advice in transport table "CONTAINER"
096ms
And
Set advice window in schedule
2s 652ms
And
Fill advice form
14s 650ms
And
Click advice save button and wait for advice form to disappear
30s 716ms
And
Go to "TRANSPORT_TABLE"
184ms
Then
Check advice data in SK API database "CONTAINER"
3s 110ms
After
Hooks.deleteTransportAfterTest()
140ms
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 241ms
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 879ms
When
Click button advice in transport table "TRANSPORT_ORDER"
087ms
And
Set advice window in schedule
2s 634ms
And
Fill advice form
14s 629ms
And
Click advice save button and wait for advice form to disappear
30s 740ms
And
Go to "TRANSPORT_TABLE"
222ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 042ms
After
Hooks.deleteTransportAfterTest()
133ms
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 261ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
003ms
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 365ms
When
Click button advice in transport table "CONTAINER"
093ms
And
Set advice window in schedule in the past
2s 613ms
And
Fill advice form
14s 607ms
And
Click advice save button to check error message
089ms
Then
Check if possible advice alert is displayed
020ms
After
Hooks.deleteTransportAfterTest()
128ms
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_OWN_COLLECTION" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
004ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
43s 138ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 054ms
And
Go to "TRANSPORT_TABLE"
216ms
When
Go to transport details "OWN_COLLECTION"
4s 423ms
And
Expand advice panel
115ms
And
Edit advice in transport details
13s 996ms
And
Fill arrival date field
2s 274ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 638ms
Then
Check advice data in database after edition "OWN_COLLECTION"
031ms
After
Hooks.deleteTransportAfterTest()
131ms
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 200ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
34s 024ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 162ms
And
Go to "TRANSPORT_TABLE"
207ms
When
Go to transport details "CONTAINER"
4s 454ms
And
Expand advice panel
111ms
And
Edit advice in transport details
13s 968ms
And
Fill arrival date field
2s 272ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 621ms
Then
Check advice data in database after edition "CONTAINER"
029ms
After
Hooks.deleteTransportAfterTest()
131ms
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 183ms
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"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 970ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 193ms
And
Go to "TRANSPORT_TABLE"
240ms
When
Go to transport details "TRANSPORT_ORDER"
4s 421ms
And
Expand advice panel
101ms
And
Edit advice in transport details
13s 974ms
And
Fill arrival date field
2s 258ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 624ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
026ms
After
Hooks.deleteTransportAfterTest()
137ms