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"
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 421ms
When
Click button advice in transport table "CONTAINER"
091ms
And
Set advice window in schedule
2s 802ms
And
Fill advice form
14s 647ms
And
Click advice save button and wait for advice form to disappear
15s 754ms
And
Go to "TRANSPORT_TABLE"
191ms
And
Go to transport details "CONTAINER"
4s 468ms
Then
Check are advice values equals
2s 278ms
After
Hooks.deleteTransportAfterTest()
151ms
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 256ms
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
18s 407ms
When
Click button advice in transport table "OWN_COLLECTION"
093ms
And
Set advice window in schedule
2s 648ms
And
Fill advice form
14s 552ms
And
Click advice save button and wait for advice form to disappear
30s 723ms
And
Go to "TRANSPORT_TABLE"
172ms
And
Go to transport details "OWN_COLLECTION"
4s 460ms
Then
Check are advice values equals
2s 315ms
After
Hooks.deleteTransportAfterTest()
116ms
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 269ms
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
3s 250ms
When
Click button advice in transport table "TRANSPORT_ORDER"
075ms
And
Set advice window in schedule
2s 603ms
And
Fill advice form
14s 630ms
And
Click advice save button and wait for advice form to disappear
30s 743ms
And
Go to "TRANSPORT_TABLE"
223ms
And
Go to transport details "TRANSPORT_ORDER"
4s 471ms
Then
Check are advice values equals
2s 318ms
After
Hooks.deleteTransportAfterTest()
136ms
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 253ms
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 384ms
When
Click button advice in transport table "OWN_COLLECTION"
088ms
And
Set advice window in schedule
2s 610ms
And
Fill advice form
14s 612ms
And
Click advice save button and wait for advice form to disappear
30s 719ms
And
Go to "TRANSPORT_TABLE"
216ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 179ms
After
Hooks.deleteTransportAfterTest()
109ms
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 232ms
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"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 317ms
When
Click button advice in transport table "CONTAINER"
101ms
And
Set advice window in schedule
2s 591ms
And
Fill advice form
14s 592ms
And
Click advice save button and wait for advice form to disappear
30s 694ms
And
Go to "TRANSPORT_TABLE"
185ms
Then
Check advice data in SK API database "CONTAINER"
4s 104ms
After
Hooks.deleteTransportAfterTest()
097ms
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 218ms
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 843ms
When
Click button advice in transport table "TRANSPORT_ORDER"
079ms
And
Set advice window in schedule
2s 595ms
And
Fill advice form
14s 510ms
And
Click advice save button and wait for advice form to disappear
30s 710ms
And
Go to "TRANSPORT_TABLE"
246ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 041ms
After
Hooks.deleteTransportAfterTest()
092ms
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 195ms
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"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
9s 362ms
When
Click button advice in transport table "CONTAINER"
094ms
And
Set advice window in schedule in the past
2s 622ms
And
Fill advice form
14s 647ms
And
Click advice save button to check error message
092ms
Then
Check if possible advice alert is displayed
019ms
After
Hooks.deleteTransportAfterTest()
148ms
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 247ms
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 465ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
47s 988ms
And
Go to "TRANSPORT_TABLE"
217ms
When
Go to transport details "OWN_COLLECTION"
4s 500ms
And
Expand advice panel
105ms
And
Edit advice in transport details
14s 031ms
And
Fill arrival date field
2s 294ms
And
Click "save-transport-and-close" save button and wait for form to disappear
659ms
Then
Check advice data in database after edition "OWN_COLLECTION"
032ms
After
Hooks.deleteTransportAfterTest()
145ms
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 210ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
48s 979ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 049ms
And
Go to "TRANSPORT_TABLE"
204ms
When
Go to transport details "CONTAINER"
4s 527ms
And
Expand advice panel
108ms
And
Edit advice in transport details
13s 997ms
And
Fill arrival date field
2s 273ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 182ms
Then
Check advice data in database after edition "CONTAINER"
037ms
After
Hooks.deleteTransportAfterTest()
166ms
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 236ms
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 357ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 084ms
And
Go to "TRANSPORT_TABLE"
252ms
When
Go to transport details "TRANSPORT_ORDER"
4s 545ms
And
Expand advice panel
104ms
And
Edit advice in transport details
13s 981ms
And
Fill arrival date field
2s 284ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 595ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
029ms
After
Hooks.deleteTransportAfterTest()
145ms