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 152ms
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 403ms
When
Click button advice in transport table "CONTAINER"
081ms
And
Set advice window in schedule
2s 717ms
And
Fill advice form
14s 566ms
And
Click advice save button and wait for advice form to disappear
30s 730ms
And
Go to "TRANSPORT_TABLE"
259ms
And
Go to transport details "CONTAINER"
4s 628ms
Then
Check are advice values equals
2s 310ms
After
Hooks.deleteTransportAfterTest()
094ms
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 394ms
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 370ms
When
Click button advice in transport table "OWN_COLLECTION"
107ms
And
Set advice window in schedule
2s 536ms
And
Fill advice form
14s 507ms
And
Click advice save button and wait for advice form to disappear
30s 673ms
And
Go to "TRANSPORT_TABLE"
279ms
And
Go to transport details "OWN_COLLECTION"
4s 536ms
Then
Check are advice values equals
2s 355ms
After
Hooks.deleteTransportAfterTest()
114ms
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 215ms
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 215ms
When
Click button advice in transport table "TRANSPORT_ORDER"
091ms
And
Set advice window in schedule
2s 566ms
And
Fill advice form
14s 584ms
And
Click advice save button and wait for advice form to disappear
30s 680ms
And
Go to "TRANSPORT_TABLE"
356ms
And
Go to transport details "TRANSPORT_ORDER"
4s 527ms
Then
Check are advice values equals
2s 316ms
After
Hooks.deleteTransportAfterTest()
120ms
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 170ms
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 "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 400ms
When
Click button advice in transport table "OWN_COLLECTION"
096ms
And
Set advice window in schedule
2s 558ms
And
Fill advice form
14s 563ms
And
Click advice save button and wait for advice form to disappear
30s 723ms
And
Go to "TRANSPORT_TABLE"
158ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 150ms
After
Hooks.deleteTransportAfterTest()
095ms
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 164ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
001ms
And
Add transport by SKApi in "MGW"
004ms
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 292ms
When
Click button advice in transport table "CONTAINER"
104ms
And
Set advice window in schedule
2s 554ms
And
Fill advice form
14s 561ms
And
Click advice save button and wait for advice form to disappear
30s 705ms
And
Go to "TRANSPORT_TABLE"
185ms
Then
Check advice data in SK API database "CONTAINER"
4s 103ms
After
Hooks.deleteTransportAfterTest()
104ms
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 308ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
001ms
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 218ms
When
Click button advice in transport table "TRANSPORT_ORDER"
105ms
And
Set advice window in schedule
2s 569ms
And
Fill advice form
14s 556ms
And
Click advice save button and wait for advice form to disappear
30s 744ms
And
Go to "TRANSPORT_TABLE"
240ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 043ms
After
Hooks.deleteTransportAfterTest()
141ms
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 430ms
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 378ms
When
Click button advice in transport table "CONTAINER"
087ms
And
Set advice window in schedule in the past
2s 587ms
And
Fill advice form
14s 568ms
And
Click advice save button to check error message
078ms
Then
Check if possible advice alert is displayed
022ms
After
Hooks.deleteTransportAfterTest()
112ms
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 191ms
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 474ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 026ms
And
Go to "TRANSPORT_TABLE"
149ms
When
Go to transport details "OWN_COLLECTION"
4s 497ms
And
Expand advice panel
136ms
And
Edit advice in transport details
13s 907ms
And
Fill arrival date field
2s 288ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 598ms
Then
Check advice data in database after edition "OWN_COLLECTION"
026ms
After
Hooks.deleteTransportAfterTest()
159ms
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 741ms
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
33s 401ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
47s 934ms
And
Go to "TRANSPORT_TABLE"
171ms
When
Go to transport details "CONTAINER"
4s 478ms
And
Expand advice panel
139ms
And
Edit advice in transport details
13s 923ms
And
Fill arrival date field
2s 274ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 616ms
Then
Check advice data in database after edition "CONTAINER"
026ms
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 772ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
001ms
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
33s 295ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 011ms
And
Go to "TRANSPORT_TABLE"
380ms
When
Go to transport details "TRANSPORT_ORDER"
4s 529ms
And
Expand advice panel
129ms
And
Edit advice in transport details
13s 937ms
And
Fill arrival date field
2s 270ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 653ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
031ms
After
Hooks.deleteTransportAfterTest()
145ms