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 221ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
54s 425ms
When
Click button advice in transport table "CONTAINER"
119ms
And
Set advice window in schedule
2s 629ms
And
Fill advice form
14s 865ms
And
Click advice save button and wait for advice form to disappear
30s 788ms
And
Go to "TRANSPORT_TABLE"
199ms
And
Go to transport details "CONTAINER"
4s 512ms
Then
Check are advice values equals
2s 336ms
After
Hooks.deleteTransportAfterTest()
140ms
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 226ms
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 385ms
When
Click button advice in transport table "OWN_COLLECTION"
130ms
And
Set advice window in schedule
2s 561ms
And
Fill advice form
14s 775ms
And
Click advice save button and wait for advice form to disappear
30s 735ms
And
Go to "TRANSPORT_TABLE"
195ms
And
Go to transport details "OWN_COLLECTION"
4s 499ms
Then
Check are advice values equals
2s 340ms
After
Hooks.deleteTransportAfterTest()
138ms
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 516ms
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 292ms
When
Click button advice in transport table "TRANSPORT_ORDER"
080ms
And
Set advice window in schedule
2s 595ms
And
Fill advice form
14s 780ms
And
Click advice save button and wait for advice form to disappear
30s 757ms
And
Go to "TRANSPORT_TABLE"
206ms
And
Go to transport details "TRANSPORT_ORDER"
4s 470ms
Then
Check are advice values equals
2s 328ms
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 248ms
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 381ms
When
Click button advice in transport table "OWN_COLLECTION"
117ms
And
Set advice window in schedule
2s 505ms
And
Fill advice form
14s 747ms
And
Click advice save button and wait for advice form to disappear
30s 770ms
And
Go to "TRANSPORT_TABLE"
179ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 166ms
After
Hooks.deleteTransportAfterTest()
144ms
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 216ms
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
6s 356ms
When
Click button advice in transport table "CONTAINER"
114ms
And
Set advice window in schedule
2s 502ms
And
Fill advice form
14s 847ms
And
Click advice save button and wait for advice form to disappear
30s 702ms
And
Go to "TRANSPORT_TABLE"
191ms
Then
Check advice data in SK API database "CONTAINER"
4s 111ms
After
Hooks.deleteTransportAfterTest()
136ms
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 362ms
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
6s 211ms
When
Click button advice in transport table "TRANSPORT_ORDER"
111ms
And
Set advice window in schedule
2s 506ms
And
Fill advice form
14s 729ms
And
Click advice save button and wait for advice form to disappear
30s 739ms
And
Go to "TRANSPORT_TABLE"
243ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 051ms
After
Hooks.deleteTransportAfterTest()
103ms
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 247ms
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 338ms
When
Click button advice in transport table "CONTAINER"
098ms
And
Set advice window in schedule in the past
2s 620ms
And
Fill advice form
14s 867ms
And
Click advice save button to check error message
099ms
Then
Check if possible advice alert is displayed
024ms
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 252ms
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 492ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 179ms
And
Go to "TRANSPORT_TABLE"
182ms
When
Go to transport details "OWN_COLLECTION"
4s 470ms
And
Expand advice panel
117ms
And
Edit advice in transport details
14s 128ms
And
Fill arrival date field
2s 323ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 642ms
Then
Check advice data in database after edition "OWN_COLLECTION"
036ms
After
Hooks.deleteTransportAfterTest()
127ms
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 253ms
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
33s 408ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 307ms
And
Go to "TRANSPORT_TABLE"
211ms
When
Go to transport details "CONTAINER"
4s 556ms
And
Expand advice panel
117ms
And
Edit advice in transport details
14s 094ms
And
Fill arrival date field
2s 319ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 619ms
Then
Check advice data in database after edition "CONTAINER"
040ms
After
Hooks.deleteTransportAfterTest()
129ms
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 273ms
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"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 330ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 232ms
And
Go to "TRANSPORT_TABLE"
263ms
When
Go to transport details "TRANSPORT_ORDER"
4s 493ms
And
Expand advice panel
116ms
And
Edit advice in transport details
14s 181ms
And
Fill arrival date field
2s 282ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 654ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
038ms
After
Hooks.deleteTransportAfterTest()
131ms