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 209ms
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 444ms
When
Click button advice in transport table "CONTAINER"
103ms
And
Set advice window in schedule
2s 628ms
And
Fill advice form
14s 857ms
And
Click advice save button and wait for advice form to disappear
30s 726ms
And
Go to "TRANSPORT_TABLE"
164ms
And
Go to transport details "CONTAINER"
4s 511ms
Then
Check are advice values equals
2s 337ms
After
Hooks.deleteTransportAfterTest()
155ms
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 171ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
001ms
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 349ms
When
Click button advice in transport table "OWN_COLLECTION"
119ms
And
Set advice window in schedule
2s 543ms
And
Fill advice form
14s 754ms
And
Click advice save button and wait for advice form to disappear
30s 702ms
And
Go to "TRANSPORT_TABLE"
174ms
And
Go to transport details "OWN_COLLECTION"
4s 461ms
Then
Check are advice values equals
2s 331ms
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 266ms
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
3s 214ms
When
Click button advice in transport table "TRANSPORT_ORDER"
121ms
And
Set advice window in schedule
2s 545ms
And
Fill advice form
14s 801ms
And
Click advice save button and wait for advice form to disappear
30s 738ms
And
Go to "TRANSPORT_TABLE"
203ms
And
Go to transport details "TRANSPORT_ORDER"
4s 486ms
Then
Check are advice values equals
2s 343ms
After
Hooks.deleteTransportAfterTest()
121ms
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 274ms
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"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 390ms
When
Click button advice in transport table "OWN_COLLECTION"
107ms
And
Set advice window in schedule
2s 516ms
And
Fill advice form
14s 792ms
And
Click advice save button and wait for advice form to disappear
30s 769ms
And
Go to "TRANSPORT_TABLE"
187ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 183ms
After
Hooks.deleteTransportAfterTest()
132ms
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 250ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
6s 313ms
When
Click button advice in transport table "CONTAINER"
134ms
And
Set advice window in schedule
2s 478ms
And
Fill advice form
14s 740ms
And
Click advice save button and wait for advice form to disappear
30s 830ms
And
Go to "TRANSPORT_TABLE"
174ms
Then
Check advice data in SK API database "CONTAINER"
3s 103ms
After
Hooks.deleteTransportAfterTest()
094ms
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 428ms
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 823ms
When
Click button advice in transport table "TRANSPORT_ORDER"
110ms
And
Set advice window in schedule
2s 521ms
And
Fill advice form
14s 784ms
And
Click advice save button and wait for advice form to disappear
30s 715ms
And
Go to "TRANSPORT_TABLE"
228ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 041ms
After
Hooks.deleteTransportAfterTest()
089ms
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 215ms
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 332ms
When
Click button advice in transport table "CONTAINER"
109ms
And
Set advice window in schedule in the past
2s 575ms
And
Fill advice form
14s 782ms
And
Click advice save button to check error message
122ms
Then
Check if possible advice alert is displayed
023ms
After
Hooks.deleteTransportAfterTest()
111ms
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 230ms
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 487ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 251ms
And
Go to "TRANSPORT_TABLE"
195ms
When
Go to transport details "OWN_COLLECTION"
4s 495ms
And
Expand advice panel
108ms
And
Edit advice in transport details
14s 085ms
And
Fill arrival date field
2s 309ms
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"
039ms
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 184ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
33s 387ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 260ms
And
Go to "TRANSPORT_TABLE"
181ms
When
Go to transport details "CONTAINER"
4s 551ms
And
Expand advice panel
118ms
And
Edit advice in transport details
14s 068ms
And
Fill arrival date field
2s 276ms
And
Click "save-transport-and-close" save button and wait for form to disappear
674ms
Then
Check advice data in database after edition "CONTAINER"
027ms
After
Hooks.deleteTransportAfterTest()
116ms
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 215ms
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
48s 339ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 300ms
And
Go to "TRANSPORT_TABLE"
199ms
When
Go to transport details "TRANSPORT_ORDER"
4s 476ms
And
Expand advice panel
119ms
And
Edit advice in transport details
14s 170ms
And
Fill arrival date field
2s 279ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 217ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
034ms
After
Hooks.deleteTransportAfterTest()
114ms