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 236ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
002ms
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 410ms
When
Click button advice in transport table "CONTAINER"
087ms
And
Set advice window in schedule
6s 011ms
And
Fill advice form
14s 682ms
And
Click advice save button and wait for advice form to disappear
31s 267ms
And
Go to "TRANSPORT_TABLE"
177ms
And
Go to transport details "CONTAINER"
4s 441ms
Then
Check are advice values equals
2s 334ms
After
Hooks.deleteTransportAfterTest()
3s 252ms
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 280ms
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
55s 098ms
When
Click button advice in transport table "OWN_COLLECTION"
094ms
And
Set advice window in schedule
2s 816ms
And
Fill advice form
14s 649ms
And
Click advice save button and wait for advice form to disappear
31s 280ms
And
Go to "TRANSPORT_TABLE"
207ms
And
Go to transport details "OWN_COLLECTION"
4s 437ms
Then
Check are advice values equals
2s 328ms
After
Hooks.deleteTransportAfterTest()
285ms
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"
4s 290ms
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 "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
1m 387ms
When
Click button advice in transport table "TRANSPORT_ORDER"
081ms
And
Set advice window in schedule
2s 813ms
And
Fill advice form
14s 717ms
And
Click advice save button and wait for advice form to disappear
31s 179ms
And
Go to "TRANSPORT_TABLE"
238ms
And
Go to transport details "TRANSPORT_ORDER"
4s 470ms
Then
Check are advice values equals
2s 322ms
After
Hooks.deleteTransportAfterTest()
228ms
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 270ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
7s 134ms
When
Click button advice in transport table "OWN_COLLECTION"
081ms
And
Set advice window in schedule
2s 725ms
And
Fill advice form
14s 701ms
And
Click advice save button and wait for advice form to disappear
34s 423ms
And
Go to "TRANSPORT_TABLE"
183ms
Then
Check advice data in SK API database "OWN_COLLECTION"
204ms
After
Hooks.deleteTransportAfterTest()
124ms
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 197ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
001ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 922ms
When
Click button advice in transport table "CONTAINER"
080ms
And
Set advice window in schedule
2s 624ms
And
Fill advice form
14s 556ms
And
Click advice save button and wait for advice form to disappear
34s 796ms
And
Go to "TRANSPORT_TABLE"
154ms
Then
Check advice data in SK API database "CONTAINER"
1s 117ms
After
Hooks.deleteTransportAfterTest()
165ms
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 385ms
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
3s 202ms
When
Click button advice in transport table "TRANSPORT_ORDER"
069ms
And
Set advice window in schedule
6s 168ms
And
Fill advice form
14s 661ms
And
Click advice save button and wait for advice form to disappear
30s 696ms
And
Go to "TRANSPORT_TABLE"
255ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
033ms
After
Hooks.deleteTransportAfterTest()
360ms
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"
4s 322ms
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
3s 956ms
When
Click button advice in transport table "CONTAINER"
079ms
And
Set advice window in schedule in the past
2s 634ms
And
Fill advice form
17s 690ms
And
Click advice save button to check error message
095ms
Then
Check if possible advice alert is displayed
015ms
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 248ms
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
40s 130ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 682ms
And
Go to "TRANSPORT_TABLE"
177ms
When
Go to transport details "OWN_COLLECTION"
4s 496ms
And
Expand advice panel
090ms
And
Edit advice in transport details
13s 878ms
And
Fill arrival date field
2s 274ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 172ms
Then
Check advice data in database after edition "OWN_COLLECTION"
035ms
After
Hooks.deleteTransportAfterTest()
4s 047ms
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 442ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
004ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
25s 080ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
55s 649ms
And
Go to "TRANSPORT_TABLE"
169ms
When
Go to transport details "CONTAINER"
4s 519ms
And
Expand advice panel
100ms
And
Edit advice in transport details
13s 933ms
And
Fill arrival date field
2s 268ms
And
Click "save-transport-and-close" save button and wait for form to disappear
651ms
Then
Check advice data in database after edition "CONTAINER"
046ms
After
Hooks.deleteTransportAfterTest()
167ms
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 333ms
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
42s 384ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
51s 858ms
And
Go to "TRANSPORT_TABLE"
210ms
When
Go to transport details "TRANSPORT_ORDER"
4s 434ms
And
Expand advice panel
118ms
And
Edit advice in transport details
13s 963ms
And
Fill arrival date field
2s 280ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 120ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
029ms
After
Hooks.deleteTransportAfterTest()
917ms