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 223ms
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
54s 408ms
When
Click button advice in transport table "CONTAINER"
094ms
And
Set advice window in schedule
2s 649ms
And
Fill advice form
14s 618ms
And
Click advice save button and wait for advice form to disappear
30s 735ms
And
Go to "TRANSPORT_TABLE"
188ms
And
Go to transport details "CONTAINER"
4s 515ms
Then
Check are advice values equals
2s 329ms
After
Hooks.deleteTransportAfterTest()
137ms
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 194ms
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 356ms
When
Click button advice in transport table "OWN_COLLECTION"
100ms
And
Set advice window in schedule
2s 590ms
And
Fill advice form
14s 587ms
And
Click advice save button and wait for advice form to disappear
30s 704ms
And
Go to "TRANSPORT_TABLE"
195ms
And
Go to transport details "OWN_COLLECTION"
4s 444ms
Then
Check are advice values equals
2s 311ms
After
Hooks.deleteTransportAfterTest()
127ms
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 219ms
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"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 237ms
When
Click button advice in transport table "TRANSPORT_ORDER"
084ms
And
Set advice window in schedule
2s 588ms
And
Fill advice form
14s 549ms
And
Click advice save button and wait for advice form to disappear
30s 698ms
And
Go to "TRANSPORT_TABLE"
248ms
And
Go to transport details "TRANSPORT_ORDER"
4s 445ms
Then
Check are advice values equals
2s 315ms
After
Hooks.deleteTransportAfterTest()
103ms
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 245ms
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 381ms
When
Click button advice in transport table "OWN_COLLECTION"
095ms
And
Set advice window in schedule
2s 567ms
And
Fill advice form
14s 569ms
And
Click advice save button and wait for advice form to disappear
30s 667ms
And
Go to "TRANSPORT_TABLE"
179ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 166ms
After
Hooks.deleteTransportAfterTest()
110ms
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"
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 313ms
When
Click button advice in transport table "CONTAINER"
089ms
And
Set advice window in schedule
2s 577ms
And
Fill advice form
14s 595ms
And
Click advice save button and wait for advice form to disappear
30s 681ms
And
Go to "TRANSPORT_TABLE"
201ms
Then
Check advice data in SK API database "CONTAINER"
4s 102ms
After
Hooks.deleteTransportAfterTest()
111ms
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 247ms
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 837ms
When
Click button advice in transport table "TRANSPORT_ORDER"
081ms
And
Set advice window in schedule
2s 584ms
And
Fill advice form
14s 678ms
And
Click advice save button and wait for advice form to disappear
30s 706ms
And
Go to "TRANSPORT_TABLE"
219ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 040ms
After
Hooks.deleteTransportAfterTest()
099ms
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 236ms
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"
010ms
And
Check is transport "CONTAINER" created in transport table and set transport id
9s 343ms
When
Click button advice in transport table "CONTAINER"
087ms
And
Set advice window in schedule in the past
2s 602ms
And
Fill advice form
14s 578ms
And
Click advice save button to check error message
073ms
Then
Check if possible advice alert is displayed
021ms
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 184ms
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
39s 431ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
47s 993ms
And
Go to "TRANSPORT_TABLE"
203ms
When
Go to transport details "OWN_COLLECTION"
4s 443ms
And
Expand advice panel
105ms
And
Edit advice in transport details
14s 017ms
And
Fill arrival date field
2s 298ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 635ms
Then
Check advice data in database after edition "OWN_COLLECTION"
038ms
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 246ms
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 382ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 112ms
And
Go to "TRANSPORT_TABLE"
212ms
When
Go to transport details "CONTAINER"
4s 528ms
And
Expand advice panel
104ms
And
Edit advice in transport details
14s 046ms
And
Fill arrival date field
2s 304ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 637ms
Then
Check advice data in database after edition "CONTAINER"
036ms
After
Hooks.deleteTransportAfterTest()
141ms
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 275ms
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 901ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s
And
Go to "TRANSPORT_TABLE"
233ms
When
Go to transport details "TRANSPORT_ORDER"
4s 441ms
And
Expand advice panel
107ms
And
Edit advice in transport details
14s 001ms
And
Fill arrival date field
2s 291ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 586ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
039ms
After
Hooks.deleteTransportAfterTest()
148ms