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 263ms
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 032ms
When
Click button advice in transport table "CONTAINER"
097ms
And
Set advice window in schedule
2s 705ms
And
Fill advice form
14s 712ms
And
Click advice save button and wait for advice form to disappear
15s 780ms
And
Go to "TRANSPORT_TABLE"
192ms
And
Go to transport details "CONTAINER"
4s 472ms
Then
Check are advice values equals
2s 319ms
After
Hooks.deleteTransportAfterTest()
139ms
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 263ms
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
19s 139ms
When
Click button advice in transport table "OWN_COLLECTION"
095ms
And
Set advice window in schedule
2s 677ms
And
Fill advice form
14s 664ms
And
Click advice save button and wait for advice form to disappear
30s 762ms
And
Go to "TRANSPORT_TABLE"
213ms
And
Go to transport details "OWN_COLLECTION"
4s 446ms
Then
Check are advice values equals
2s 301ms
After
Hooks.deleteTransportAfterTest()
149ms
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 278ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
003ms
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 320ms
When
Click button advice in transport table "TRANSPORT_ORDER"
088ms
And
Set advice window in schedule
2s 628ms
And
Fill advice form
14s 659ms
And
Click advice save button and wait for advice form to disappear
30s 772ms
And
Go to "TRANSPORT_TABLE"
218ms
And
Go to transport details "TRANSPORT_ORDER"
4s 433ms
Then
Check are advice values equals
2s 290ms
After
Hooks.deleteTransportAfterTest()
139ms
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 292ms
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 "CREATE_ADVICE" "super-admin-skz"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
4s 051ms
When
Click button advice in transport table "OWN_COLLECTION"
085ms
And
Set advice window in schedule
2s 651ms
And
Fill advice form
14s 583ms
And
Click advice save button and wait for advice form to disappear
30s 737ms
And
Go to "TRANSPORT_TABLE"
203ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 212ms
After
Hooks.deleteTransportAfterTest()
150ms
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 232ms
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
6s 992ms
When
Click button advice in transport table "CONTAINER"
102ms
And
Set advice window in schedule
2s 634ms
And
Fill advice form
14s 643ms
And
Click advice save button and wait for advice form to disappear
30s 803ms
And
Go to "TRANSPORT_TABLE"
186ms
Then
Check advice data in SK API database "CONTAINER"
2s 111ms
After
Hooks.deleteTransportAfterTest()
137ms
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 207ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id
6s 883ms
When
Click button advice in transport table "TRANSPORT_ORDER"
093ms
And
Set advice window in schedule
2s 621ms
And
Fill advice form
14s 731ms
And
Click advice save button and wait for advice form to disappear
30s 679ms
And
Go to "TRANSPORT_TABLE"
218ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 036ms
After
Hooks.deleteTransportAfterTest()
127ms
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 220ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
004ms
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 945ms
When
Click button advice in transport table "CONTAINER"
079ms
And
Set advice window in schedule in the past
2s 654ms
And
Fill advice form
14s 631ms
And
Click advice save button to check error message
085ms
Then
Check if possible advice alert is displayed
019ms
After
Hooks.deleteTransportAfterTest()
142ms
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 263ms
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 125ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 028ms
And
Go to "TRANSPORT_TABLE"
201ms
When
Go to transport details "OWN_COLLECTION"
4s 420ms
And
Expand advice panel
101ms
And
Edit advice in transport details
13s 951ms
And
Fill arrival date field
2s 297ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 134ms
Then
Check advice data in database after edition "OWN_COLLECTION"
035ms
After
Hooks.deleteTransportAfterTest()
140ms
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 224ms
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
33s 503ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 070ms
And
Go to "TRANSPORT_TABLE"
206ms
When
Go to transport details "CONTAINER"
4s 436ms
And
Expand advice panel
106ms
And
Edit advice in transport details
13s 924ms
And
Fill arrival date field
2s 276ms
And
Click "save-transport-and-close" save button and wait for form to disappear
635ms
Then
Check advice data in database after edition "CONTAINER"
033ms
After
Hooks.deleteTransportAfterTest()
146ms
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 227ms
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
48s 933ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 259ms
And
Go to "TRANSPORT_TABLE"
225ms
When
Go to transport details "TRANSPORT_ORDER"
4s 409ms
And
Expand advice panel
108ms
And
Edit advice in transport details
13s 973ms
And
Fill arrival date field
2s 270ms
And
Click "save-transport-and-close" save button and wait for form to disappear
661ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
027ms
After
Hooks.deleteTransportAfterTest()
147ms