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 749ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
035ms
And
Check is transport "CONTAINER" created in transport table and set transport id
48s 994ms
When
Click button advice in transport table "CONTAINER"
233ms
And
Set advice window in schedule
3s 563ms
And
Fill advice form
18s 009ms
And
Click advice save button and wait for advice form to disappear
33s 266ms
And
Go to "TRANSPORT_TABLE"
382ms
And
Go to transport details "CONTAINER"
4s 920ms
Then
Check are advice values equals
2s 897ms
After
Hooks.deleteTransportAfterTest()
870ms
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 895ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
035ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
55s 201ms
When
Click button advice in transport table "OWN_COLLECTION"
248ms
And
Set advice window in schedule
3s 503ms
And
Fill advice form
17s 883ms
And
Click advice save button and wait for advice form to disappear
33s 268ms
And
Go to "TRANSPORT_TABLE"
473ms
And
Go to transport details "OWN_COLLECTION"
4s 963ms
Then
Check are advice values equals
2s 892ms
After
Hooks.deleteTransportAfterTest()
1s 023ms
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 692ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
51s 635ms
When
Click button advice in transport table "TRANSPORT_ORDER"
237ms
And
Set advice window in schedule
3s 508ms
And
Fill advice form
18s 018ms
And
Click advice save button and wait for advice form to disappear
33s 408ms
And
Go to "TRANSPORT_TABLE"
444ms
And
Go to transport details "TRANSPORT_ORDER"
4s 944ms
Then
Check are advice values equals
2s 929ms
After
Hooks.deleteTransportAfterTest()
1s 041ms
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 995ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
52s 135ms
When
Click button advice in transport table "OWN_COLLECTION"
198ms
And
Set advice window in schedule
3s 652ms
And
Fill advice form
17s 426ms
And
Click advice save button and wait for advice form to disappear
33s 286ms
And
Go to "TRANSPORT_TABLE"
418ms
Then
Check advice data in SK API database "OWN_COLLECTION"
371ms
After
Hooks.deleteTransportAfterTest()
877ms
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 692ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 975ms
When
Click button advice in transport table "CONTAINER"
239ms
And
Set advice window in schedule
3s 638ms
And
Fill advice form
18s 039ms
And
Click advice save button and wait for advice form to disappear
33s 232ms
And
Go to "TRANSPORT_TABLE"
426ms
Then
Check advice data in SK API database "CONTAINER"
206ms
After
Hooks.deleteTransportAfterTest()
1s 030ms
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 801ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
1m 647ms
When
Click button advice in transport table "TRANSPORT_ORDER"
229ms
And
Set advice window in schedule
3s 539ms
And
Fill advice form
18s 002ms
And
Click advice save button and wait for advice form to disappear
33s 261ms
And
Go to "TRANSPORT_TABLE"
474ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
095ms
After
Hooks.deleteTransportAfterTest()
984ms
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 792ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "CONTAINER" created in transport table and set transport id
1m 993ms
When
Click button advice in transport table "CONTAINER"
232ms
And
Set advice window in schedule in the past
3s 560ms
And
Fill advice form
17s 994ms
And
Click advice save button to check error message
167ms
Then
Check if possible advice alert is displayed
065ms
After
Hooks.deleteTransportAfterTest()
614ms
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 516ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
042ms
And
Add transport by SKApi in "MGW"
019ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
036ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
34s 122ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
54s 824ms
And
Go to "TRANSPORT_TABLE"
471ms
When
Go to transport details "OWN_COLLECTION"
4s 868ms
And
Expand advice panel
274ms
And
Edit advice in transport details
16s 560ms
And
Fill arrival date field
2s 593ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 415ms
Then
Check advice data in database after edition "OWN_COLLECTION"
103ms
After
Hooks.deleteTransportAfterTest()
935ms
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 857ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
035ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
034ms
And
Check is transport "CONTAINER" created in transport table and set transport id
18s 912ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
54s 916ms
And
Go to "TRANSPORT_TABLE"
390ms
When
Go to transport details "CONTAINER"
4s 882ms
And
Expand advice panel
262ms
And
Edit advice in transport details
16s 639ms
And
Fill arrival date field
2s 552ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 431ms
Then
Check advice data in database after edition "CONTAINER"
102ms
After
Hooks.deleteTransportAfterTest()
915ms
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 778ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
036ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
036ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
18s 590ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
40s 307ms
And
Go to "TRANSPORT_TABLE"
475ms
When
Go to transport details "TRANSPORT_ORDER"
4s 885ms
And
Expand advice panel
284ms
And
Edit advice in transport details
16s 398ms
And
Fill arrival date field
2s 668ms
And
Click "save-transport-and-close" save button and wait for form to disappear
17s 451ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
089ms
After
Hooks.deleteTransportAfterTest()
854ms