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 222ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
007ms
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 958ms
When
Click button advice in transport table "CONTAINER"
121ms
And
Set advice window in schedule
2s 740ms
And
Fill advice form
14s 786ms
And
Click advice save button and wait for advice form to disappear
31s 243ms
And
Go to "TRANSPORT_TABLE"
209ms
And
Go to transport details "CONTAINER"
4s 501ms
Then
Check are advice values equals
2s 307ms
After
Hooks.deleteTransportAfterTest()
142ms
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 188ms
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 394ms
When
Click button advice in transport table "OWN_COLLECTION"
128ms
And
Set advice window in schedule
2s 540ms
And
Fill advice form
14s 657ms
And
Click advice save button and wait for advice form to disappear
30s 761ms
And
Go to "TRANSPORT_TABLE"
206ms
And
Go to transport details "OWN_COLLECTION"
4s 495ms
Then
Check are advice values equals
2s 342ms
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 219ms
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 236ms
When
Click button advice in transport table "TRANSPORT_ORDER"
132ms
And
Set advice window in schedule
2s 547ms
And
Fill advice form
14s 702ms
And
Click advice save button and wait for advice form to disappear
30s 698ms
And
Go to "TRANSPORT_TABLE"
252ms
And
Go to transport details "TRANSPORT_ORDER"
4s 494ms
Then
Check are advice values equals
2s 319ms
After
Hooks.deleteTransportAfterTest()
127ms
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 214ms
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 381ms
When
Click button advice in transport table "OWN_COLLECTION"
131ms
And
Set advice window in schedule
2s 525ms
And
Fill advice form
14s 694ms
And
Click advice save button and wait for advice form to disappear
30s 744ms
And
Go to "TRANSPORT_TABLE"
193ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 172ms
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 210ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
6s 319ms
When
Click button advice in transport table "CONTAINER"
124ms
And
Set advice window in schedule
2s 520ms
And
Fill advice form
14s 686ms
And
Click advice save button and wait for advice form to disappear
30s 754ms
And
Go to "TRANSPORT_TABLE"
209ms
Then
Check advice data in SK API database "CONTAINER"
3s 100ms
After
Hooks.deleteTransportAfterTest()
112ms
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 191ms
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 829ms
When
Click button advice in transport table "TRANSPORT_ORDER"
115ms
And
Set advice window in schedule
2s 545ms
And
Fill advice form
14s 656ms
And
Click advice save button and wait for advice form to disappear
30s 753ms
And
Go to "TRANSPORT_TABLE"
228ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 048ms
After
Hooks.deleteTransportAfterTest()
134ms
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 264ms
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
6s 316ms
When
Click button advice in transport table "CONTAINER"
117ms
And
Set advice window in schedule in the past
2s 579ms
And
Fill advice form
14s 735ms
And
Click advice save button to check error message
098ms
Then
Check if possible advice alert is displayed
022ms
After
Hooks.deleteTransportAfterTest()
095ms
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 232ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
001ms
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
42s 450ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 192ms
And
Go to "TRANSPORT_TABLE"
199ms
When
Go to transport details "OWN_COLLECTION"
4s 416ms
And
Expand advice panel
113ms
And
Edit advice in transport details
14s 147ms
And
Fill arrival date field
2s 298ms
And
Click "save-transport-and-close" save button and wait for form to disappear
640ms
Then
Check advice data in database after edition "OWN_COLLECTION"
029ms
After
Hooks.deleteTransportAfterTest()
118ms
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 358ms
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
48s 406ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 116ms
And
Go to "TRANSPORT_TABLE"
205ms
When
Go to transport details "CONTAINER"
4s 520ms
And
Expand advice panel
118ms
And
Edit advice in transport details
14s 050ms
And
Fill arrival date field
2s 274ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 654ms
Then
Check advice data in database after edition "CONTAINER"
038ms
After
Hooks.deleteTransportAfterTest()
138ms
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 242ms
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 335ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 232ms
And
Go to "TRANSPORT_TABLE"
262ms
When
Go to transport details "TRANSPORT_ORDER"
4s 473ms
And
Expand advice panel
117ms
And
Edit advice in transport details
14s 088ms
And
Fill arrival date field
2s 281ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 633ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
033ms
After
Hooks.deleteTransportAfterTest()
137ms