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 277ms
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
54s 439ms
When
Click button advice in transport table "CONTAINER"
088ms
And
Set advice window in schedule
2s 759ms
And
Fill advice form
14s 647ms
And
Click advice save button and wait for advice form to disappear
30s 764ms
And
Go to "TRANSPORT_TABLE"
200ms
And
Go to transport details "CONTAINER"
4s 487ms
Then
Check are advice values equals
2s 327ms
After
Hooks.deleteTransportAfterTest()
140ms
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 279ms
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 429ms
When
Click button advice in transport table "OWN_COLLECTION"
101ms
And
Set advice window in schedule
2s 665ms
And
Fill advice form
14s 650ms
And
Click advice save button and wait for advice form to disappear
30s 699ms
And
Go to "TRANSPORT_TABLE"
203ms
And
Go to transport details "OWN_COLLECTION"
4s 458ms
Then
Check are advice values equals
2s 318ms
After
Hooks.deleteTransportAfterTest()
165ms
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 275ms
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
3s 279ms
When
Click button advice in transport table "TRANSPORT_ORDER"
095ms
And
Set advice window in schedule
2s 618ms
And
Fill advice form
14s 610ms
And
Click advice save button and wait for advice form to disappear
30s 683ms
And
Go to "TRANSPORT_TABLE"
235ms
And
Go to transport details "TRANSPORT_ORDER"
4s 445ms
Then
Check are advice values equals
2s 328ms
After
Hooks.deleteTransportAfterTest()
146ms
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 314ms
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 "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
4s 001ms
When
Click button advice in transport table "OWN_COLLECTION"
109ms
And
Set advice window in schedule
2s 616ms
And
Fill advice form
14s 577ms
And
Click advice save button and wait for advice form to disappear
30s 687ms
And
Go to "TRANSPORT_TABLE"
196ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 207ms
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 218ms
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 373ms
When
Click button advice in transport table "CONTAINER"
092ms
And
Set advice window in schedule
2s 644ms
And
Fill advice form
14s 675ms
And
Click advice save button and wait for advice form to disappear
30s 784ms
And
Go to "TRANSPORT_TABLE"
170ms
Then
Check advice data in SK API database "CONTAINER"
3s 119ms
After
Hooks.deleteTransportAfterTest()
147ms
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 275ms
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
6s 873ms
When
Click button advice in transport table "TRANSPORT_ORDER"
083ms
And
Set advice window in schedule
2s 644ms
And
Fill advice form
14s 632ms
And
Click advice save button and wait for advice form to disappear
30s 710ms
And
Go to "TRANSPORT_TABLE"
198ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 043ms
After
Hooks.deleteTransportAfterTest()
124ms
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 193ms
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 369ms
When
Click button advice in transport table "CONTAINER"
093ms
And
Set advice window in schedule in the past
2s 616ms
And
Fill advice form
14s 640ms
And
Click advice save button to check error message
087ms
Then
Check if possible advice alert is displayed
021ms
After
Hooks.deleteTransportAfterTest()
096ms
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 271ms
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
43s 076ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 174ms
And
Go to "TRANSPORT_TABLE"
210ms
When
Go to transport details "OWN_COLLECTION"
4s 468ms
And
Expand advice panel
114ms
And
Edit advice in transport details
13s 977ms
And
Fill arrival date field
2s 281ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 176ms
Then
Check advice data in database after edition "OWN_COLLECTION"
037ms
After
Hooks.deleteTransportAfterTest()
144ms
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 256ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
33s 472ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 218ms
And
Go to "TRANSPORT_TABLE"
205ms
When
Go to transport details "CONTAINER"
4s 455ms
And
Expand advice panel
121ms
And
Edit advice in transport details
14s 030ms
And
Fill arrival date field
2s 283ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 613ms
Then
Check advice data in database after edition "CONTAINER"
039ms
After
Hooks.deleteTransportAfterTest()
168ms
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 297ms
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
33s 360ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 182ms
And
Go to "TRANSPORT_TABLE"
235ms
When
Go to transport details "TRANSPORT_ORDER"
4s 464ms
And
Expand advice panel
113ms
And
Edit advice in transport details
14s 029ms
And
Fill arrival date field
2s 284ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 592ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
039ms
After
Hooks.deleteTransportAfterTest()
148ms