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 218ms
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 423ms
When
Click button advice in transport table "CONTAINER"
073ms
And
Set advice window in schedule
2s 807ms
And
Fill advice form
14s 751ms
And
Click advice save button and wait for advice form to disappear
30s 695ms
And
Go to "TRANSPORT_TABLE"
180ms
And
Go to transport details "CONTAINER"
4s 488ms
Then
Check are advice values equals
2s 287ms
After
Hooks.deleteTransportAfterTest()
100ms
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 279ms
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 516ms
When
Click button advice in transport table "OWN_COLLECTION"
126ms
And
Set advice window in schedule
2s 798ms
And
Fill advice form
14s 570ms
And
Click advice save button and wait for advice form to disappear
30s 692ms
And
Go to "TRANSPORT_TABLE"
146ms
And
Go to transport details "OWN_COLLECTION"
4s 518ms
Then
Check are advice values equals
2s 285ms
After
Hooks.deleteTransportAfterTest()
149ms
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 217ms
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 360ms
When
Click button advice in transport table "TRANSPORT_ORDER"
108ms
And
Set advice window in schedule
2s 833ms
And
Fill advice form
14s 482ms
And
Click advice save button and wait for advice form to disappear
30s 724ms
And
Go to "TRANSPORT_TABLE"
218ms
And
Go to transport details "TRANSPORT_ORDER"
4s 461ms
Then
Check are advice values equals
2s 284ms
After
Hooks.deleteTransportAfterTest()
086ms
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 226ms
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 375ms
When
Click button advice in transport table "OWN_COLLECTION"
094ms
And
Set advice window in schedule
3s 101ms
And
Fill advice form
14s 474ms
And
Click advice save button and wait for advice form to disappear
30s 706ms
And
Go to "TRANSPORT_TABLE"
176ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 181ms
After
Hooks.deleteTransportAfterTest()
103ms
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_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 417ms
When
Click button advice in transport table "CONTAINER"
102ms
And
Set advice window in schedule
2s 739ms
And
Fill advice form
14s 625ms
And
Click advice save button and wait for advice form to disappear
30s 690ms
And
Go to "TRANSPORT_TABLE"
178ms
Then
Check advice data in SK API database "CONTAINER"
3s 129ms
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 364ms
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 379ms
When
Click button advice in transport table "TRANSPORT_ORDER"
064ms
And
Set advice window in schedule
2s 742ms
And
Fill advice form
14s 524ms
And
Click advice save button and wait for advice form to disappear
30s 651ms
And
Go to "TRANSPORT_TABLE"
202ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 037ms
After
Hooks.deleteTransportAfterTest()
122ms
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 451ms
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 349ms
When
Click button advice in transport table "CONTAINER"
084ms
And
Set advice window in schedule in the past
2s 678ms
And
Fill advice form
14s 487ms
And
Click advice save button to check error message
067ms
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 213ms
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"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
42s 469ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 035ms
And
Go to "TRANSPORT_TABLE"
182ms
When
Go to transport details "OWN_COLLECTION"
4s 410ms
And
Expand advice panel
107ms
And
Edit advice in transport details
13s 999ms
And
Fill arrival date field
2s 284ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 131ms
Then
Check advice data in database after edition "OWN_COLLECTION"
033ms
After
Hooks.deleteTransportAfterTest()
205ms
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 235ms
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 001ms
And
Go to "TRANSPORT_TABLE"
169ms
When
Go to transport details "CONTAINER"
4s 525ms
And
Expand advice panel
099ms
And
Edit advice in transport details
13s 960ms
And
Fill arrival date field
2s 257ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 107ms
Then
Check advice data in database after edition "CONTAINER"
029ms
After
Hooks.deleteTransportAfterTest()
110ms
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 278ms
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
33s 315ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 027ms
And
Go to "TRANSPORT_TABLE"
228ms
When
Go to transport details "TRANSPORT_ORDER"
4s 529ms
And
Expand advice panel
108ms
And
Edit advice in transport details
14s 110ms
And
Fill arrival date field
2s 280ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 152ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
031ms
After
Hooks.deleteTransportAfterTest()
116ms