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 277ms
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
54s 454ms
When
Click button advice in transport table "CONTAINER"
085ms
And
Set advice window in schedule
2s 748ms
And
Fill advice form
14s 728ms
And
Click advice save button and wait for advice form to disappear
30s 712ms
And
Go to "TRANSPORT_TABLE"
207ms
And
Go to transport details "CONTAINER"
4s 508ms
Then
Check are advice values equals
2s 301ms
After
Hooks.deleteTransportAfterTest()
167ms
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 287ms
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
4s 004ms
When
Click button advice in transport table "OWN_COLLECTION"
101ms
And
Set advice window in schedule
2s 653ms
And
Fill advice form
14s 599ms
And
Click advice save button and wait for advice form to disappear
30s 730ms
And
Go to "TRANSPORT_TABLE"
233ms
And
Go to transport details "OWN_COLLECTION"
4s 447ms
Then
Check are advice values equals
2s 336ms
After
Hooks.deleteTransportAfterTest()
152ms
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 295ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
004ms
And
Add transport by SKApi in "MGW"
004ms
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
1m 959ms
When
Click button advice in transport table "TRANSPORT_ORDER"
088ms
And
Set advice window in schedule
2s 670ms
And
Fill advice form
14s 641ms
And
Click advice save button and wait for advice form to disappear
30s 765ms
And
Go to "TRANSPORT_TABLE"
216ms
And
Go to transport details "TRANSPORT_ORDER"
4s 456ms
Then
Check are advice values equals
2s 341ms
After
Hooks.deleteTransportAfterTest()
153ms
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 282ms
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"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 441ms
When
Click button advice in transport table "OWN_COLLECTION"
072ms
And
Set advice window in schedule
2s 628ms
And
Fill advice form
14s 600ms
And
Click advice save button and wait for advice form to disappear
30s 757ms
And
Go to "TRANSPORT_TABLE"
172ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 185ms
After
Hooks.deleteTransportAfterTest()
112ms
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 263ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
005ms
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 349ms
When
Click button advice in transport table "CONTAINER"
093ms
And
Set advice window in schedule
2s 644ms
And
Fill advice form
14s 728ms
And
Click advice save button and wait for advice form to disappear
30s 714ms
And
Go to "TRANSPORT_TABLE"
192ms
Then
Check advice data in SK API database "CONTAINER"
3s 128ms
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 309ms
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
6s 890ms
When
Click button advice in transport table "TRANSPORT_ORDER"
073ms
And
Set advice window in schedule
2s 615ms
And
Fill advice form
14s 630ms
And
Click advice save button and wait for advice form to disappear
30s 808ms
And
Go to "TRANSPORT_TABLE"
221ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 037ms
After
Hooks.deleteTransportAfterTest()
134ms
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 242ms
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 951ms
When
Click button advice in transport table "CONTAINER"
082ms
And
Set advice window in schedule in the past
2s 656ms
And
Fill advice form
14s 599ms
And
Click advice save button to check error message
093ms
Then
Check if possible advice alert is displayed
024ms
After
Hooks.deleteTransportAfterTest()
095ms
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 300ms
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 "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
42s 557ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 102ms
And
Go to "TRANSPORT_TABLE"
213ms
When
Go to transport details "OWN_COLLECTION"
4s 498ms
And
Expand advice panel
115ms
And
Edit advice in transport details
14s 055ms
And
Fill arrival date field
2s 261ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 621ms
Then
Check advice data in database after edition "OWN_COLLECTION"
037ms
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 235ms
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
34s 029ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 200ms
And
Go to "TRANSPORT_TABLE"
202ms
When
Go to transport details "CONTAINER"
4s 510ms
And
Expand advice panel
106ms
And
Edit advice in transport details
14s 050ms
And
Fill arrival date field
2s 229ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 581ms
Then
Check advice data in database after edition "CONTAINER"
035ms
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 252ms
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 965ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 219ms
And
Go to "TRANSPORT_TABLE"
266ms
When
Go to transport details "TRANSPORT_ORDER"
4s 467ms
And
Expand advice panel
118ms
And
Edit advice in transport details
14s 040ms
And
Fill arrival date field
2s 272ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 645ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
028ms
After
Hooks.deleteTransportAfterTest()
136ms