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 293ms
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 414ms
When
Click button advice in transport table "CONTAINER"
138ms
And
Set advice window in schedule
2s 944ms
And
Fill advice form
14s 797ms
And
Click advice save button and wait for advice form to disappear
30s 757ms
And
Go to "TRANSPORT_TABLE"
179ms
And
Go to transport details "CONTAINER"
4s 506ms
Then
Check are advice values equals
2s 331ms
After
Hooks.deleteTransportAfterTest()
155ms
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 250ms
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 "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"
195ms
And
Set advice window in schedule
2s 626ms
And
Fill advice form
14s 697ms
And
Click advice save button and wait for advice form to disappear
30s 754ms
And
Go to "TRANSPORT_TABLE"
196ms
And
Go to transport details "OWN_COLLECTION"
4s 486ms
Then
Check are advice values equals
2s 356ms
After
Hooks.deleteTransportAfterTest()
158ms
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 241ms
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 "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 255ms
When
Click button advice in transport table "TRANSPORT_ORDER"
122ms
And
Set advice window in schedule
2s 551ms
And
Fill advice form
14s 763ms
And
Click advice save button and wait for advice form to disappear
30s 718ms
And
Go to "TRANSPORT_TABLE"
209ms
And
Go to transport details "TRANSPORT_ORDER"
4s 497ms
Then
Check are advice values equals
2s 310ms
After
Hooks.deleteTransportAfterTest()
115ms
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 245ms
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 "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"
108ms
And
Set advice window in schedule
2s 667ms
And
Fill advice form
14s 716ms
And
Click advice save button and wait for advice form to disappear
30s 714ms
And
Go to "TRANSPORT_TABLE"
181ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 165ms
After
Hooks.deleteTransportAfterTest()
132ms
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 239ms
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 351ms
When
Click button advice in transport table "CONTAINER"
140ms
And
Set advice window in schedule
2s 551ms
And
Fill advice form
14s 813ms
And
Click advice save button and wait for advice form to disappear
30s 727ms
And
Go to "TRANSPORT_TABLE"
180ms
Then
Check advice data in SK API database "CONTAINER"
3s 095ms
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 230ms
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"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 823ms
When
Click button advice in transport table "TRANSPORT_ORDER"
115ms
And
Set advice window in schedule
2s 522ms
And
Fill advice form
14s 780ms
And
Click advice save button and wait for advice form to disappear
30s 787ms
And
Go to "TRANSPORT_TABLE"
209ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 047ms
After
Hooks.deleteTransportAfterTest()
114ms
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 234ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
004ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
9s 328ms
When
Click button advice in transport table "CONTAINER"
117ms
And
Set advice window in schedule in the past
2s 566ms
And
Fill advice form
14s 779ms
And
Click advice save button to check error message
104ms
Then
Check if possible advice alert is displayed
022ms
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 678ms
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 494ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 237ms
And
Go to "TRANSPORT_TABLE"
168ms
When
Go to transport details "OWN_COLLECTION"
4s 478ms
And
Expand advice panel
115ms
And
Edit advice in transport details
14s 045ms
And
Fill arrival date field
2s 277ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 669ms
Then
Check advice data in database after edition "OWN_COLLECTION"
039ms
After
Hooks.deleteTransportAfterTest()
142ms
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 249ms
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
34s 011ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 314ms
And
Go to "TRANSPORT_TABLE"
171ms
When
Go to transport details "CONTAINER"
4s 513ms
And
Expand advice panel
113ms
And
Edit advice in transport details
14s 091ms
And
Fill arrival date field
2s 309ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 143ms
Then
Check advice data in database after edition "CONTAINER"
039ms
After
Hooks.deleteTransportAfterTest()
150ms
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 257ms
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 372ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 322ms
And
Go to "TRANSPORT_TABLE"
216ms
When
Go to transport details "TRANSPORT_ORDER"
4s 481ms
And
Expand advice panel
111ms
And
Edit advice in transport details
14s 090ms
And
Fill arrival date field
2s 296ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 627ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
041ms
After
Hooks.deleteTransportAfterTest()
142ms