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"
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
55s 008ms
When
Click button advice in transport table "CONTAINER"
094ms
And
Set advice window in schedule
2s 694ms
And
Fill advice form
14s 668ms
And
Click advice save button and wait for advice form to disappear
30s 745ms
And
Go to "TRANSPORT_TABLE"
212ms
And
Go to transport details "CONTAINER"
4s 472ms
Then
Check are advice values equals
2s 333ms
After
Hooks.deleteTransportAfterTest()
143ms
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"
003ms
And
Add transport by SKApi in "MGW"
004ms
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
4s 100ms
When
Click button advice in transport table "OWN_COLLECTION"
083ms
And
Set advice window in schedule
2s 660ms
And
Fill advice form
14s 621ms
And
Click advice save button and wait for advice form to disappear
30s 736ms
And
Go to "TRANSPORT_TABLE"
207ms
And
Go to transport details "OWN_COLLECTION"
4s 445ms
Then
Check are advice values equals
2s 299ms
After
Hooks.deleteTransportAfterTest()
135ms
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 257ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id
3s 878ms
When
Click button advice in transport table "TRANSPORT_ORDER"
072ms
And
Set advice window in schedule
2s 640ms
And
Fill advice form
14s 683ms
And
Click advice save button and wait for advice form to disappear
30s 706ms
And
Go to "TRANSPORT_TABLE"
216ms
And
Go to transport details "TRANSPORT_ORDER"
4s 408ms
Then
Check are advice values equals
2s 295ms
After
Hooks.deleteTransportAfterTest()
149ms
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 310ms
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
1s 121ms
When
Click button advice in transport table "OWN_COLLECTION"
097ms
And
Set advice window in schedule
2s 614ms
And
Fill advice form
14s 622ms
And
Click advice save button and wait for advice form to disappear
30s 702ms
And
Go to "TRANSPORT_TABLE"
169ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 234ms
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 278ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
6s 974ms
When
Click button advice in transport table "CONTAINER"
080ms
And
Set advice window in schedule
2s 625ms
And
Fill advice form
14s 546ms
And
Click advice save button and wait for advice form to disappear
30s 741ms
And
Go to "TRANSPORT_TABLE"
187ms
Then
Check advice data in SK API database "CONTAINER"
3s 116ms
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 244ms
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"
003ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 921ms
When
Click button advice in transport table "TRANSPORT_ORDER"
081ms
And
Set advice window in schedule
2s 599ms
And
Fill advice form
14s 639ms
And
Click advice save button and wait for advice form to disappear
30s 721ms
And
Go to "TRANSPORT_TABLE"
188ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 035ms
After
Hooks.deleteTransportAfterTest()
153ms
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 255ms
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 984ms
When
Click button advice in transport table "CONTAINER"
069ms
And
Set advice window in schedule in the past
2s 671ms
And
Fill advice form
14s 607ms
And
Click advice save button to check error message
098ms
Then
Check if possible advice alert is displayed
017ms
After
Hooks.deleteTransportAfterTest()
147ms
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 274ms
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 "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
43s 116ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 118ms
And
Go to "TRANSPORT_TABLE"
216ms
When
Go to transport details "OWN_COLLECTION"
4s 441ms
And
Expand advice panel
108ms
And
Edit advice in transport details
13s 941ms
And
Fill arrival date field
2s 308ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 131ms
Then
Check advice data in database after edition "OWN_COLLECTION"
028ms
After
Hooks.deleteTransportAfterTest()
163ms
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 261ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
001ms
And
Add transport by SKApi in "MGW"
005ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
002ms
And
Check is transport "CONTAINER" created in transport table and set transport id
31s 032ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 143ms
And
Go to "TRANSPORT_TABLE"
173ms
When
Go to transport details "CONTAINER"
4s 501ms
And
Expand advice panel
105ms
And
Edit advice in transport details
13s 944ms
And
Fill arrival date field
2s 290ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 618ms
Then
Check advice data in database after edition "CONTAINER"
028ms
After
Hooks.deleteTransportAfterTest()
109ms
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 291ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
001ms
And
Add transport by SKApi in "MGW"
001ms
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 932ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 059ms
And
Go to "TRANSPORT_TABLE"
212ms
When
Go to transport details "TRANSPORT_ORDER"
4s 468ms
And
Expand advice panel
101ms
And
Edit advice in transport details
13s 962ms
And
Fill arrival date field
2s 281ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 658ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
026ms
After
Hooks.deleteTransportAfterTest()
139ms