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 288ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
54s 370ms
When
Click button advice in transport table "CONTAINER"
115ms
And
Set advice window in schedule
2s 614ms
And
Fill advice form
14s 835ms
And
Click advice save button and wait for advice form to disappear
30s 787ms
And
Go to "TRANSPORT_TABLE"
192ms
And
Go to transport details "CONTAINER"
4s 522ms
Then
Check are advice values equals
2s 331ms
After
Hooks.deleteTransportAfterTest()
128ms
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 240ms
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 356ms
When
Click button advice in transport table "OWN_COLLECTION"
123ms
And
Set advice window in schedule
2s 548ms
And
Fill advice form
14s 736ms
And
Click advice save button and wait for advice form to disappear
30s 756ms
And
Go to "TRANSPORT_TABLE"
179ms
And
Go to transport details "OWN_COLLECTION"
4s 461ms
Then
Check are advice values equals
2s 325ms
After
Hooks.deleteTransportAfterTest()
131ms
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_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
3s 220ms
When
Click button advice in transport table "TRANSPORT_ORDER"
137ms
And
Set advice window in schedule
2s 536ms
And
Fill advice form
14s 773ms
And
Click advice save button and wait for advice form to disappear
30s 753ms
And
Go to "TRANSPORT_TABLE"
223ms
And
Go to transport details "TRANSPORT_ORDER"
4s 458ms
Then
Check are advice values equals
2s 347ms
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 248ms
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 367ms
When
Click button advice in transport table "OWN_COLLECTION"
128ms
And
Set advice window in schedule
2s 506ms
And
Fill advice form
14s 760ms
And
Click advice save button and wait for advice form to disappear
30s 679ms
And
Go to "TRANSPORT_TABLE"
187ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 175ms
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 682ms
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 338ms
When
Click button advice in transport table "CONTAINER"
117ms
And
Set advice window in schedule
2s 537ms
And
Fill advice form
14s 709ms
And
Click advice save button and wait for advice form to disappear
30s 758ms
And
Go to "TRANSPORT_TABLE"
197ms
Then
Check advice data in SK API database "CONTAINER"
3s 111ms
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 255ms
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"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 797ms
When
Click button advice in transport table "TRANSPORT_ORDER"
123ms
And
Set advice window in schedule
2s 503ms
And
Fill advice form
14s 837ms
And
Click advice save button and wait for advice form to disappear
30s 713ms
And
Go to "TRANSPORT_TABLE"
229ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 045ms
After
Hooks.deleteTransportAfterTest()
111ms
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 238ms
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"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 323ms
When
Click button advice in transport table "CONTAINER"
110ms
And
Set advice window in schedule in the past
2s 532ms
And
Fill advice form
14s 806ms
And
Click advice save button to check error message
089ms
Then
Check if possible advice alert is displayed
021ms
After
Hooks.deleteTransportAfterTest()
109ms
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_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
42s 448ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 144ms
And
Go to "TRANSPORT_TABLE"
200ms
When
Go to transport details "OWN_COLLECTION"
4s 499ms
And
Expand advice panel
115ms
And
Edit advice in transport details
14s 070ms
And
Fill arrival date field
2s 334ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 695ms
Then
Check advice data in database after edition "OWN_COLLECTION"
035ms
After
Hooks.deleteTransportAfterTest()
134ms
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 231ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
003ms
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 408ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 240ms
And
Go to "TRANSPORT_TABLE"
174ms
When
Go to transport details "CONTAINER"
4s 524ms
And
Expand advice panel
110ms
And
Edit advice in transport details
14s 155ms
And
Fill arrival date field
2s 289ms
And
Click "save-transport-and-close" save button and wait for form to disappear
691ms
Then
Check advice data in database after edition "CONTAINER"
023ms
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 200ms
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 "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
48s 313ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 230ms
And
Go to "TRANSPORT_TABLE"
226ms
When
Go to transport details "TRANSPORT_ORDER"
4s 461ms
And
Expand advice panel
122ms
And
Edit advice in transport details
14s 078ms
And
Fill arrival date field
2s 295ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 680ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
041ms
After
Hooks.deleteTransportAfterTest()
132ms