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 212ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
007ms
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 391ms
When
Click button advice in transport table "CONTAINER"
101ms
And
Set advice window in schedule
2s 670ms
And
Fill advice form
14s 556ms
And
Click advice save button and wait for advice form to disappear
30s 730ms
And
Go to "TRANSPORT_TABLE"
294ms
And
Go to transport details "CONTAINER"
4s 476ms
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 387ms
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 "CREATE_ADVICE" "super-admin-skz"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 331ms
When
Click button advice in transport table "OWN_COLLECTION"
081ms
And
Set advice window in schedule
2s 591ms
And
Fill advice form
14s 469ms
And
Click advice save button and wait for advice form to disappear
30s 783ms
And
Go to "TRANSPORT_TABLE"
213ms
And
Go to transport details "OWN_COLLECTION"
4s 633ms
Then
Check are advice values equals
2s 299ms
After
Hooks.deleteTransportAfterTest()
144ms
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 246ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
003ms
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 235ms
When
Click button advice in transport table "TRANSPORT_ORDER"
076ms
And
Set advice window in schedule
2s 553ms
And
Fill advice form
14s 501ms
And
Click advice save button and wait for advice form to disappear
30s 774ms
And
Go to "TRANSPORT_TABLE"
221ms
And
Go to transport details "TRANSPORT_ORDER"
4s 395ms
Then
Check are advice values equals
2s 293ms
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 212ms
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 "CREATE_ADVICE" "super-admin-skz"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
6s 378ms
When
Click button advice in transport table "OWN_COLLECTION"
087ms
And
Set advice window in schedule
2s 580ms
And
Fill advice form
14s 490ms
And
Click advice save button and wait for advice form to disappear
30s 677ms
And
Go to "TRANSPORT_TABLE"
239ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 259ms
After
Hooks.deleteTransportAfterTest()
095ms
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 192ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
005ms
And
Add transport by SKApi in "MGW"
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
010ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 325ms
When
Click button advice in transport table "CONTAINER"
087ms
And
Set advice window in schedule
2s 569ms
And
Fill advice form
14s 621ms
And
Click advice save button and wait for advice form to disappear
30s 680ms
And
Go to "TRANSPORT_TABLE"
258ms
Then
Check advice data in SK API database "CONTAINER"
4s 097ms
After
Hooks.deleteTransportAfterTest()
128ms
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_TRANSPORT_ORDER" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
005ms
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
6s 222ms
When
Click button advice in transport table "TRANSPORT_ORDER"
098ms
And
Set advice window in schedule
2s 534ms
And
Fill advice form
14s 476ms
And
Click advice save button and wait for advice form to disappear
30s 712ms
And
Go to "TRANSPORT_TABLE"
303ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 042ms
After
Hooks.deleteTransportAfterTest()
098ms
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 158ms
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
6s 312ms
When
Click button advice in transport table "CONTAINER"
086ms
And
Set advice window in schedule in the past
2s 583ms
And
Fill advice form
14s 736ms
And
Click advice save button to check error message
091ms
Then
Check if possible advice alert is displayed
021ms
After
Hooks.deleteTransportAfterTest()
113ms
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 233ms
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
42s 481ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
47s 816ms
And
Go to "TRANSPORT_TABLE"
327ms
When
Go to transport details "OWN_COLLECTION"
4s 517ms
And
Expand advice panel
103ms
And
Edit advice in transport details
13s 931ms
And
Fill arrival date field
2s 251ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 094ms
Then
Check advice data in database after edition "OWN_COLLECTION"
039ms
After
Hooks.deleteTransportAfterTest()
203ms
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 609ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
33s 480ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 027ms
And
Go to "TRANSPORT_TABLE"
271ms
When
Go to transport details "CONTAINER"
4s 523ms
And
Expand advice panel
113ms
And
Edit advice in transport details
13s 949ms
And
Fill arrival date field
2s 241ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 574ms
Then
Check advice data in database after edition "CONTAINER"
027ms
After
Hooks.deleteTransportAfterTest()
196ms
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 614ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
004ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
005ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
33s 324ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 035ms
And
Go to "TRANSPORT_TABLE"
281ms
When
Go to transport details "TRANSPORT_ORDER"
4s 478ms
And
Expand advice panel
126ms
And
Edit advice in transport details
13s 980ms
And
Fill arrival date field
2s 242ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 627ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
035ms
After
Hooks.deleteTransportAfterTest()
173ms