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 250ms
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
55s 028ms
When
Click button advice in transport table "CONTAINER"
091ms
And
Set advice window in schedule
2s 678ms
And
Fill advice form
14s 627ms
And
Click advice save button and wait for advice form to disappear
30s 718ms
And
Go to "TRANSPORT_TABLE"
224ms
And
Go to transport details "CONTAINER"
4s 497ms
Then
Check are advice values equals
2s 307ms
After
Hooks.deleteTransportAfterTest()
170ms
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 232ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
006ms
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
1m 3s 550ms
When
Click button advice in transport table "OWN_COLLECTION"
075ms
And
Set advice window in schedule
2s 612ms
And
Fill advice form
14s 656ms
And
Click advice save button and wait for advice form to disappear
30s 759ms
And
Go to "TRANSPORT_TABLE"
195ms
And
Go to transport details "OWN_COLLECTION"
4s 550ms
Then
Check are advice values equals
2s 316ms
After
Hooks.deleteTransportAfterTest()
169ms
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 250ms
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
1m 962ms
When
Click button advice in transport table "TRANSPORT_ORDER"
089ms
And
Set advice window in schedule
2s 656ms
And
Fill advice form
14s 584ms
And
Click advice save button and wait for advice form to disappear
30s 697ms
And
Go to "TRANSPORT_TABLE"
364ms
And
Go to transport details "TRANSPORT_ORDER"
4s 543ms
Then
Check are advice values equals
2s 383ms
After
Hooks.deleteTransportAfterTest()
164ms
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 242ms
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
4s 076ms
When
Click button advice in transport table "OWN_COLLECTION"
092ms
And
Set advice window in schedule
2s 650ms
And
Fill advice form
14s 708ms
And
Click advice save button and wait for advice form to disappear
30s 739ms
And
Go to "TRANSPORT_TABLE"
222ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 216ms
After
Hooks.deleteTransportAfterTest()
210ms
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 286ms
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
6s 960ms
When
Click button advice in transport table "CONTAINER"
095ms
And
Set advice window in schedule
2s 639ms
And
Fill advice form
14s 637ms
And
Click advice save button and wait for advice form to disappear
31s 251ms
And
Go to "TRANSPORT_TABLE"
135ms
Then
Check advice data in SK API database "CONTAINER"
2s 116ms
After
Hooks.deleteTransportAfterTest()
219ms
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 501ms
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 872ms
When
Click button advice in transport table "TRANSPORT_ORDER"
097ms
And
Set advice window in schedule
2s 627ms
And
Fill advice form
14s 708ms
And
Click advice save button and wait for advice form to disappear
30s 766ms
And
Go to "TRANSPORT_TABLE"
206ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 039ms
After
Hooks.deleteTransportAfterTest()
240ms
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 545ms
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
6s 944ms
When
Click button advice in transport table "CONTAINER"
096ms
And
Set advice window in schedule in the past
2s 614ms
And
Fill advice form
14s 563ms
And
Click advice save button to check error message
084ms
Then
Check if possible advice alert is displayed
019ms
After
Hooks.deleteTransportAfterTest()
144ms
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 264ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
004ms
And
Add transport by SKApi in "MGW"
003ms
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
40s 092ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
47s 957ms
And
Go to "TRANSPORT_TABLE"
191ms
When
Go to transport details "OWN_COLLECTION"
4s 418ms
And
Expand advice panel
083ms
And
Edit advice in transport details
14s 021ms
And
Fill arrival date field
2s 278ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 101ms
Then
Check advice data in database after edition "OWN_COLLECTION"
029ms
After
Hooks.deleteTransportAfterTest()
194ms
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 687ms
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
34s 005ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 133ms
And
Go to "TRANSPORT_TABLE"
251ms
When
Go to transport details "CONTAINER"
4s 471ms
And
Expand advice panel
086ms
And
Edit advice in transport details
13s 959ms
And
Fill arrival date field
2s 277ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 658ms
Then
Check advice data in database after edition "CONTAINER"
029ms
After
Hooks.deleteTransportAfterTest()
213ms
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 645ms
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 993ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 183ms
And
Go to "TRANSPORT_TABLE"
241ms
When
Go to transport details "TRANSPORT_ORDER"
4s 596ms
And
Expand advice panel
112ms
And
Edit advice in transport details
13s 969ms
And
Fill arrival date field
2s 308ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 114ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
039ms
After
Hooks.deleteTransportAfterTest()
177ms