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 253ms
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
54s 410ms
When
Click button advice in transport table "CONTAINER"
127ms
And
Set advice window in schedule
2s 697ms
And
Fill advice form
14s 760ms
And
Click advice save button and wait for advice form to disappear
31s 264ms
And
Go to "TRANSPORT_TABLE"
190ms
And
Go to transport details "CONTAINER"
4s 524ms
Then
Check are advice values equals
2s 329ms
After
Hooks.deleteTransportAfterTest()
150ms
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 290ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
001ms
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
1m 489ms
When
Click button advice in transport table "OWN_COLLECTION"
125ms
And
Set advice window in schedule
2s 574ms
And
Fill advice form
14s 648ms
And
Click advice save button and wait for advice form to disappear
30s 764ms
And
Go to "TRANSPORT_TABLE"
194ms
And
Go to transport details "OWN_COLLECTION"
4s 504ms
Then
Check are advice values equals
2s 333ms
After
Hooks.deleteTransportAfterTest()
130ms
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 245ms
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
3s 228ms
When
Click button advice in transport table "TRANSPORT_ORDER"
102ms
And
Set advice window in schedule
2s 511ms
And
Fill advice form
14s 526ms
And
Click advice save button and wait for advice form to disappear
31s 226ms
And
Go to "TRANSPORT_TABLE"
199ms
And
Go to transport details "TRANSPORT_ORDER"
4s 472ms
Then
Check are advice values equals
2s 332ms
After
Hooks.deleteTransportAfterTest()
108ms
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 282ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
003ms
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 356ms
When
Click button advice in transport table "OWN_COLLECTION"
133ms
And
Set advice window in schedule
2s 504ms
And
Fill advice form
14s 617ms
And
Click advice save button and wait for advice form to disappear
30s 798ms
And
Go to "TRANSPORT_TABLE"
180ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 163ms
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 293ms
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"
124ms
And
Set advice window in schedule
2s 489ms
And
Fill advice form
14s 595ms
And
Click advice save button and wait for advice form to disappear
30s 721ms
And
Go to "TRANSPORT_TABLE"
191ms
Then
Check advice data in SK API database "CONTAINER"
4s 103ms
After
Hooks.deleteTransportAfterTest()
148ms
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 244ms
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 220ms
When
Click button advice in transport table "TRANSPORT_ORDER"
122ms
And
Set advice window in schedule
2s 528ms
And
Fill advice form
14s 598ms
And
Click advice save button and wait for advice form to disappear
31s 323ms
And
Go to "TRANSPORT_TABLE"
222ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 044ms
After
Hooks.deleteTransportAfterTest()
155ms
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 217ms
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"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
9s 337ms
When
Click button advice in transport table "CONTAINER"
114ms
And
Set advice window in schedule in the past
2s 599ms
And
Fill advice form
14s 584ms
And
Click advice save button to check error message
102ms
Then
Check if possible advice alert is displayed
143ms
After
Hooks.deleteTransportAfterTest()
104ms
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 190ms
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 468ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 027ms
And
Go to "TRANSPORT_TABLE"
187ms
When
Go to transport details "OWN_COLLECTION"
4s 477ms
And
Expand advice panel
121ms
And
Edit advice in transport details
14s 111ms
And
Fill arrival date field
2s 309ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 138ms
Then
Check advice data in database after edition "OWN_COLLECTION"
042ms
After
Hooks.deleteTransportAfterTest()
155ms
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 243ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
001ms
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 386ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 205ms
And
Go to "TRANSPORT_TABLE"
172ms
When
Go to transport details "CONTAINER"
4s 492ms
And
Expand advice panel
112ms
And
Edit advice in transport details
13s 965ms
And
Fill arrival date field
2s 296ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 156ms
Then
Check advice data in database after edition "CONTAINER"
035ms
After
Hooks.deleteTransportAfterTest()
136ms
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_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 328ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 111ms
And
Go to "TRANSPORT_TABLE"
211ms
When
Go to transport details "TRANSPORT_ORDER"
4s 450ms
And
Expand advice panel
145ms
And
Edit advice in transport details
14s 040ms
And
Fill arrival date field
2s 313ms
And
Click "save-transport-and-close" save button and wait for form to disappear
666ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
026ms
After
Hooks.deleteTransportAfterTest()
144ms