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 256ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
061ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
003ms
And
Check is transport "CONTAINER" created in transport table and set transport id
54s 406ms
When
Click button advice in transport table "CONTAINER"
103ms
And
Set advice window in schedule
2s 763ms
And
Fill advice form
14s 843ms
And
Click advice save button and wait for advice form to disappear
15s 740ms
And
Go to "TRANSPORT_TABLE"
209ms
And
Go to transport details "CONTAINER"
4s 522ms
Then
Check are advice values equals
2s 339ms
After
Hooks.deleteTransportAfterTest()
145ms
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 225ms
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
18s 437ms
When
Click button advice in transport table "OWN_COLLECTION"
105ms
And
Set advice window in schedule
2s 589ms
And
Fill advice form
14s 807ms
And
Click advice save button and wait for advice form to disappear
30s 692ms
And
Go to "TRANSPORT_TABLE"
221ms
And
Go to transport details "OWN_COLLECTION"
4s 476ms
Then
Check are advice values equals
2s 318ms
After
Hooks.deleteTransportAfterTest()
166ms
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 213ms
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
1s 146ms
When
Click button advice in transport table "TRANSPORT_ORDER"
121ms
And
Set advice window in schedule
2s 551ms
And
Fill advice form
14s 745ms
And
Click advice save button and wait for advice form to disappear
30s 743ms
And
Go to "TRANSPORT_TABLE"
226ms
And
Go to transport details "TRANSPORT_ORDER"
4s 498ms
Then
Check are advice values equals
2s 335ms
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 228ms
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 357ms
When
Click button advice in transport table "OWN_COLLECTION"
136ms
And
Set advice window in schedule
2s 516ms
And
Fill advice form
14s 715ms
And
Click advice save button and wait for advice form to disappear
30s 674ms
And
Go to "TRANSPORT_TABLE"
217ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 178ms
After
Hooks.deleteTransportAfterTest()
122ms
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 238ms
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 326ms
When
Click button advice in transport table "CONTAINER"
114ms
And
Set advice window in schedule
2s 530ms
And
Fill advice form
14s 666ms
And
Click advice save button and wait for advice form to disappear
30s 736ms
And
Go to "TRANSPORT_TABLE"
187ms
Then
Check advice data in SK API database "CONTAINER"
4s 114ms
After
Hooks.deleteTransportAfterTest()
127ms
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 234ms
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 "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 204ms
When
Click button advice in transport table "TRANSPORT_ORDER"
111ms
And
Set advice window in schedule
2s 506ms
And
Fill advice form
14s 731ms
And
Click advice save button and wait for advice form to disappear
30s 703ms
And
Go to "TRANSPORT_TABLE"
233ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 042ms
After
Hooks.deleteTransportAfterTest()
090ms
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 183ms
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 307ms
When
Click button advice in transport table "CONTAINER"
103ms
And
Set advice window in schedule in the past
2s 590ms
And
Fill advice form
14s 751ms
And
Click advice save button to check error message
102ms
Then
Check if possible advice alert is displayed
022ms
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 227ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
39s 436ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 247ms
And
Go to "TRANSPORT_TABLE"
212ms
When
Go to transport details "OWN_COLLECTION"
4s 543ms
And
Expand advice panel
117ms
And
Edit advice in transport details
14s 128ms
And
Fill arrival date field
2s 302ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 161ms
Then
Check advice data in database after edition "OWN_COLLECTION"
042ms
After
Hooks.deleteTransportAfterTest()
184ms
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 262ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
33s 385ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 243ms
And
Go to "TRANSPORT_TABLE"
224ms
When
Go to transport details "CONTAINER"
4s 526ms
And
Expand advice panel
111ms
And
Edit advice in transport details
14s 075ms
And
Fill arrival date field
2s 302ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 595ms
Then
Check advice data in database after edition "CONTAINER"
038ms
After
Hooks.deleteTransportAfterTest()
126ms
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_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 288ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 268ms
And
Go to "TRANSPORT_TABLE"
257ms
When
Go to transport details "TRANSPORT_ORDER"
4s 473ms
And
Expand advice panel
107ms
And
Edit advice in transport details
14s 193ms
And
Fill arrival date field
2s 314ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 626ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
041ms
After
Hooks.deleteTransportAfterTest()
161ms