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 205ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
004ms
And
Add transport by SKApi in "MGW"
001ms
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 429ms
When
Click button advice in transport table "CONTAINER"
089ms
And
Set advice window in schedule
2s 665ms
And
Fill advice form
14s 523ms
And
Click advice save button and wait for advice form to disappear
30s 722ms
And
Go to "TRANSPORT_TABLE"
197ms
And
Go to transport details "CONTAINER"
4s 486ms
Then
Check are advice values equals
2s 318ms
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 193ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
004ms
And
Add transport by SKApi in "MGW"
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 365ms
When
Click button advice in transport table "OWN_COLLECTION"
084ms
And
Set advice window in schedule
2s 571ms
And
Fill advice form
14s 615ms
And
Click advice save button and wait for advice form to disappear
30s 743ms
And
Go to "TRANSPORT_TABLE"
193ms
And
Go to transport details "OWN_COLLECTION"
4s 461ms
Then
Check are advice values equals
2s 303ms
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 202ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
004ms
And
Add transport by SKApi in "MGW"
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
004ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 202ms
When
Click button advice in transport table "TRANSPORT_ORDER"
078ms
And
Set advice window in schedule
2s 559ms
And
Fill advice form
14s 498ms
And
Click advice save button and wait for advice form to disappear
30s 667ms
And
Go to "TRANSPORT_TABLE"
251ms
And
Go to transport details "TRANSPORT_ORDER"
4s 433ms
Then
Check are advice values equals
2s 315ms
After
Hooks.deleteTransportAfterTest()
111ms
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 205ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
005ms
And
Add transport by SKApi in "MGW"
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
6s 367ms
When
Click button advice in transport table "OWN_COLLECTION"
083ms
And
Set advice window in schedule
2s 566ms
And
Fill advice form
14s 529ms
And
Click advice save button and wait for advice form to disappear
30s 724ms
And
Go to "TRANSPORT_TABLE"
189ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 152ms
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 431ms
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"
003ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 318ms
When
Click button advice in transport table "CONTAINER"
090ms
And
Set advice window in schedule
2s 573ms
And
Fill advice form
14s 494ms
And
Click advice save button and wait for advice form to disappear
30s 726ms
And
Go to "TRANSPORT_TABLE"
184ms
Then
Check advice data in SK API database "CONTAINER"
3s 107ms
After
Hooks.deleteTransportAfterTest()
108ms
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 172ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
004ms
And
Add transport by SKApi in "MGW"
005ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
003ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 795ms
When
Click button advice in transport table "TRANSPORT_ORDER"
089ms
And
Set advice window in schedule
2s 546ms
And
Fill advice form
14s 493ms
And
Click advice save button and wait for advice form to disappear
30s 704ms
And
Go to "TRANSPORT_TABLE"
226ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 056ms
After
Hooks.deleteTransportAfterTest()
098ms
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 165ms
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 324ms
When
Click button advice in transport table "CONTAINER"
092ms
And
Set advice window in schedule in the past
2s 587ms
And
Fill advice form
14s 585ms
And
Click advice save button to check error message
084ms
Then
Check if possible advice alert is displayed
018ms
After
Hooks.deleteTransportAfterTest()
123ms
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 197ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
002ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
003ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
42s 437ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
47s 987ms
And
Go to "TRANSPORT_TABLE"
213ms
When
Go to transport details "OWN_COLLECTION"
4s 461ms
And
Expand advice panel
121ms
And
Edit advice in transport details
13s 973ms
And
Fill arrival date field
2s 277ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 618ms
Then
Check advice data in database after edition "OWN_COLLECTION"
027ms
After
Hooks.deleteTransportAfterTest()
101ms
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 248ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
33s 397ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
47s 947ms
And
Go to "TRANSPORT_TABLE"
197ms
When
Go to transport details "CONTAINER"
4s 496ms
And
Expand advice panel
110ms
And
Edit advice in transport details
13s 947ms
And
Fill arrival date field
2s 263ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 639ms
Then
Check advice data in database after edition "CONTAINER"
030ms
After
Hooks.deleteTransportAfterTest()
102ms
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 203ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
002ms
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 879ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
47s 945ms
And
Go to "TRANSPORT_TABLE"
237ms
When
Go to transport details "TRANSPORT_ORDER"
4s 464ms
And
Expand advice panel
105ms
And
Edit advice in transport details
14s 017ms
And
Fill arrival date field
2s 294ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 632ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
033ms
After
Hooks.deleteTransportAfterTest()
118ms