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 248ms
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 400ms
When
Click button advice in transport table "CONTAINER"
138ms
And
Set advice window in schedule
2s 620ms
And
Fill advice form
14s 849ms
And
Click advice save button and wait for advice form to disappear
30s 757ms
And
Go to "TRANSPORT_TABLE"
215ms
And
Go to transport details "CONTAINER"
4s 514ms
Then
Check are advice values equals
2s 323ms
After
Hooks.deleteTransportAfterTest()
159ms
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 261ms
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 389ms
When
Click button advice in transport table "OWN_COLLECTION"
140ms
And
Set advice window in schedule
2s 517ms
And
Fill advice form
14s 761ms
And
Click advice save button and wait for advice form to disappear
30s 789ms
And
Go to "TRANSPORT_TABLE"
209ms
And
Go to transport details "OWN_COLLECTION"
4s 513ms
Then
Check are advice values equals
2s 320ms
After
Hooks.deleteTransportAfterTest()
140ms
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 307ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id
1s 139ms
When
Click button advice in transport table "TRANSPORT_ORDER"
134ms
And
Set advice window in schedule
2s 490ms
And
Fill advice form
14s 836ms
And
Click advice save button and wait for advice form to disappear
30s 687ms
And
Go to "TRANSPORT_TABLE"
196ms
And
Go to transport details "TRANSPORT_ORDER"
4s 483ms
Then
Check are advice values equals
2s 307ms
After
Hooks.deleteTransportAfterTest()
125ms
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 265ms
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 385ms
When
Click button advice in transport table "OWN_COLLECTION"
129ms
And
Set advice window in schedule
2s 470ms
And
Fill advice form
14s 724ms
And
Click advice save button and wait for advice form to disappear
30s 750ms
And
Go to "TRANSPORT_TABLE"
212ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 165ms
After
Hooks.deleteTransportAfterTest()
117ms
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 224ms
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 328ms
When
Click button advice in transport table "CONTAINER"
135ms
And
Set advice window in schedule
2s 495ms
And
Fill advice form
14s 771ms
And
Click advice save button and wait for advice form to disappear
31s 296ms
And
Go to "TRANSPORT_TABLE"
159ms
Then
Check advice data in SK API database "CONTAINER"
3s 097ms
After
Hooks.deleteTransportAfterTest()
131ms
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 220ms
When
Click button advice in transport table "TRANSPORT_ORDER"
140ms
And
Set advice window in schedule
2s 511ms
And
Fill advice form
14s 775ms
And
Click advice save button and wait for advice form to disappear
30s 736ms
And
Go to "TRANSPORT_TABLE"
246ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 042ms
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 181ms
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 329ms
When
Click button advice in transport table "CONTAINER"
125ms
And
Set advice window in schedule in the past
2s 526ms
And
Fill advice form
14s 567ms
And
Click advice save button to check error message
088ms
Then
Check if possible advice alert is displayed
018ms
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 272ms
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 "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
42s 468ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 351ms
And
Go to "TRANSPORT_TABLE"
187ms
When
Go to transport details "OWN_COLLECTION"
4s 445ms
And
Expand advice panel
114ms
And
Edit advice in transport details
14s 086ms
And
Fill arrival date field
2s 320ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 639ms
Then
Check advice data in database after edition "OWN_COLLECTION"
036ms
After
Hooks.deleteTransportAfterTest()
119ms
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 232ms
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"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
33s 420ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 212ms
And
Go to "TRANSPORT_TABLE"
216ms
When
Go to transport details "CONTAINER"
4s 495ms
And
Expand advice panel
120ms
And
Edit advice in transport details
14s 100ms
And
Fill arrival date field
2s 306ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 592ms
Then
Check advice data in database after edition "CONTAINER"
036ms
After
Hooks.deleteTransportAfterTest()
126ms
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 209ms
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
33s 334ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 228ms
And
Go to "TRANSPORT_TABLE"
224ms
When
Go to transport details "TRANSPORT_ORDER"
4s 490ms
And
Expand advice panel
113ms
And
Edit advice in transport details
14s 084ms
And
Fill arrival date field
2s 305ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 647ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
034ms
After
Hooks.deleteTransportAfterTest()
119ms