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 212ms
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
54s 399ms
When
Click button advice in transport table "CONTAINER"
099ms
And
Set advice window in schedule
2s 788ms
And
Fill advice form
14s 776ms
And
Click advice save button and wait for advice form to disappear
30s 743ms
And
Go to "TRANSPORT_TABLE"
165ms
And
Go to transport details "CONTAINER"
4s 534ms
Then
Check are advice values equals
2s 336ms
After
Hooks.deleteTransportAfterTest()
136ms
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 212ms
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"
120ms
And
Set advice window in schedule
2s 516ms
And
Fill advice form
14s 698ms
And
Click advice save button and wait for advice form to disappear
30s 771ms
And
Go to "TRANSPORT_TABLE"
180ms
And
Go to transport details "OWN_COLLECTION"
4s 490ms
Then
Check are advice values equals
2s 347ms
After
Hooks.deleteTransportAfterTest()
157ms
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 185ms
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 245ms
When
Click button advice in transport table "TRANSPORT_ORDER"
119ms
And
Set advice window in schedule
2s 527ms
And
Fill advice form
14s 793ms
And
Click advice save button and wait for advice form to disappear
30s 770ms
And
Go to "TRANSPORT_TABLE"
229ms
And
Go to transport details "TRANSPORT_ORDER"
4s 463ms
Then
Check are advice values equals
2s 329ms
After
Hooks.deleteTransportAfterTest()
124ms
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 225ms
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 397ms
When
Click button advice in transport table "OWN_COLLECTION"
155ms
And
Set advice window in schedule
2s 498ms
And
Fill advice form
14s 637ms
And
Click advice save button and wait for advice form to disappear
30s 722ms
And
Go to "TRANSPORT_TABLE"
197ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 160ms
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 149ms
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 320ms
When
Click button advice in transport table "CONTAINER"
136ms
And
Set advice window in schedule
2s 532ms
And
Fill advice form
14s 808ms
And
Click advice save button and wait for advice form to disappear
30s 778ms
And
Go to "TRANSPORT_TABLE"
189ms
Then
Check advice data in SK API database "CONTAINER"
4s 105ms
After
Hooks.deleteTransportAfterTest()
135ms
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 198ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
004ms
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 212ms
When
Click button advice in transport table "TRANSPORT_ORDER"
119ms
And
Set advice window in schedule
2s 550ms
And
Fill advice form
14s 724ms
And
Click advice save button and wait for advice form to disappear
30s 778ms
And
Go to "TRANSPORT_TABLE"
224ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 050ms
After
Hooks.deleteTransportAfterTest()
125ms
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 273ms
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
9s 332ms
When
Click button advice in transport table "CONTAINER"
097ms
And
Set advice window in schedule in the past
2s 547ms
And
Fill advice form
14s 765ms
And
Click advice save button to check error message
090ms
Then
Check if possible advice alert is displayed
019ms
After
Hooks.deleteTransportAfterTest()
120ms
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 214ms
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"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
39s 462ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 211ms
And
Go to "TRANSPORT_TABLE"
178ms
When
Go to transport details "OWN_COLLECTION"
4s 492ms
And
Expand advice panel
120ms
And
Edit advice in transport details
14s 140ms
And
Fill arrival date field
2s 332ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 659ms
Then
Check advice data in database after edition "OWN_COLLECTION"
033ms
After
Hooks.deleteTransportAfterTest()
118ms
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 298ms
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"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
33s 393ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 244ms
And
Go to "TRANSPORT_TABLE"
198ms
When
Go to transport details "CONTAINER"
4s 535ms
And
Expand advice panel
123ms
And
Edit advice in transport details
14s 142ms
And
Fill arrival date field
2s 303ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 647ms
Then
Check advice data in database after edition "CONTAINER"
041ms
After
Hooks.deleteTransportAfterTest()
161ms
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 218ms
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 347ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 233ms
And
Go to "TRANSPORT_TABLE"
218ms
When
Go to transport details "TRANSPORT_ORDER"
4s 463ms
And
Expand advice panel
117ms
And
Edit advice in transport details
14s 112ms
And
Fill arrival date field
2s 290ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 157ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
029ms
After
Hooks.deleteTransportAfterTest()
137ms