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 239ms
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 418ms
When
Click button advice in transport table "CONTAINER"
134ms
And
Set advice window in schedule
2s 609ms
And
Fill advice form
14s 895ms
And
Click advice save button and wait for advice form to disappear
30s 761ms
And
Go to "TRANSPORT_TABLE"
185ms
And
Go to transport details "CONTAINER"
4s 518ms
Then
Check are advice values equals
2s 323ms
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 240ms
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 "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 376ms
When
Click button advice in transport table "OWN_COLLECTION"
113ms
And
Set advice window in schedule
2s 528ms
And
Fill advice form
14s 806ms
And
Click advice save button and wait for advice form to disappear
30s 707ms
And
Go to "TRANSPORT_TABLE"
188ms
And
Go to transport details "OWN_COLLECTION"
4s 476ms
Then
Check are advice values equals
2s 307ms
After
Hooks.deleteTransportAfterTest()
113ms
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 237ms
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 235ms
When
Click button advice in transport table "TRANSPORT_ORDER"
113ms
And
Set advice window in schedule
2s 518ms
And
Fill advice form
14s 796ms
And
Click advice save button and wait for advice form to disappear
30s 744ms
And
Go to "TRANSPORT_TABLE"
226ms
And
Go to transport details "TRANSPORT_ORDER"
4s 469ms
Then
Check are advice values equals
2s 317ms
After
Hooks.deleteTransportAfterTest()
098ms
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 339ms
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 390ms
When
Click button advice in transport table "OWN_COLLECTION"
138ms
And
Set advice window in schedule
2s 502ms
And
Fill advice form
14s 796ms
And
Click advice save button and wait for advice form to disappear
30s 721ms
And
Go to "TRANSPORT_TABLE"
181ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 168ms
After
Hooks.deleteTransportAfterTest()
124ms
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 249ms
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 315ms
When
Click button advice in transport table "CONTAINER"
119ms
And
Set advice window in schedule
2s 501ms
And
Fill advice form
14s 722ms
And
Click advice save button and wait for advice form to disappear
30s 756ms
And
Go to "TRANSPORT_TABLE"
184ms
Then
Check advice data in SK API database "CONTAINER"
4s 106ms
After
Hooks.deleteTransportAfterTest()
124ms
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_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 224ms
When
Click button advice in transport table "TRANSPORT_ORDER"
114ms
And
Set advice window in schedule
2s 513ms
And
Fill advice form
14s 777ms
And
Click advice save button and wait for advice form to disappear
30s 744ms
And
Go to "TRANSPORT_TABLE"
232ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 042ms
After
Hooks.deleteTransportAfterTest()
098ms
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 247ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
9s 322ms
When
Click button advice in transport table "CONTAINER"
109ms
And
Set advice window in schedule in the past
2s 567ms
And
Fill advice form
14s 816ms
And
Click advice save button to check error message
094ms
Then
Check if possible advice alert is displayed
024ms
After
Hooks.deleteTransportAfterTest()
104ms
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 291ms
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
39s 470ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 177ms
And
Go to "TRANSPORT_TABLE"
170ms
When
Go to transport details "OWN_COLLECTION"
4s 503ms
And
Expand advice panel
123ms
And
Edit advice in transport details
14s 055ms
And
Fill arrival date field
2s 305ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 690ms
Then
Check advice data in database after edition "OWN_COLLECTION"
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 173ms
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"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
33s 983ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 220ms
And
Go to "TRANSPORT_TABLE"
161ms
When
Go to transport details "CONTAINER"
4s 488ms
And
Expand advice panel
108ms
And
Edit advice in transport details
14s 111ms
And
Fill arrival date field
2s 298ms
And
Click "save-transport-and-close" save button and wait for form to disappear
676ms
Then
Check advice data in database after edition "CONTAINER"
029ms
After
Hooks.deleteTransportAfterTest()
105ms
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 230ms
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"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
48s 352ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 188ms
And
Go to "TRANSPORT_TABLE"
211ms
When
Go to transport details "TRANSPORT_ORDER"
4s 455ms
And
Expand advice panel
125ms
And
Edit advice in transport details
14s 070ms
And
Fill arrival date field
2s 289ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 648ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
031ms
After
Hooks.deleteTransportAfterTest()
125ms