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 224ms
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
54s 398ms
When
Click button advice in transport table "CONTAINER"
134ms
And
Set advice window in schedule
2s 611ms
And
Fill advice form
14s 756ms
And
Click advice save button and wait for advice form to disappear
30s 797ms
And
Go to "TRANSPORT_TABLE"
178ms
And
Go to transport details "CONTAINER"
4s 501ms
Then
Check are advice values equals
2s 331ms
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 253ms
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 389ms
When
Click button advice in transport table "OWN_COLLECTION"
133ms
And
Set advice window in schedule
2s 506ms
And
Fill advice form
14s 663ms
And
Click advice save button and wait for advice form to disappear
30s 727ms
And
Go to "TRANSPORT_TABLE"
174ms
And
Go to transport details "OWN_COLLECTION"
4s 451ms
Then
Check are advice values equals
2s 349ms
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 240ms
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 220ms
When
Click button advice in transport table "TRANSPORT_ORDER"
110ms
And
Set advice window in schedule
2s 514ms
And
Fill advice form
14s 772ms
And
Click advice save button and wait for advice form to disappear
30s 772ms
And
Go to "TRANSPORT_TABLE"
209ms
And
Go to transport details "TRANSPORT_ORDER"
4s 464ms
Then
Check are advice values equals
2s 329ms
After
Hooks.deleteTransportAfterTest()
123ms
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 236ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
003ms
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 390ms
When
Click button advice in transport table "OWN_COLLECTION"
123ms
And
Set advice window in schedule
2s 506ms
And
Fill advice form
14s 784ms
And
Click advice save button and wait for advice form to disappear
30s 769ms
And
Go to "TRANSPORT_TABLE"
169ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 176ms
After
Hooks.deleteTransportAfterTest()
115ms
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 177ms
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 321ms
When
Click button advice in transport table "CONTAINER"
114ms
And
Set advice window in schedule
2s 523ms
And
Fill advice form
14s 769ms
And
Click advice save button and wait for advice form to disappear
30s 751ms
And
Go to "TRANSPORT_TABLE"
166ms
Then
Check advice data in SK API database "CONTAINER"
4s 114ms
After
Hooks.deleteTransportAfterTest()
135ms
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 157ms
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 220ms
When
Click button advice in transport table "TRANSPORT_ORDER"
128ms
And
Set advice window in schedule
2s 497ms
And
Fill advice form
14s 738ms
And
Click advice save button and wait for advice form to disappear
15s 791ms
And
Go to "TRANSPORT_TABLE"
179ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
19s 098ms
After
Hooks.deleteTransportAfterTest()
146ms
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 391ms
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 318ms
When
Click button advice in transport table "CONTAINER"
134ms
And
Set advice window in schedule in the past
2s 564ms
And
Fill advice form
14s 845ms
And
Click advice save button to check error message
086ms
Then
Check if possible advice alert is displayed
019ms
After
Hooks.deleteTransportAfterTest()
080ms
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 261ms
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 "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
42s 472ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 245ms
And
Go to "TRANSPORT_TABLE"
176ms
When
Go to transport details "OWN_COLLECTION"
4s 476ms
And
Expand advice panel
115ms
And
Edit advice in transport details
14s 122ms
And
Fill arrival date field
2s 299ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 108ms
Then
Check advice data in database after edition "OWN_COLLECTION"
028ms
After
Hooks.deleteTransportAfterTest()
141ms
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 193ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
004ms
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 397ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 261ms
And
Go to "TRANSPORT_TABLE"
169ms
When
Go to transport details "CONTAINER"
4s 518ms
And
Expand advice panel
118ms
And
Edit advice in transport details
14s 084ms
And
Fill arrival date field
2s 286ms
And
Click "save-transport-and-close" save button and wait for form to disappear
653ms
Then
Check advice data in database after edition "CONTAINER"
035ms
After
Hooks.deleteTransportAfterTest()
105ms
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 211ms
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
48s 326ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 171ms
And
Go to "TRANSPORT_TABLE"
216ms
When
Go to transport details "TRANSPORT_ORDER"
4s 454ms
And
Expand advice panel
110ms
And
Edit advice in transport details
14s 060ms
And
Fill arrival date field
2s 300ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 653ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
041ms
After
Hooks.deleteTransportAfterTest()
147ms