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 239ms
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
51s 414ms
When
Click button advice in transport table "CONTAINER"
097ms
And
Set advice window in schedule
2s 787ms
And
Fill advice form
14s 696ms
And
Click advice save button and wait for advice form to disappear
31s 272ms
And
Go to "TRANSPORT_TABLE"
200ms
And
Go to transport details "CONTAINER"
4s 523ms
Then
Check are advice values equals
2s 325ms
After
Hooks.deleteTransportAfterTest()
150ms
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"
001ms
And
Add transport by SKApi in "MGW"
001ms
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 364ms
When
Click button advice in transport table "OWN_COLLECTION"
094ms
And
Set advice window in schedule
2s 612ms
And
Fill advice form
14s 587ms
And
Click advice save button and wait for advice form to disappear
30s 737ms
And
Go to "TRANSPORT_TABLE"
204ms
And
Go to transport details "OWN_COLLECTION"
4s 596ms
Then
Check are advice values equals
2s 318ms
After
Hooks.deleteTransportAfterTest()
161ms
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 251ms
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 236ms
When
Click button advice in transport table "TRANSPORT_ORDER"
074ms
And
Set advice window in schedule
2s 603ms
And
Fill advice form
14s 579ms
And
Click advice save button and wait for advice form to disappear
31s 244ms
And
Go to "TRANSPORT_TABLE"
259ms
And
Go to transport details "TRANSPORT_ORDER"
4s 495ms
Then
Check are advice values equals
2s 322ms
After
Hooks.deleteTransportAfterTest()
114ms
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 288ms
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 369ms
When
Click button advice in transport table "OWN_COLLECTION"
090ms
And
Set advice window in schedule
2s 658ms
And
Fill advice form
14s 608ms
And
Click advice save button and wait for advice form to disappear
30s 750ms
And
Go to "TRANSPORT_TABLE"
177ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 164ms
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 256ms
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 301ms
When
Click button advice in transport table "CONTAINER"
097ms
And
Set advice window in schedule
2s 595ms
And
Fill advice form
14s 605ms
And
Click advice save button and wait for advice form to disappear
30s 705ms
And
Go to "TRANSPORT_TABLE"
198ms
Then
Check advice data in SK API database "CONTAINER"
4s 103ms
After
Hooks.deleteTransportAfterTest()
134ms
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 326ms
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 230ms
When
Click button advice in transport table "TRANSPORT_ORDER"
107ms
And
Set advice window in schedule
2s 573ms
And
Fill advice form
14s 588ms
And
Click advice save button and wait for advice form to disappear
31s 313ms
And
Go to "TRANSPORT_TABLE"
232ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 039ms
After
Hooks.deleteTransportAfterTest()
113ms
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 280ms
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 318ms
When
Click button advice in transport table "CONTAINER"
081ms
And
Set advice window in schedule in the past
2s 586ms
And
Fill advice form
14s 610ms
And
Click advice save button to check error message
102ms
Then
Check if possible advice alert is displayed
016ms
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 244ms
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"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
39s 453ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 016ms
And
Go to "TRANSPORT_TABLE"
206ms
When
Go to transport details "OWN_COLLECTION"
4s 511ms
And
Expand advice panel
110ms
And
Edit advice in transport details
14s 024ms
And
Fill arrival date field
2s 303ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 582ms
Then
Check advice data in database after edition "OWN_COLLECTION"
040ms
After
Hooks.deleteTransportAfterTest()
190ms
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 238ms
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 404ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 594ms
And
Go to "TRANSPORT_TABLE"
185ms
When
Go to transport details "CONTAINER"
4s 525ms
And
Expand advice panel
113ms
And
Edit advice in transport details
13s 967ms
And
Fill arrival date field
2s 293ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 624ms
Then
Check advice data in database after edition "CONTAINER"
031ms
After
Hooks.deleteTransportAfterTest()
173ms
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 223ms
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"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 322ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 071ms
And
Go to "TRANSPORT_TABLE"
255ms
When
Go to transport details "TRANSPORT_ORDER"
4s 491ms
And
Expand advice panel
088ms
And
Edit advice in transport details
14s 014ms
And
Fill arrival date field
2s 285ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 616ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
037ms
After
Hooks.deleteTransportAfterTest()
141ms