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 245ms
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
54s 400ms
When
Click button advice in transport table "CONTAINER"
084ms
And
Set advice window in schedule
2s 727ms
And
Fill advice form
14s 603ms
And
Click advice save button and wait for advice form to disappear
30s 717ms
And
Go to "TRANSPORT_TABLE"
221ms
And
Go to transport details "CONTAINER"
4s 494ms
Then
Check are advice values equals
2s 290ms
After
Hooks.deleteTransportAfterTest()
159ms
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 220ms
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 347ms
When
Click button advice in transport table "OWN_COLLECTION"
097ms
And
Set advice window in schedule
2s 611ms
And
Fill advice form
14s 575ms
And
Click advice save button and wait for advice form to disappear
30s 734ms
And
Go to "TRANSPORT_TABLE"
189ms
And
Go to transport details "OWN_COLLECTION"
4s 439ms
Then
Check are advice values equals
2s 307ms
After
Hooks.deleteTransportAfterTest()
128ms
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 245ms
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 230ms
When
Click button advice in transport table "TRANSPORT_ORDER"
087ms
And
Set advice window in schedule
2s 540ms
And
Fill advice form
14s 644ms
And
Click advice save button and wait for advice form to disappear
30s 734ms
And
Go to "TRANSPORT_TABLE"
215ms
And
Go to transport details "TRANSPORT_ORDER"
4s 465ms
Then
Check are advice values equals
2s 317ms
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 244ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
085ms
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 381ms
When
Click button advice in transport table "OWN_COLLECTION"
083ms
And
Set advice window in schedule
2s 590ms
And
Fill advice form
14s 593ms
And
Click advice save button and wait for advice form to disappear
30s 751ms
And
Go to "TRANSPORT_TABLE"
208ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 173ms
After
Hooks.deleteTransportAfterTest()
133ms
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 220ms
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 344ms
When
Click button advice in transport table "CONTAINER"
098ms
And
Set advice window in schedule
2s 584ms
And
Fill advice form
14s 627ms
And
Click advice save button and wait for advice form to disappear
30s 763ms
And
Go to "TRANSPORT_TABLE"
186ms
Then
Check advice data in SK API database "CONTAINER"
3s 098ms
After
Hooks.deleteTransportAfterTest()
109ms
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 270ms
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
6s 844ms
When
Click button advice in transport table "TRANSPORT_ORDER"
086ms
And
Set advice window in schedule
2s 605ms
And
Fill advice form
14s 503ms
And
Click advice save button and wait for advice form to disappear
30s 726ms
And
Go to "TRANSPORT_TABLE"
247ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 040ms
After
Hooks.deleteTransportAfterTest()
123ms
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 245ms
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 331ms
When
Click button advice in transport table "CONTAINER"
100ms
And
Set advice window in schedule in the past
2s 585ms
And
Fill advice form
14s 675ms
And
Click advice save button to check error message
092ms
Then
Check if possible advice alert is displayed
018ms
After
Hooks.deleteTransportAfterTest()
131ms
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 244ms
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"
002ms
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 020ms
And
Go to "TRANSPORT_TABLE"
199ms
When
Go to transport details "OWN_COLLECTION"
4s 468ms
And
Expand advice panel
126ms
And
Edit advice in transport details
14s 004ms
And
Fill arrival date field
2s 304ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 643ms
Then
Check advice data in database after edition "OWN_COLLECTION"
038ms
After
Hooks.deleteTransportAfterTest()
148ms
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 225ms
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 444ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 063ms
And
Go to "TRANSPORT_TABLE"
173ms
When
Go to transport details "CONTAINER"
4s 493ms
And
Expand advice panel
108ms
And
Edit advice in transport details
13s 946ms
And
Fill arrival date field
2s 286ms
And
Click "save-transport-and-close" save button and wait for form to disappear
652ms
Then
Check advice data in database after edition "CONTAINER"
025ms
After
Hooks.deleteTransportAfterTest()
115ms
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 235ms
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
48s 331ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 040ms
And
Go to "TRANSPORT_TABLE"
237ms
When
Go to transport details "TRANSPORT_ORDER"
4s 474ms
And
Expand advice panel
112ms
And
Edit advice in transport details
13s 911ms
And
Fill arrival date field
2s 283ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 611ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
035ms
After
Hooks.deleteTransportAfterTest()
158ms