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 214ms
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 454ms
When
Click button advice in transport table "CONTAINER"
104ms
And
Set advice window in schedule
2s 665ms
And
Fill advice form
14s 698ms
And
Click advice save button and wait for advice form to disappear
30s 759ms
And
Go to "TRANSPORT_TABLE"
161ms
And
Go to transport details "CONTAINER"
4s 480ms
Then
Check are advice values equals
2s 320ms
After
Hooks.deleteTransportAfterTest()
141ms
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 260ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
3s 382ms
When
Click button advice in transport table "OWN_COLLECTION"
130ms
And
Set advice window in schedule
2s 527ms
And
Fill advice form
14s 641ms
And
Click advice save button and wait for advice form to disappear
30s 768ms
And
Go to "TRANSPORT_TABLE"
153ms
And
Go to transport details "OWN_COLLECTION"
4s 451ms
Then
Check are advice values equals
2s 313ms
After
Hooks.deleteTransportAfterTest()
154ms
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 217ms
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 247ms
When
Click button advice in transport table "TRANSPORT_ORDER"
125ms
And
Set advice window in schedule
2s 501ms
And
Fill advice form
14s 687ms
And
Click advice save button and wait for advice form to disappear
30s 765ms
And
Go to "TRANSPORT_TABLE"
206ms
And
Go to transport details "TRANSPORT_ORDER"
4s 450ms
Then
Check are advice values equals
2s 322ms
After
Hooks.deleteTransportAfterTest()
101ms
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 217ms
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 391ms
When
Click button advice in transport table "OWN_COLLECTION"
125ms
And
Set advice window in schedule
2s 489ms
And
Fill advice form
14s 592ms
And
Click advice save button and wait for advice form to disappear
30s 743ms
And
Go to "TRANSPORT_TABLE"
182ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 177ms
After
Hooks.deleteTransportAfterTest()
120ms
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 221ms
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 326ms
When
Click button advice in transport table "CONTAINER"
119ms
And
Set advice window in schedule
2s 567ms
And
Fill advice form
14s 612ms
And
Click advice save button and wait for advice form to disappear
30s 747ms
And
Go to "TRANSPORT_TABLE"
192ms
Then
Check advice data in SK API database "CONTAINER"
3s 106ms
After
Hooks.deleteTransportAfterTest()
130ms
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 236ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
004ms
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 829ms
When
Click button advice in transport table "TRANSPORT_ORDER"
125ms
And
Set advice window in schedule
2s 529ms
And
Fill advice form
14s 665ms
And
Click advice save button and wait for advice form to disappear
30s 808ms
And
Go to "TRANSPORT_TABLE"
196ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 049ms
After
Hooks.deleteTransportAfterTest()
119ms
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 207ms
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 332ms
When
Click button advice in transport table "CONTAINER"
106ms
And
Set advice window in schedule in the past
2s 516ms
And
Fill advice form
14s 577ms
And
Click advice save button to check error message
097ms
Then
Check if possible advice alert is displayed
142ms
After
Hooks.deleteTransportAfterTest()
114ms
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 300ms
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 471ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 193ms
And
Go to "TRANSPORT_TABLE"
163ms
When
Go to transport details "OWN_COLLECTION"
4s 431ms
And
Expand advice panel
113ms
And
Edit advice in transport details
14s 054ms
And
Fill arrival date field
2s 306ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 647ms
Then
Check advice data in database after edition "OWN_COLLECTION"
040ms
After
Hooks.deleteTransportAfterTest()
139ms
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"
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 405ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 115ms
And
Go to "TRANSPORT_TABLE"
182ms
When
Go to transport details "CONTAINER"
4s 520ms
And
Expand advice panel
119ms
And
Edit advice in transport details
14s 128ms
And
Fill arrival date field
2s 257ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 166ms
Then
Check advice data in database after edition "CONTAINER"
041ms
After
Hooks.deleteTransportAfterTest()
189ms
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 259ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
001ms
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 299ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 159ms
And
Go to "TRANSPORT_TABLE"
197ms
When
Go to transport details "TRANSPORT_ORDER"
4s 456ms
And
Expand advice panel
124ms
And
Edit advice in transport details
14s 105ms
And
Fill arrival date field
2s 279ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 638ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
038ms
After
Hooks.deleteTransportAfterTest()
120ms