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 303ms
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
55s 029ms
When
Click button advice in transport table "CONTAINER"
076ms
And
Set advice window in schedule
2s 746ms
And
Fill advice form
14s 632ms
And
Click advice save button and wait for advice form to disappear
30s 742ms
And
Go to "TRANSPORT_TABLE"
219ms
And
Go to transport details "CONTAINER"
4s 470ms
Then
Check are advice values equals
2s 326ms
After
Hooks.deleteTransportAfterTest()
161ms
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 335ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
003ms
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 462ms
When
Click button advice in transport table "OWN_COLLECTION"
086ms
And
Set advice window in schedule
2s 705ms
And
Fill advice form
14s 695ms
And
Click advice save button and wait for advice form to disappear
30s 790ms
And
Go to "TRANSPORT_TABLE"
207ms
And
Go to transport details "OWN_COLLECTION"
4s 458ms
Then
Check are advice values equals
2s 314ms
After
Hooks.deleteTransportAfterTest()
147ms
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 319ms
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
1m 982ms
When
Click button advice in transport table "TRANSPORT_ORDER"
093ms
And
Set advice window in schedule
2s 691ms
And
Fill advice form
14s 693ms
And
Click advice save button and wait for advice form to disappear
30s 695ms
And
Go to "TRANSPORT_TABLE"
243ms
And
Go to transport details "TRANSPORT_ORDER"
4s 511ms
Then
Check are advice values equals
2s 321ms
After
Hooks.deleteTransportAfterTest()
154ms
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 285ms
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"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 472ms
When
Click button advice in transport table "OWN_COLLECTION"
087ms
And
Set advice window in schedule
2s 703ms
And
Fill advice form
14s 669ms
And
Click advice save button and wait for advice form to disappear
30s 734ms
And
Go to "TRANSPORT_TABLE"
197ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 200ms
After
Hooks.deleteTransportAfterTest()
116ms
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 291ms
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"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 379ms
When
Click button advice in transport table "CONTAINER"
097ms
And
Set advice window in schedule
2s 648ms
And
Fill advice form
14s 769ms
And
Click advice save button and wait for advice form to disappear
30s 688ms
And
Go to "TRANSPORT_TABLE"
193ms
Then
Check advice data in SK API database "CONTAINER"
3s 128ms
After
Hooks.deleteTransportAfterTest()
137ms
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 251ms
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
6s 286ms
When
Click button advice in transport table "TRANSPORT_ORDER"
099ms
And
Set advice window in schedule
2s 672ms
And
Fill advice form
14s 680ms
And
Click advice save button and wait for advice form to disappear
30s 733ms
And
Go to "TRANSPORT_TABLE"
226ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 044ms
After
Hooks.deleteTransportAfterTest()
153ms
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 319ms
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 944ms
When
Click button advice in transport table "CONTAINER"
091ms
And
Set advice window in schedule in the past
2s 658ms
And
Fill advice form
14s 633ms
And
Click advice save button to check error message
085ms
Then
Check if possible advice alert is displayed
019ms
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 284ms
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
40s 107ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 071ms
And
Go to "TRANSPORT_TABLE"
175ms
When
Go to transport details "OWN_COLLECTION"
4s 454ms
And
Expand advice panel
114ms
And
Edit advice in transport details
13s 965ms
And
Fill arrival date field
2s 293ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 604ms
Then
Check advice data in database after edition "OWN_COLLECTION"
029ms
After
Hooks.deleteTransportAfterTest()
135ms
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 282ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
001ms
And
Add transport by SKApi in "MGW"
001ms
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 973ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 149ms
And
Go to "TRANSPORT_TABLE"
209ms
When
Go to transport details "CONTAINER"
4s 530ms
And
Expand advice panel
114ms
And
Edit advice in transport details
13s 959ms
And
Fill arrival date field
2s 291ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 140ms
Then
Check advice data in database after edition "CONTAINER"
034ms
After
Hooks.deleteTransportAfterTest()
132ms
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 278ms
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 "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 950ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
33s 230ms
And
Go to "TRANSPORT_TABLE"
248ms
When
Go to transport details "TRANSPORT_ORDER"
4s 480ms
And
Expand advice panel
110ms
And
Edit advice in transport details
13s 989ms
And
Fill arrival date field
2s 288ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 634ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
029ms
After
Hooks.deleteTransportAfterTest()
106ms