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 805ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
015ms
And
Check is transport "CONTAINER" created in transport table and set transport id
51s 976ms
When
Click button advice in transport table "CONTAINER"
239ms
And
Set advice window in schedule
3s 378ms
And
Fill advice form
18s 148ms
And
Click advice save button and wait for advice form to disappear
33s 883ms
And
Go to "TRANSPORT_TABLE"
467ms
And
Go to transport details "CONTAINER"
2s 913ms
Then
Check are advice values equals
2s 935ms
After
Hooks.deleteTransportAfterTest()
1s 043ms
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 706ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
024ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
019ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
55s 212ms
When
Click button advice in transport table "OWN_COLLECTION"
238ms
And
Set advice window in schedule
3s 390ms
And
Fill advice form
18s 063ms
And
Click advice save button and wait for advice form to disappear
33s 896ms
And
Go to "TRANSPORT_TABLE"
473ms
And
Go to transport details "OWN_COLLECTION"
2s 838ms
Then
Check are advice values equals
2s 893ms
After
Hooks.deleteTransportAfterTest()
1s 059ms
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 635ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
025ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
52s 528ms
When
Click button advice in transport table "TRANSPORT_ORDER"
246ms
And
Set advice window in schedule
3s 341ms
And
Fill advice form
18s 020ms
And
Click advice save button and wait for advice form to disappear
33s 827ms
And
Go to "TRANSPORT_TABLE"
490ms
And
Go to transport details "TRANSPORT_ORDER"
2s 899ms
Then
Check are advice values equals
2s 920ms
After
Hooks.deleteTransportAfterTest()
987ms
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 665ms
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"
017ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
55s 270ms
When
Click button advice in transport table "OWN_COLLECTION"
244ms
And
Set advice window in schedule
3s 359ms
And
Fill advice form
18s 048ms
And
Click advice save button and wait for advice form to disappear
33s 857ms
And
Go to "TRANSPORT_TABLE"
462ms
Then
Check advice data in SK API database "OWN_COLLECTION"
407ms
After
Hooks.deleteTransportAfterTest()
1s 137ms
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 705ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
022ms
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 033ms
When
Click button advice in transport table "CONTAINER"
239ms
And
Set advice window in schedule
3s 428ms
And
Fill advice form
18s 070ms
And
Click advice save button and wait for advice form to disappear
33s 894ms
And
Go to "TRANSPORT_TABLE"
449ms
Then
Check advice data in SK API database "CONTAINER"
204ms
After
Hooks.deleteTransportAfterTest()
1s 053ms
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_TRANSPORT_ORDER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
018ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
57s 712ms
When
Click button advice in transport table "TRANSPORT_ORDER"
247ms
And
Set advice window in schedule
3s 370ms
And
Fill advice form
18s 026ms
And
Click advice save button and wait for advice form to disappear
34s 037ms
And
Go to "TRANSPORT_TABLE"
461ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
094ms
After
Hooks.deleteTransportAfterTest()
1s 114ms
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 665ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
019ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 1s 029ms
When
Click button advice in transport table "CONTAINER"
228ms
And
Set advice window in schedule in the past
3s 350ms
And
Fill advice form
17s 905ms
And
Click advice save button to check error message
199ms
Then
Check if possible advice alert is displayed
067ms
After
Hooks.deleteTransportAfterTest()
819ms
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 639ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
024ms
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 228ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
55s 370ms
And
Go to "TRANSPORT_TABLE"
459ms
When
Go to transport details "OWN_COLLECTION"
2s 900ms
And
Expand advice panel
301ms
And
Edit advice in transport details
16s 702ms
And
Fill arrival date field
2s 535ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 435ms
Then
Check advice data in database after edition "OWN_COLLECTION"
105ms
After
Hooks.deleteTransportAfterTest()
1s 046ms
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 725ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
019ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
017ms
And
Check is transport "CONTAINER" created in transport table and set transport id
21s 983ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
55s 612ms
And
Go to "TRANSPORT_TABLE"
448ms
When
Go to transport details "CONTAINER"
2s 925ms
And
Expand advice panel
312ms
And
Edit advice in transport details
16s 613ms
And
Fill arrival date field
2s 544ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 489ms
Then
Check advice data in database after edition "CONTAINER"
112ms
After
Hooks.deleteTransportAfterTest()
1s
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 628ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
016ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
18s 655ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
55s 509ms
And
Go to "TRANSPORT_TABLE"
516ms
When
Go to transport details "TRANSPORT_ORDER"
2s 880ms
And
Expand advice panel
309ms
And
Edit advice in transport details
16s 678ms
And
Fill arrival date field
2s 533ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 498ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
082ms
After
Hooks.deleteTransportAfterTest()
949ms