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"
003ms
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 413ms
When
Click button advice in transport table "CONTAINER"
131ms
And
Set advice window in schedule
2s 656ms
And
Fill advice form
14s 655ms
And
Click advice save button and wait for advice form to disappear
30s 718ms
And
Go to "TRANSPORT_TABLE"
173ms
And
Go to transport details "CONTAINER"
4s 480ms
Then
Check are advice values equals
2s 293ms
After
Hooks.deleteTransportAfterTest()
120ms
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 236ms
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 381ms
When
Click button advice in transport table "OWN_COLLECTION"
125ms
And
Set advice window in schedule
2s 531ms
And
Fill advice form
14s 571ms
And
Click advice save button and wait for advice form to disappear
30s 786ms
And
Go to "TRANSPORT_TABLE"
194ms
And
Go to transport details "OWN_COLLECTION"
4s 466ms
Then
Check are advice values equals
2s 307ms
After
Hooks.deleteTransportAfterTest()
135ms
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 254ms
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 225ms
When
Click button advice in transport table "TRANSPORT_ORDER"
111ms
And
Set advice window in schedule
2s 513ms
And
Fill advice form
14s 719ms
And
Click advice save button and wait for advice form to disappear
30s 726ms
And
Go to "TRANSPORT_TABLE"
228ms
And
Go to transport details "TRANSPORT_ORDER"
4s 498ms
Then
Check are advice values equals
2s 344ms
After
Hooks.deleteTransportAfterTest()
128ms
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 233ms
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 357ms
When
Click button advice in transport table "OWN_COLLECTION"
141ms
And
Set advice window in schedule
2s 486ms
And
Fill advice form
14s 619ms
And
Click advice save button and wait for advice form to disappear
30s 752ms
And
Go to "TRANSPORT_TABLE"
168ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 153ms
After
Hooks.deleteTransportAfterTest()
105ms
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 368ms
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 324ms
When
Click button advice in transport table "CONTAINER"
124ms
And
Set advice window in schedule
2s 556ms
And
Fill advice form
14s 600ms
And
Click advice save button and wait for advice form to disappear
30s 748ms
And
Go to "TRANSPORT_TABLE"
178ms
Then
Check advice data in SK API database "CONTAINER"
4s 131ms
After
Hooks.deleteTransportAfterTest()
142ms
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 268ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
001ms
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
6s 244ms
When
Click button advice in transport table "TRANSPORT_ORDER"
112ms
And
Set advice window in schedule
2s 499ms
And
Fill advice form
14s 604ms
And
Click advice save button and wait for advice form to disappear
30s 728ms
And
Go to "TRANSPORT_TABLE"
229ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 046ms
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 226ms
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"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 350ms
When
Click button advice in transport table "CONTAINER"
130ms
And
Set advice window in schedule in the past
2s 511ms
And
Fill advice form
14s 588ms
And
Click advice save button to check error message
096ms
Then
Check if possible advice alert is displayed
145ms
After
Hooks.deleteTransportAfterTest()
086ms
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 254ms
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
42s 497ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 136ms
And
Go to "TRANSPORT_TABLE"
196ms
When
Go to transport details "OWN_COLLECTION"
4s 509ms
And
Expand advice panel
198ms
And
Edit advice in transport details
14s 193ms
And
Fill arrival date field
2s 302ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 605ms
Then
Check advice data in database after edition "OWN_COLLECTION"
038ms
After
Hooks.deleteTransportAfterTest()
155ms
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 258ms
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 415ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 083ms
And
Go to "TRANSPORT_TABLE"
199ms
When
Go to transport details "CONTAINER"
4s 514ms
And
Expand advice panel
108ms
And
Edit advice in transport details
14s 090ms
And
Fill arrival date field
2s 299ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 120ms
Then
Check advice data in database after edition "CONTAINER"
041ms
After
Hooks.deleteTransportAfterTest()
135ms
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 255ms
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 365ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 592ms
And
Go to "TRANSPORT_TABLE"
212ms
When
Go to transport details "TRANSPORT_ORDER"
4s 454ms
And
Expand advice panel
120ms
And
Edit advice in transport details
14s 133ms
And
Fill arrival date field
2s 297ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 639ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
041ms
After
Hooks.deleteTransportAfterTest()
132ms