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 234ms
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"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
54s 384ms
When
Click button advice in transport table "CONTAINER"
131ms
And
Set advice window in schedule
2s 606ms
And
Fill advice form
14s 645ms
And
Click advice save button and wait for advice form to disappear
30s 797ms
And
Go to "TRANSPORT_TABLE"
170ms
And
Go to transport details "CONTAINER"
4s 487ms
Then
Check are advice values equals
2s 319ms
After
Hooks.deleteTransportAfterTest()
139ms
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 267ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
3s 384ms
When
Click button advice in transport table "OWN_COLLECTION"
120ms
And
Set advice window in schedule
2s 595ms
And
Fill advice form
14s 540ms
And
Click advice save button and wait for advice form to disappear
30s 702ms
And
Go to "TRANSPORT_TABLE"
175ms
And
Go to transport details "OWN_COLLECTION"
4s 453ms
Then
Check are advice values equals
2s 330ms
After
Hooks.deleteTransportAfterTest()
117ms
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 273ms
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 225ms
When
Click button advice in transport table "TRANSPORT_ORDER"
106ms
And
Set advice window in schedule
2s 497ms
And
Fill advice form
14s 534ms
And
Click advice save button and wait for advice form to disappear
30s 781ms
And
Go to "TRANSPORT_TABLE"
236ms
And
Go to transport details "TRANSPORT_ORDER"
4s 457ms
Then
Check are advice values equals
2s 339ms
After
Hooks.deleteTransportAfterTest()
121ms
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 185ms
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 383ms
When
Click button advice in transport table "OWN_COLLECTION"
119ms
And
Set advice window in schedule
2s 522ms
And
Fill advice form
14s 618ms
And
Click advice save button and wait for advice form to disappear
30s 755ms
And
Go to "TRANSPORT_TABLE"
195ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 178ms
After
Hooks.deleteTransportAfterTest()
129ms
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 226ms
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
9s 345ms
When
Click button advice in transport table "CONTAINER"
119ms
And
Set advice window in schedule
2s 580ms
And
Fill advice form
14s 696ms
And
Click advice save button and wait for advice form to disappear
30s 707ms
And
Go to "TRANSPORT_TABLE"
172ms
Then
Check advice data in SK API database "CONTAINER"
1s 105ms
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 214ms
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
6s 804ms
When
Click button advice in transport table "TRANSPORT_ORDER"
110ms
And
Set advice window in schedule
2s 530ms
And
Fill advice form
14s 617ms
And
Click advice save button and wait for advice form to disappear
30s 773ms
And
Go to "TRANSPORT_TABLE"
224ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 049ms
After
Hooks.deleteTransportAfterTest()
129ms
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 228ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
004ms
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 326ms
When
Click button advice in transport table "CONTAINER"
116ms
And
Set advice window in schedule in the past
2s 506ms
And
Fill advice form
14s 595ms
And
Click advice save button to check error message
087ms
Then
Check if possible advice alert is displayed
083ms
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 285ms
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 481ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 051ms
And
Go to "TRANSPORT_TABLE"
172ms
When
Go to transport details "OWN_COLLECTION"
4s 466ms
And
Expand advice panel
119ms
And
Edit advice in transport details
14s 022ms
And
Fill arrival date field
2s 313ms
And
Click "save-transport-and-close" save button and wait for form to disappear
658ms
Then
Check advice data in database after edition "OWN_COLLECTION"
034ms
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 183ms
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
48s 382ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 016ms
And
Go to "TRANSPORT_TABLE"
186ms
When
Go to transport details "CONTAINER"
4s 546ms
And
Expand advice panel
117ms
And
Edit advice in transport details
14s 139ms
And
Fill arrival date field
2s 297ms
And
Click "save-transport-and-close" save button and wait for form to disappear
655ms
Then
Check advice data in database after edition "CONTAINER"
033ms
After
Hooks.deleteTransportAfterTest()
146ms
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_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 309ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 456ms
And
Go to "TRANSPORT_TABLE"
216ms
When
Go to transport details "TRANSPORT_ORDER"
4s 452ms
And
Expand advice panel
115ms
And
Edit advice in transport details
14s 065ms
And
Fill arrival date field
2s 304ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 143ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
035ms
After
Hooks.deleteTransportAfterTest()
148ms