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 196ms
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 402ms
When
Click button advice in transport table "CONTAINER"
094ms
And
Set advice window in schedule
2s 663ms
And
Fill advice form
14s 360ms
And
Click advice save button and wait for advice form to disappear
30s 698ms
And
Go to "TRANSPORT_TABLE"
170ms
And
Go to transport details "CONTAINER"
4s 575ms
Then
Check are advice values equals
2s 279ms
After
Hooks.deleteTransportAfterTest()
082ms
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 235ms
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 339ms
When
Click button advice in transport table "OWN_COLLECTION"
067ms
And
Set advice window in schedule
2s 676ms
And
Fill advice form
14s 413ms
And
Click advice save button and wait for advice form to disappear
30s 702ms
And
Go to "TRANSPORT_TABLE"
184ms
And
Go to transport details "OWN_COLLECTION"
4s 442ms
Then
Check are advice values equals
2s 282ms
After
Hooks.deleteTransportAfterTest()
119ms
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 274ms
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 792ms
When
Click button advice in transport table "TRANSPORT_ORDER"
087ms
And
Set advice window in schedule
2s 652ms
And
Fill advice form
14s 450ms
And
Click advice save button and wait for advice form to disappear
30s 706ms
And
Go to "TRANSPORT_TABLE"
225ms
And
Go to transport details "TRANSPORT_ORDER"
4s 523ms
Then
Check are advice values equals
2s 263ms
After
Hooks.deleteTransportAfterTest()
094ms
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 200ms
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
6s 341ms
When
Click button advice in transport table "OWN_COLLECTION"
097ms
And
Set advice window in schedule
2s 542ms
And
Fill advice form
14s 501ms
And
Click advice save button and wait for advice form to disappear
30s 733ms
And
Go to "TRANSPORT_TABLE"
157ms
Then
Check advice data in SK API database "OWN_COLLECTION"
2s 153ms
After
Hooks.deleteTransportAfterTest()
188ms
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 168ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
023ms
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 329ms
When
Click button advice in transport table "CONTAINER"
078ms
And
Set advice window in schedule
2s 542ms
And
Fill advice form
14s 466ms
And
Click advice save button and wait for advice form to disappear
30s 750ms
And
Go to "TRANSPORT_TABLE"
172ms
Then
Check advice data in SK API database "CONTAINER"
4s 110ms
After
Hooks.deleteTransportAfterTest()
097ms
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_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id
6s 209ms
When
Click button advice in transport table "TRANSPORT_ORDER"
103ms
And
Set advice window in schedule
2s 568ms
And
Fill advice form
14s 424ms
And
Click advice save button and wait for advice form to disappear
30s 704ms
And
Go to "TRANSPORT_TABLE"
213ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
4s 052ms
After
Hooks.deleteTransportAfterTest()
101ms
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 250ms
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
6s 282ms
When
Click button advice in transport table "CONTAINER"
097ms
And
Set advice window in schedule in the past
2s 552ms
And
Fill advice form
14s 453ms
And
Click advice save button to check error message
079ms
Then
Check if possible advice alert is displayed
038ms
After
Hooks.deleteTransportAfterTest()
091ms
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 395ms
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"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
42s 956ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
47s 872ms
And
Go to "TRANSPORT_TABLE"
179ms
When
Go to transport details "OWN_COLLECTION"
4s 483ms
And
Expand advice panel
088ms
And
Edit advice in transport details
13s 892ms
And
Fill arrival date field
2s 279ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 590ms
Then
Check advice data in database after edition "OWN_COLLECTION"
030ms
After
Hooks.deleteTransportAfterTest()
110ms
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 244ms
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 420ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
47s 825ms
And
Go to "TRANSPORT_TABLE"
185ms
When
Go to transport details "CONTAINER"
4s 439ms
And
Expand advice panel
098ms
And
Edit advice in transport details
13s 857ms
And
Fill arrival date field
2s 242ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 631ms
Then
Check advice data in database after edition "CONTAINER"
033ms
After
Hooks.deleteTransportAfterTest()
130ms
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 208ms
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
33s 881ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
47s 825ms
And
Go to "TRANSPORT_TABLE"
234ms
When
Go to transport details "TRANSPORT_ORDER"
4s 522ms
And
Expand advice panel
093ms
And
Edit advice in transport details
13s 841ms
And
Fill arrival date field
2s 267ms
And
Click "save-transport-and-close" save button and wait for form to disappear
16s 091ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
032ms
After
Hooks.deleteTransportAfterTest()
112ms