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 211ms
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 402ms
When
Click button advice in transport table "CONTAINER"
126ms
And
Set advice window in schedule
2s 730ms
And
Fill advice form
14s 854ms
And
Click advice save button and wait for advice form to disappear
31s 270ms
And
Go to "TRANSPORT_TABLE"
215ms
And
Go to transport details "CONTAINER"
4s 521ms
Then
Check are advice values equals
2s 293ms
After
Hooks.deleteTransportAfterTest()
141ms
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 234ms
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"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 374ms
When
Click button advice in transport table "OWN_COLLECTION"
117ms
And
Set advice window in schedule
2s 548ms
And
Fill advice form
14s 709ms
And
Click advice save button and wait for advice form to disappear
30s 770ms
And
Go to "TRANSPORT_TABLE"
213ms
And
Go to transport details "OWN_COLLECTION"
4s 453ms
Then
Check are advice values equals
2s 330ms
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 224ms
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 237ms
When
Click button advice in transport table "TRANSPORT_ORDER"
118ms
And
Set advice window in schedule
2s 530ms
And
Fill advice form
14s 719ms
And
Click advice save button and wait for advice form to disappear
30s 720ms
And
Go to "TRANSPORT_TABLE"
197ms
And
Go to transport details "TRANSPORT_ORDER"
4s 478ms
Then
Check are advice values equals
2s 326ms
After
Hooks.deleteTransportAfterTest()
103ms
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 220ms
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 356ms
When
Click button advice in transport table "OWN_COLLECTION"
126ms
And
Set advice window in schedule
2s 525ms
And
Fill advice form
14s 645ms
And
Click advice save button and wait for advice form to disappear
30s 736ms
And
Go to "TRANSPORT_TABLE"
213ms
Then
Check advice data in SK API database "OWN_COLLECTION"
3s 175ms
After
Hooks.deleteTransportAfterTest()
095ms
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 225ms
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
9s 340ms
When
Click button advice in transport table "CONTAINER"
111ms
And
Set advice window in schedule
2s 592ms
And
Fill advice form
14s 723ms
And
Click advice save button and wait for advice form to disappear
30s 695ms
And
Go to "TRANSPORT_TABLE"
189ms
Then
Check advice data in SK API database "CONTAINER"
1s 087ms
After
Hooks.deleteTransportAfterTest()
111ms
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 234ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
002ms
And
Add transport by SKApi in "MGW"
001ms
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 784ms
When
Click button advice in transport table "TRANSPORT_ORDER"
118ms
And
Set advice window in schedule
2s 530ms
And
Fill advice form
14s 826ms
And
Click advice save button and wait for advice form to disappear
30s 704ms
And
Go to "TRANSPORT_TABLE"
226ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
3s 051ms
After
Hooks.deleteTransportAfterTest()
125ms
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 228ms
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
9s 362ms
When
Click button advice in transport table "CONTAINER"
102ms
And
Set advice window in schedule in the past
2s 633ms
And
Fill advice form
14s 775ms
And
Click advice save button to check error message
094ms
Then
Check if possible advice alert is displayed
020ms
After
Hooks.deleteTransportAfterTest()
115ms
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 207ms
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
39s 424ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
48s 200ms
And
Go to "TRANSPORT_TABLE"
210ms
When
Go to transport details "OWN_COLLECTION"
4s 489ms
And
Expand advice panel
098ms
And
Edit advice in transport details
14s 168ms
And
Fill arrival date field
2s 301ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 640ms
Then
Check advice data in database after edition "OWN_COLLECTION"
032ms
After
Hooks.deleteTransportAfterTest()
107ms
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 197ms
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 382ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
48s 114ms
And
Go to "TRANSPORT_TABLE"
208ms
When
Go to transport details "CONTAINER"
4s 537ms
And
Expand advice panel
099ms
And
Edit advice in transport details
14s 234ms
And
Fill arrival date field
2s 286ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 642ms
Then
Check advice data in database after edition "CONTAINER"
032ms
After
Hooks.deleteTransportAfterTest()
126ms
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 254ms
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 314ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
48s 262ms
And
Go to "TRANSPORT_TABLE"
264ms
When
Go to transport details "TRANSPORT_ORDER"
4s 499ms
And
Expand advice panel
123ms
And
Edit advice in transport details
14s 188ms
And
Fill arrival date field
2s 311ms
And
Click "save-transport-and-close" save button and wait for form to disappear
15s 605ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
038ms
After
Hooks.deleteTransportAfterTest()
125ms