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 270ms
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 379ms
When
Click button advice in transport table "CONTAINER"
148ms
And
Set advice window in schedule
2s 579ms
And
Fill advice form
14s 626ms
And
Click advice save button and wait for advice form to disappear
31s 289ms
And
Go to "TRANSPORT_TABLE"
173ms
And
Go to transport details "CONTAINER"
4s 513ms
Then
Check are advice values equals
2s 319ms
After
Hooks.deleteTransportAfterTest()
098ms
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 205ms
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"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 389ms
When
Click button advice in transport table "OWN_COLLECTION"
126ms
And
Set advice window in schedule
2s 501ms
And
Fill advice form
14s 627ms
And
Click advice save button and wait for advice form to disappear
30s 817ms
And
Go to "TRANSPORT_TABLE"
182ms
And
Go to transport details "OWN_COLLECTION"
4s 472ms
Then
Check are advice values equals
2s 306ms
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 187ms
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"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 214ms
When
Click button advice in transport table "TRANSPORT_ORDER"
127ms
And
Set advice window in schedule
2s 507ms
And
Fill advice form
14s 695ms
And
Click advice save button and wait for advice form to disappear
30s 739ms
And
Go to "TRANSPORT_TABLE"
233ms
And
Go to transport details "TRANSPORT_ORDER"
4s 503ms
Then
Check are advice values equals
2s 311ms
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 276ms
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 374ms
When
Click button advice in transport table "OWN_COLLECTION"
143ms
And
Set advice window in schedule
2s 639ms
And
Fill advice form
14s 611ms
And
Click advice save button and wait for advice form to disappear
30s 768ms
And
Go to "TRANSPORT_TABLE"
201ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 172ms
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 282ms
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"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 329ms
When
Click button advice in transport table "CONTAINER"
113ms
And
Set advice window in schedule
2s 502ms
And
Fill advice form
14s 615ms
And
Click advice save button and wait for advice form to disappear
30s 747ms
And
Go to "TRANSPORT_TABLE"
167ms
Then
Check advice data in SK API database "CONTAINER"
4s 108ms
After
Hooks.deleteTransportAfterTest()
140ms
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 264ms
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 224ms
When
Click button advice in transport table "TRANSPORT_ORDER"
129ms
And
Set advice window in schedule
2s 489ms
And
Fill advice form
14s 668ms
And
Click advice save button and wait for advice form to disappear
15s 754ms
And
Go to "TRANSPORT_TABLE"
204ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
19s 100ms
After
Hooks.deleteTransportAfterTest()
133ms
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 292ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
004ms
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 310ms
When
Click button advice in transport table "CONTAINER"
125ms
And
Set advice window in schedule in the past
2s 574ms
And
Fill advice form
14s 681ms
And
Click advice save button to check error message
107ms
Then
Check if possible advice alert is displayed
096ms
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 251ms
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 442ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 153ms
And
Go to "TRANSPORT_TABLE"
172ms
When
Go to transport details "OWN_COLLECTION"
4s 455ms
And
Expand advice panel
104ms
And
Edit advice in transport details
14s 093ms
And
Fill arrival date field
2s 312ms
And
Click "save-transport-and-close" save button and wait for form to disappear
682ms
Then
Check advice data in database after edition "OWN_COLLECTION"
025ms
After
Hooks.deleteTransportAfterTest()
125ms
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 227ms
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 485ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 039ms
And
Go to "TRANSPORT_TABLE"
165ms
When
Go to transport details "CONTAINER"
4s 489ms
And
Expand advice panel
109ms
And
Edit advice in transport details
14s 057ms
And
Fill arrival date field
2s 294ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 654ms
Then
Check advice data in database after edition "CONTAINER"
045ms
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 236ms
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
33s 363ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
33s 128ms
And
Go to "TRANSPORT_TABLE"
212ms
When
Go to transport details "TRANSPORT_ORDER"
4s 403ms
And
Expand advice panel
114ms
And
Edit advice in transport details
14s 074ms
And
Fill arrival date field
2s 288ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 152ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
038ms
After
Hooks.deleteTransportAfterTest()
131ms