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 230ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
004ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
007ms
And
Check is transport "CONTAINER" created in transport table and set transport id
54s 403ms
When
Click button advice in transport table "CONTAINER"
119ms
And
Set advice window in schedule
2s 625ms
And
Fill advice form
14s 719ms
And
Click advice save button and wait for advice form to disappear
31s 262ms
And
Go to "TRANSPORT_TABLE"
163ms
And
Go to transport details "CONTAINER"
4s 511ms
Then
Check are advice values equals
2s 337ms
After
Hooks.deleteTransportAfterTest()
129ms
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 278ms
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
1m 3s 484ms
When
Click button advice in transport table "OWN_COLLECTION"
102ms
And
Set advice window in schedule
2s 557ms
And
Fill advice form
14s 725ms
And
Click advice save button and wait for advice form to disappear
30s 675ms
And
Go to "TRANSPORT_TABLE"
184ms
And
Go to transport details "OWN_COLLECTION"
4s 464ms
Then
Check are advice values equals
2s 362ms
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 285ms
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
1m 928ms
When
Click button advice in transport table "TRANSPORT_ORDER"
139ms
And
Set advice window in schedule
2s 537ms
And
Fill advice form
14s 807ms
And
Click advice save button and wait for advice form to disappear
30s 744ms
And
Go to "TRANSPORT_TABLE"
214ms
And
Go to transport details "TRANSPORT_ORDER"
4s 503ms
Then
Check are advice values equals
2s 336ms
After
Hooks.deleteTransportAfterTest()
114ms
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 214ms
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 382ms
When
Click button advice in transport table "OWN_COLLECTION"
112ms
And
Set advice window in schedule
2s 558ms
And
Fill advice form
14s 765ms
And
Click advice save button and wait for advice form to disappear
30s 762ms
And
Go to "TRANSPORT_TABLE"
169ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 160ms
After
Hooks.deleteTransportAfterTest()
117ms
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 206ms
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 328ms
When
Click button advice in transport table "CONTAINER"
125ms
And
Set advice window in schedule
2s 575ms
And
Fill advice form
14s 819ms
And
Click advice save button and wait for advice form to disappear
30s 787ms
And
Go to "TRANSPORT_TABLE"
174ms
Then
Check advice data in SK API database "CONTAINER"
3s 089ms
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 257ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
003ms
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 831ms
When
Click button advice in transport table "TRANSPORT_ORDER"
121ms
And
Set advice window in schedule
2s 520ms
And
Fill advice form
14s 845ms
And
Click advice save button and wait for advice form to disappear
30s 735ms
And
Go to "TRANSPORT_TABLE"
206ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 048ms
After
Hooks.deleteTransportAfterTest()
115ms
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 213ms
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 352ms
When
Click button advice in transport table "CONTAINER"
090ms
And
Set advice window in schedule in the past
2s 579ms
And
Fill advice form
14s 764ms
And
Click advice save button to check error message
095ms
Then
Check if possible advice alert is displayed
027ms
After
Hooks.deleteTransportAfterTest()
082ms
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 256ms
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 467ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 168ms
And
Go to "TRANSPORT_TABLE"
168ms
When
Go to transport details "OWN_COLLECTION"
4s 487ms
And
Expand advice panel
123ms
And
Edit advice in transport details
14s 157ms
And
Fill arrival date field
2s 337ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 664ms
Then
Check advice data in database after edition "OWN_COLLECTION"
034ms
After
Hooks.deleteTransportAfterTest()
118ms
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 265ms
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 426ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 335ms
And
Go to "TRANSPORT_TABLE"
160ms
When
Go to transport details "CONTAINER"
4s 504ms
And
Expand advice panel
112ms
And
Edit advice in transport details
14s 068ms
And
Fill arrival date field
2s 290ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 612ms
Then
Check advice data in database after edition "CONTAINER"
038ms
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 231ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
003ms
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 302ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 244ms
And
Go to "TRANSPORT_TABLE"
206ms
When
Go to transport details "TRANSPORT_ORDER"
4s 525ms
And
Expand advice panel
113ms
And
Edit advice in transport details
14s 108ms
And
Fill arrival date field
2s 292ms
And
Click "save-transport-and-close" save button and wait for form to disappear
645ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
034ms
After
Hooks.deleteTransportAfterTest()
109ms