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 190ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
004ms
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 382ms
When
Click button advice in transport table "CONTAINER"
087ms
And
Set advice window in schedule
2s 651ms
And
Fill advice form
14s 508ms
And
Click advice save button and wait for advice form to disappear
30s 734ms
And
Go to "TRANSPORT_TABLE"
207ms
And
Go to transport details "CONTAINER"
4s 502ms
Then
Check are advice values equals
2s 308ms
After
Hooks.deleteTransportAfterTest()
148ms
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 218ms
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"
004ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 367ms
When
Click button advice in transport table "OWN_COLLECTION"
081ms
And
Set advice window in schedule
2s 559ms
And
Fill advice form
14s 568ms
And
Click advice save button and wait for advice form to disappear
30s 753ms
And
Go to "TRANSPORT_TABLE"
182ms
And
Go to transport details "OWN_COLLECTION"
4s 472ms
Then
Check are advice values equals
2s 306ms
After
Hooks.deleteTransportAfterTest()
126ms
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 213ms
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
3s 816ms
When
Click button advice in transport table "TRANSPORT_ORDER"
086ms
And
Set advice window in schedule
2s 564ms
And
Fill advice form
14s 536ms
And
Click advice save button and wait for advice form to disappear
30s 736ms
And
Go to "TRANSPORT_TABLE"
231ms
And
Go to transport details "TRANSPORT_ORDER"
4s 426ms
Then
Check are advice values equals
2s 304ms
After
Hooks.deleteTransportAfterTest()
122ms
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 167ms
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
6s 380ms
When
Click button advice in transport table "OWN_COLLECTION"
082ms
And
Set advice window in schedule
2s 586ms
And
Fill advice form
14s 528ms
And
Click advice save button and wait for advice form to disappear
30s 671ms
And
Go to "TRANSPORT_TABLE"
163ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 194ms
After
Hooks.deleteTransportAfterTest()
156ms
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 188ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
004ms
And
Add transport by SKApi in "MGW"
004ms
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 300ms
When
Click button advice in transport table "CONTAINER"
074ms
And
Set advice window in schedule
2s 586ms
And
Fill advice form
14s 513ms
And
Click advice save button and wait for advice form to disappear
30s 724ms
And
Go to "TRANSPORT_TABLE"
192ms
Then
Check advice data in SK API database "CONTAINER"
4s 104ms
After
Hooks.deleteTransportAfterTest()
149ms
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 222ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
010ms
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 199ms
When
Click button advice in transport table "TRANSPORT_ORDER"
082ms
And
Set advice window in schedule
2s 578ms
And
Fill advice form
14s 577ms
And
Click advice save button and wait for advice form to disappear
30s 702ms
And
Go to "TRANSPORT_TABLE"
254ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 050ms
After
Hooks.deleteTransportAfterTest()
108ms
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 213ms
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 313ms
When
Click button advice in transport table "CONTAINER"
078ms
And
Set advice window in schedule in the past
2s 570ms
And
Fill advice form
14s 769ms
And
Click advice save button to check error message
082ms
Then
Check if possible advice alert is displayed
019ms
After
Hooks.deleteTransportAfterTest()
137ms
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 175ms
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"
008ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
42s 422ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
55s 569ms
And
Go to "TRANSPORT_TABLE"
194ms
When
Go to transport details "OWN_COLLECTION"
4s 439ms
And
Expand advice panel
106ms
And
Edit advice in transport details
13s 946ms
And
Fill arrival date field
2s 268ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 143ms
Then
Check advice data in database after edition "OWN_COLLECTION"
035ms
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 224ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
004ms
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
24s 340ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 047ms
And
Go to "TRANSPORT_TABLE"
176ms
When
Go to transport details "CONTAINER"
4s 477ms
And
Expand advice panel
107ms
And
Edit advice in transport details
13s 973ms
And
Fill arrival date field
2s 262ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 629ms
Then
Check advice data in database after edition "CONTAINER"
035ms
After
Hooks.deleteTransportAfterTest()
107ms
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 174ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
008ms
And
Add transport by SKApi in "MGW"
007ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
003ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
36s 353ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
47s 935ms
And
Go to "TRANSPORT_TABLE"
213ms
When
Go to transport details "TRANSPORT_ORDER"
4s 455ms
And
Expand advice panel
100ms
And
Edit advice in transport details
13s 936ms
And
Fill arrival date field
2s 270ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 585ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
035ms
After
Hooks.deleteTransportAfterTest()
105ms