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"
2s 593ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
024ms
And
Add transport by SKApi in "MGW"
024ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
018ms
And
Check is transport "CONTAINER" created in transport table and set transport id
55s 004ms
When
Click button advice in transport table "CONTAINER"
228ms
And
Set advice window in schedule
3s 348ms
And
Fill advice form
18s 036ms
And
Click advice save button and wait for advice form to disappear
33s 827ms
And
Go to "TRANSPORT_TABLE"
456ms
And
Go to transport details "CONTAINER"
2s 915ms
Then
Check are advice values equals
2s 917ms
After
Hooks.deleteTransportAfterTest()
1s 245ms
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"
2s 645ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
017ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
55s 240ms
When
Click button advice in transport table "OWN_COLLECTION"
231ms
And
Set advice window in schedule
3s 404ms
And
Fill advice form
18s 148ms
And
Click advice save button and wait for advice form to disappear
33s 898ms
And
Go to "TRANSPORT_TABLE"
454ms
And
Go to transport details "OWN_COLLECTION"
2s 865ms
Then
Check are advice values equals
2s 904ms
After
Hooks.deleteTransportAfterTest()
1s 068ms
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"
2s 713ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
017ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
51s 733ms
When
Click button advice in transport table "TRANSPORT_ORDER"
235ms
And
Set advice window in schedule
3s 383ms
And
Fill advice form
18s 137ms
And
Click advice save button and wait for advice form to disappear
33s 776ms
And
Go to "TRANSPORT_TABLE"
518ms
And
Go to transport details "TRANSPORT_ORDER"
2s 995ms
Then
Check are advice values equals
2s 891ms
After
Hooks.deleteTransportAfterTest()
1s 004ms
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"
2s 686ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
55s 210ms
When
Click button advice in transport table "OWN_COLLECTION"
207ms
And
Set advice window in schedule
3s 304ms
And
Fill advice form
18s 074ms
And
Click advice save button and wait for advice form to disappear
33s 832ms
And
Go to "TRANSPORT_TABLE"
475ms
Then
Check advice data in SK API database "OWN_COLLECTION"
419ms
After
Hooks.deleteTransportAfterTest()
1s 086ms
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"
2s 631ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 1s 013ms
When
Click button advice in transport table "CONTAINER"
226ms
And
Set advice window in schedule
3s 331ms
And
Fill advice form
18s 080ms
And
Click advice save button and wait for advice form to disappear
33s 823ms
And
Go to "TRANSPORT_TABLE"
435ms
Then
Check advice data in SK API database "CONTAINER"
239ms
After
Hooks.deleteTransportAfterTest()
991ms
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"
2s 723ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
018ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
017ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
57s 715ms
When
Click button advice in transport table "TRANSPORT_ORDER"
239ms
And
Set advice window in schedule
3s 327ms
And
Fill advice form
18s 154ms
And
Click advice save button and wait for advice form to disappear
33s 850ms
And
Go to "TRANSPORT_TABLE"
492ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
094ms
After
Hooks.deleteTransportAfterTest()
1s 022ms
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"
2s 627ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 1s 025ms
When
Click button advice in transport table "CONTAINER"
246ms
And
Set advice window in schedule in the past
3s 355ms
And
Fill advice form
18s 188ms
And
Click advice save button to check error message
197ms
Then
Check if possible advice alert is displayed
066ms
After
Hooks.deleteTransportAfterTest()
800ms
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"
2s 758ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
017ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
34s 186ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
55s 497ms
And
Go to "TRANSPORT_TABLE"
462ms
When
Go to transport details "OWN_COLLECTION"
2s 884ms
And
Expand advice panel
295ms
And
Edit advice in transport details
16s 767ms
And
Fill arrival date field
2s 629ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 518ms
Then
Check advice data in database after edition "OWN_COLLECTION"
108ms
After
Hooks.deleteTransportAfterTest()
980ms
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"
2s 654ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW"
024ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
015ms
And
Check is transport "CONTAINER" created in transport table and set transport id
22s 006ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
55s 523ms
And
Go to "TRANSPORT_TABLE"
451ms
When
Go to transport details "CONTAINER"
2s 899ms
And
Expand advice panel
297ms
And
Edit advice in transport details
16s 590ms
And
Fill arrival date field
2s 629ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 458ms
Then
Check advice data in database after edition "CONTAINER"
104ms
After
Hooks.deleteTransportAfterTest()
957ms
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"
2s 604ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
019ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
017ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
18s 700ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
55s 644ms
And
Go to "TRANSPORT_TABLE"
474ms
When
Go to transport details "TRANSPORT_ORDER"
2s 905ms
And
Expand advice panel
298ms
And
Edit advice in transport details
16s 692ms
And
Fill arrival date field
2s 607ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 495ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
095ms
After
Hooks.deleteTransportAfterTest()
1s 019ms