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 723ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
033ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "CONTAINER" created in transport table and set transport id
52s 036ms
When
Click button advice in transport table "CONTAINER"
232ms
And
Set advice window in schedule
3s 592ms
And
Fill advice form
18s 393ms
And
Click advice save button and wait for advice form to disappear
33s 285ms
And
Go to "TRANSPORT_TABLE"
454ms
And
Go to transport details "CONTAINER"
4s 903ms
Then
Check are advice values equals
2s 900ms
After
Hooks.deleteTransportAfterTest()
856ms
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 847ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
52s 340ms
When
Click button advice in transport table "OWN_COLLECTION"
229ms
And
Set advice window in schedule
3s 561ms
And
Fill advice form
18s 269ms
And
Click advice save button and wait for advice form to disappear
33s 273ms
And
Go to "TRANSPORT_TABLE"
455ms
And
Go to transport details "OWN_COLLECTION"
4s 887ms
Then
Check are advice values equals
2s 944ms
After
Hooks.deleteTransportAfterTest()
877ms
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 767ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
071ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
51s 659ms
When
Click button advice in transport table "TRANSPORT_ORDER"
232ms
And
Set advice window in schedule
3s 563ms
And
Fill advice form
18s 187ms
And
Click advice save button and wait for advice form to disappear
33s 254ms
And
Go to "TRANSPORT_TABLE"
528ms
And
Go to transport details "TRANSPORT_ORDER"
4s 900ms
Then
Check are advice values equals
2s 857ms
After
Hooks.deleteTransportAfterTest()
993ms
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 780ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
52s 292ms
When
Click button advice in transport table "OWN_COLLECTION"
234ms
And
Set advice window in schedule
3s 537ms
And
Fill advice form
18s 138ms
And
Click advice save button and wait for advice form to disappear
33s 240ms
And
Go to "TRANSPORT_TABLE"
442ms
Then
Check advice data in SK API database "OWN_COLLECTION"
471ms
After
Hooks.deleteTransportAfterTest()
1s 005ms
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"
3s 091ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
018ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 1s 077ms
When
Click button advice in transport table "CONTAINER"
239ms
And
Set advice window in schedule
3s 513ms
And
Fill advice form
18s 089ms
And
Click advice save button and wait for advice form to disappear
33s 201ms
And
Go to "TRANSPORT_TABLE"
456ms
Then
Check advice data in SK API database "CONTAINER"
261ms
After
Hooks.deleteTransportAfterTest()
1s 036ms
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 767ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
58s 577ms
When
Click button advice in transport table "TRANSPORT_ORDER"
236ms
And
Set advice window in schedule
3s 598ms
And
Fill advice form
18s 408ms
And
Click advice save button and wait for advice form to disappear
33s 316ms
And
Go to "TRANSPORT_TABLE"
478ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
091ms
After
Hooks.deleteTransportAfterTest()
926ms
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 849ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
034ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 1s 161ms
When
Click button advice in transport table "CONTAINER"
237ms
And
Set advice window in schedule in the past
3s 553ms
And
Fill advice form
18s 187ms
And
Click advice save button to check error message
191ms
Then
Check if possible advice alert is displayed
069ms
After
Hooks.deleteTransportAfterTest()
683ms
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 606ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
033ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
037ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
34s 267ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
55s 688ms
And
Go to "TRANSPORT_TABLE"
438ms
When
Go to transport details "OWN_COLLECTION"
4s 869ms
And
Expand advice panel
268ms
And
Edit advice in transport details
16s 752ms
And
Fill arrival date field
2s 636ms
And
Click "save-transport-and-close" save button and wait for form to disappear
1s 992ms
Then
Check advice data in database after edition "OWN_COLLECTION"
097ms
After
Hooks.deleteTransportAfterTest()
1s 049ms
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 689ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
033ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
033ms
And
Check is transport "CONTAINER" created in transport table and set transport id
34s 020ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
55s 492ms
And
Go to "TRANSPORT_TABLE"
436ms
When
Go to transport details "CONTAINER"
4s 948ms
And
Expand advice panel
268ms
And
Edit advice in transport details
16s 674ms
And
Fill arrival date field
2s 635ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 022ms
Then
Check advice data in database after edition "CONTAINER"
105ms
After
Hooks.deleteTransportAfterTest()
962ms
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 763ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
033ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
033ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
16s 985ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
55s 276ms
And
Go to "TRANSPORT_TABLE"
482ms
When
Go to transport details "TRANSPORT_ORDER"
4s 889ms
And
Expand advice panel
257ms
And
Edit advice in transport details
16s 709ms
And
Fill arrival date field
2s 641ms
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"
105ms
After
Hooks.deleteTransportAfterTest()
964ms