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 223ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
010ms
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 434ms
When
Click button advice in transport table "CONTAINER"
082ms
And
Set advice window in schedule
2s 782ms
And
Fill advice form
14s 608ms
And
Click advice save button and wait for advice form to disappear
31s 248ms
And
Go to "TRANSPORT_TABLE"
197ms
And
Go to transport details "CONTAINER"
4s 507ms
Then
Check are advice values equals
2s 316ms
After
Hooks.deleteTransportAfterTest()
101ms
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 207ms
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"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 390ms
When
Click button advice in transport table "OWN_COLLECTION"
094ms
And
Set advice window in schedule
2s 627ms
And
Fill advice form
14s 571ms
And
Click advice save button and wait for advice form to disappear
30s 715ms
And
Go to "TRANSPORT_TABLE"
192ms
And
Go to transport details "OWN_COLLECTION"
4s 474ms
Then
Check are advice values equals
2s 333ms
After
Hooks.deleteTransportAfterTest()
170ms
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 182ms
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 262ms
When
Click button advice in transport table "TRANSPORT_ORDER"
085ms
And
Set advice window in schedule
2s 576ms
And
Fill advice form
14s 570ms
And
Click advice save button and wait for advice form to disappear
30s 703ms
And
Go to "TRANSPORT_TABLE"
224ms
And
Go to transport details "TRANSPORT_ORDER"
4s 484ms
Then
Check are advice values equals
2s 312ms
After
Hooks.deleteTransportAfterTest()
119ms
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 253ms
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 386ms
When
Click button advice in transport table "OWN_COLLECTION"
094ms
And
Set advice window in schedule
2s 595ms
And
Fill advice form
14s 548ms
And
Click advice save button and wait for advice form to disappear
30s 730ms
And
Go to "TRANSPORT_TABLE"
193ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 164ms
After
Hooks.deleteTransportAfterTest()
134ms
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 269ms
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 325ms
When
Click button advice in transport table "CONTAINER"
090ms
And
Set advice window in schedule
2s 597ms
And
Fill advice form
14s 567ms
And
Click advice save button and wait for advice form to disappear
30s 724ms
And
Go to "TRANSPORT_TABLE"
220ms
Then
Check advice data in SK API database "CONTAINER"
4s 108ms
After
Hooks.deleteTransportAfterTest()
169ms
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 262ms
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 227ms
When
Click button advice in transport table "TRANSPORT_ORDER"
075ms
And
Set advice window in schedule
2s 566ms
And
Fill advice form
14s 664ms
And
Click advice save button and wait for advice form to disappear
30s 711ms
And
Go to "TRANSPORT_TABLE"
225ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 045ms
After
Hooks.deleteTransportAfterTest()
140ms
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 294ms
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 333ms
When
Click button advice in transport table "CONTAINER"
099ms
And
Set advice window in schedule in the past
2s 678ms
And
Fill advice form
14s 591ms
And
Click advice save button to check error message
083ms
Then
Check if possible advice alert is displayed
019ms
After
Hooks.deleteTransportAfterTest()
093ms
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 260ms
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"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
42s 480ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 212ms
And
Go to "TRANSPORT_TABLE"
216ms
When
Go to transport details "OWN_COLLECTION"
4s 472ms
And
Expand advice panel
088ms
And
Edit advice in transport details
14s 049ms
And
Fill arrival date field
2s 308ms
And
Click "save-transport-and-close" save button and wait for form to disappear
648ms
Then
Check advice data in database after edition "OWN_COLLECTION"
035ms
After
Hooks.deleteTransportAfterTest()
117ms
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 220ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
48s 437ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
47s 991ms
And
Go to "TRANSPORT_TABLE"
209ms
When
Go to transport details "CONTAINER"
4s 522ms
And
Expand advice panel
101ms
And
Edit advice in transport details
13s 983ms
And
Fill arrival date field
2s 289ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 612ms
Then
Check advice data in database after edition "CONTAINER"
039ms
After
Hooks.deleteTransportAfterTest()
157ms
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 262ms
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"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 345ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 098ms
And
Go to "TRANSPORT_TABLE"
264ms
When
Go to transport details "TRANSPORT_ORDER"
4s 514ms
And
Expand advice panel
115ms
And
Edit advice in transport details
13s 995ms
And
Fill arrival date field
2s 290ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 613ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
039ms
After
Hooks.deleteTransportAfterTest()
131ms