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 237ms
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
54s 461ms
When
Click button advice in transport table "CONTAINER"
099ms
And
Set advice window in schedule
2s 739ms
And
Fill advice form
14s 702ms
And
Click advice save button and wait for advice form to disappear
30s 750ms
And
Go to "TRANSPORT_TABLE"
171ms
And
Go to transport details "CONTAINER"
4s 551ms
Then
Check are advice values equals
2s 270ms
After
Hooks.deleteTransportAfterTest()
156ms
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 245ms
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 432ms
When
Click button advice in transport table "OWN_COLLECTION"
097ms
And
Set advice window in schedule
2s 680ms
And
Fill advice form
14s 604ms
And
Click advice save button and wait for advice form to disappear
30s 719ms
And
Go to "TRANSPORT_TABLE"
190ms
And
Go to transport details "OWN_COLLECTION"
4s 452ms
Then
Check are advice values equals
2s 293ms
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 265ms
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"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 266ms
When
Click button advice in transport table "TRANSPORT_ORDER"
086ms
And
Set advice window in schedule
2s 676ms
And
Fill advice form
14s 625ms
And
Click advice save button and wait for advice form to disappear
30s 697ms
And
Go to "TRANSPORT_TABLE"
207ms
And
Go to transport details "TRANSPORT_ORDER"
4s 495ms
Then
Check are advice values equals
2s 332ms
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 226ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
3s 382ms
When
Click button advice in transport table "OWN_COLLECTION"
090ms
And
Set advice window in schedule
2s 633ms
And
Fill advice form
14s 589ms
And
Click advice save button and wait for advice form to disappear
30s 731ms
And
Go to "TRANSPORT_TABLE"
191ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 218ms
After
Hooks.deleteTransportAfterTest()
119ms
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 335ms
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 355ms
When
Click button advice in transport table "CONTAINER"
086ms
And
Set advice window in schedule
2s 583ms
And
Fill advice form
14s 624ms
And
Click advice save button and wait for advice form to disappear
30s 688ms
And
Go to "TRANSPORT_TABLE"
159ms
Then
Check advice data in SK API database "CONTAINER"
4s 116ms
After
Hooks.deleteTransportAfterTest()
113ms
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 296ms
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 245ms
When
Click button advice in transport table "TRANSPORT_ORDER"
089ms
And
Set advice window in schedule
2s 568ms
And
Fill advice form
14s 603ms
And
Click advice save button and wait for advice form to disappear
30s 734ms
And
Go to "TRANSPORT_TABLE"
214ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 042ms
After
Hooks.deleteTransportAfterTest()
111ms
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 151ms
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
9s 347ms
When
Click button advice in transport table "CONTAINER"
081ms
And
Set advice window in schedule in the past
2s 638ms
And
Fill advice form
14s 613ms
And
Click advice save button to check error message
083ms
Then
Check if possible advice alert is displayed
019ms
After
Hooks.deleteTransportAfterTest()
120ms
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 260ms
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 498ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 057ms
And
Go to "TRANSPORT_TABLE"
189ms
When
Go to transport details "OWN_COLLECTION"
4s 460ms
And
Expand advice panel
085ms
And
Edit advice in transport details
13s 888ms
And
Fill arrival date field
2s 219ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 575ms
Then
Check advice data in database after edition "OWN_COLLECTION"
021ms
After
Hooks.deleteTransportAfterTest()
120ms
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 254ms
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
36s 426ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 127ms
And
Go to "TRANSPORT_TABLE"
203ms
When
Go to transport details "CONTAINER"
4s 474ms
And
Expand advice panel
102ms
And
Edit advice in transport details
13s 966ms
And
Fill arrival date field
2s 296ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 632ms
Then
Check advice data in database after edition "CONTAINER"
034ms
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 267ms
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"
002ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
30s 914ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 092ms
And
Go to "TRANSPORT_TABLE"
223ms
When
Go to transport details "TRANSPORT_ORDER"
4s 462ms
And
Expand advice panel
113ms
And
Edit advice in transport details
13s 959ms
And
Fill arrival date field
2s 260ms
And
Click "save-transport-and-close" save button and wait for form to disappear
639ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
031ms
After
Hooks.deleteTransportAfterTest()
161ms