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 257ms
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
54s 461ms
When
Click button advice in transport table "CONTAINER"
067ms
And
Set advice window in schedule
2s 724ms
And
Fill advice form
14s 747ms
And
Click advice save button and wait for advice form to disappear
30s 725ms
And
Go to "TRANSPORT_TABLE"
171ms
And
Go to transport details "CONTAINER"
4s 417ms
Then
Check are advice values equals
2s 301ms
After
Hooks.deleteTransportAfterTest()
126ms
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 375ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
003ms
And
Add transport by SKApi in "MGW"
002ms
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 431ms
When
Click button advice in transport table "OWN_COLLECTION"
079ms
And
Set advice window in schedule
2s 711ms
And
Fill advice form
14s 677ms
And
Click advice save button and wait for advice form to disappear
30s 736ms
And
Go to "TRANSPORT_TABLE"
149ms
And
Go to transport details "OWN_COLLECTION"
4s 391ms
Then
Check are advice values equals
2s 327ms
After
Hooks.deleteTransportAfterTest()
121ms
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 256ms
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 866ms
When
Click button advice in transport table "TRANSPORT_ORDER"
072ms
And
Set advice window in schedule
2s 617ms
And
Fill advice form
14s 738ms
And
Click advice save button and wait for advice form to disappear
15s 726ms
And
Go to "TRANSPORT_TABLE"
196ms
And
Go to transport details "TRANSPORT_ORDER"
4s 444ms
Then
Check are advice values equals
2s 319ms
After
Hooks.deleteTransportAfterTest()
122ms
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 313ms
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"
002ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
16s 065ms
When
Click button advice in transport table "OWN_COLLECTION"
077ms
And
Set advice window in schedule
2s 702ms
And
Fill advice form
14s 650ms
And
Click advice save button and wait for advice form to disappear
30s 689ms
And
Go to "TRANSPORT_TABLE"
165ms
Then
Check advice data in SK API database "OWN_COLLECTION"
4s 208ms
After
Hooks.deleteTransportAfterTest()
116ms
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 470ms
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 386ms
When
Click button advice in transport table "CONTAINER"
083ms
And
Set advice window in schedule
2s 657ms
And
Fill advice form
14s 677ms
And
Click advice save button and wait for advice form to disappear
30s 713ms
And
Go to "TRANSPORT_TABLE"
185ms
Then
Check advice data in SK API database "CONTAINER"
3s 134ms
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 293ms
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
6s 891ms
When
Click button advice in transport table "TRANSPORT_ORDER"
080ms
And
Set advice window in schedule
2s 667ms
And
Fill advice form
14s 668ms
And
Click advice save button and wait for advice form to disappear
30s 742ms
And
Go to "TRANSPORT_TABLE"
297ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 068ms
After
Hooks.deleteTransportAfterTest()
136ms
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 355ms
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 942ms
When
Click button advice in transport table "CONTAINER"
080ms
And
Set advice window in schedule in the past
2s 680ms
And
Fill advice form
14s 677ms
And
Click advice save button to check error message
077ms
Then
Check if possible advice alert is displayed
018ms
After
Hooks.deleteTransportAfterTest()
114ms
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 288ms
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
42s 525ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 223ms
And
Go to "TRANSPORT_TABLE"
189ms
When
Go to transport details "OWN_COLLECTION"
4s 448ms
And
Expand advice panel
119ms
And
Edit advice in transport details
13s 951ms
And
Fill arrival date field
2s 277ms
And
Click "save-transport-and-close" save button and wait for form to disappear
637ms
Then
Check advice data in database after edition "OWN_COLLECTION"
024ms
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 294ms
And
Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
49s 014ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 238ms
And
Go to "TRANSPORT_TABLE"
176ms
When
Go to transport details "CONTAINER"
4s 429ms
And
Expand advice panel
111ms
And
Edit advice in transport details
13s 986ms
And
Fill arrival date field
2s 289ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 607ms
Then
Check advice data in database after edition "CONTAINER"
035ms
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 323ms
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 396ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 174ms
And
Go to "TRANSPORT_TABLE"
215ms
When
Go to transport details "TRANSPORT_ORDER"
4s 424ms
And
Expand advice panel
108ms
And
Edit advice in transport details
14s 014ms
And
Fill arrival date field
2s 264ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 640ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
037ms
After
Hooks.deleteTransportAfterTest()
142ms