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.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 615ms
And
Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz"
000ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 402ms
And
Add transport by SKApi in "MGW" assigned to ""
026ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
7s 001ms
When
Click button advice in transport table "CONTAINER"
208ms
And
Set advice window in schedule
3s 397ms
And
Fill advice form
20s 198ms
And
Click advice save button and wait for advice form to disappear
33s 264ms
And
Go to "TRANSPORT_TABLE"
465ms
And
Go to transport details "CONTAINER"
2s 931ms
Then
Check are advice values equals
4s 981ms
After
Hooks.cleanUserDetailsAfterTest()
2s 304ms
After
Hooks.deleteTransportAfterTest()
770ms
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.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
7s 443ms
And
Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz"
001ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 302ms
And
Add transport by SKApi in "MGW" assigned to ""
018ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
000ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 118ms
When
Click button advice in transport table "OWN_COLLECTION"
236ms
And
Set advice window in schedule
3s 403ms
And
Fill advice form
20s 435ms
And
Click advice save button and wait for advice form to disappear
33s 296ms
And
Go to "TRANSPORT_TABLE"
461ms
And
Go to transport details "OWN_COLLECTION"
2s 923ms
Then
Check are advice values equals
4s 982ms
After
Hooks.cleanUserDetailsAfterTest()
2s 095ms
After
Hooks.deleteTransportAfterTest()
785ms
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.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
7s 154ms
And
Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz"
001ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 394ms
And
Add transport by SKApi in "MGW" assigned to ""
022ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
7s 359ms
When
Click button advice in transport table "TRANSPORT_ORDER"
219ms
And
Set advice window in schedule
3s 375ms
And
Fill advice form
20s 403ms
And
Click advice save button and wait for advice form to disappear
33s 245ms
And
Go to "TRANSPORT_TABLE"
469ms
And
Go to transport details "TRANSPORT_ORDER"
2s 901ms
Then
Check are advice values equals
5s 003ms
After
Hooks.cleanUserDetailsAfterTest()
2s 274ms
After
Hooks.deleteTransportAfterTest()
799ms
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.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "pskza1-carrier" and set token of apiUsername "super-admin-skz"
8s 409ms
And
Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz"
001ms
And
Prepare user "pskza1-carrier" details with all notifications and "" by JSON file
3s 470ms
And
Add transport by SKApi in "MGW" assigned to ""
020ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
7s 039ms
When
Click button advice in transport table "TRANSPORT_ORDER"
217ms
And
Set advice window in schedule
3s 374ms
And
Fill advice form
20s 393ms
And
Click advice save button and wait for advice form to disappear
33s 785ms
And
Go to "TRANSPORT_TABLE"
524ms
And
Go to transport details "TRANSPORT_ORDER"
2s 852ms
Then
Check are advice values equals
4s 961ms
After
Hooks.cleanUserDetailsAfterTest()
2s 829ms
After
Hooks.deleteTransportAfterTest()
826ms
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.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-tradesman" and set token of apiUsername "super-admin-skz"
8s 713ms
And
Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz"
001ms
And
Prepare user "swisskrono-tradesman" details with all notifications and "automaty@test.pl" by JSON file
2s 544ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
024ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
4s 327ms
When
Click button advice in transport table "TRANSPORT_ORDER"
234ms
And
Set advice window in schedule
3s 410ms
And
Fill advice form
20s 512ms
And
Click advice save button and wait for advice form to disappear
33s 859ms
And
Go to "TRANSPORT_TABLE"
446ms
And
Go to transport details "TRANSPORT_ORDER"
2s 916ms
Then
Check are advice values equals
4s 973ms
After
Hooks.cleanUserDetailsAfterTest()
1s 777ms
After
Hooks.deleteTransportAfterTest()
832ms
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.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
7s 899ms
And
Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz"
001ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 362ms
And
Add transport by SKApi in "MGW" assigned to ""
021ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
000ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 176ms
When
Click button advice in transport table "OWN_COLLECTION"
217ms
And
Set advice window in schedule
3s 369ms
And
Fill advice form
20s 398ms
And
Click advice save button and wait for advice form to disappear
33s 336ms
And
Go to "TRANSPORT_TABLE"
410ms
Then
Check advice data in SK API database "OWN_COLLECTION"
417ms
After
Hooks.cleanUserDetailsAfterTest()
2s 063ms
After
Hooks.deleteTransportAfterTest()
779ms
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.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
7s 392ms
And
Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz"
000ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 436ms
And
Add transport by SKApi in "MGW" assigned to ""
027ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
4s 012ms
When
Click button advice in transport table "CONTAINER"
207ms
And
Set advice window in schedule
3s 404ms
And
Fill advice form
20s 375ms
And
Click advice save button and wait for advice form to disappear
33s 253ms
And
Go to "TRANSPORT_TABLE"
506ms
Then
Check advice data in SK API database "CONTAINER"
193ms
After
Hooks.cleanUserDetailsAfterTest()
2s 305ms
After
Hooks.deleteTransportAfterTest()
813ms
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.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
7s 453ms
And
Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz"
001ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 181ms
And
Add transport by SKApi in "MGW" assigned to ""
021ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
000ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
4s 487ms
When
Click button advice in transport table "TRANSPORT_ORDER"
243ms
And
Set advice window in schedule
3s 346ms
And
Fill advice form
20s 679ms
And
Click advice save button and wait for advice form to disappear
33s 240ms
And
Go to "TRANSPORT_TABLE"
512ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
092ms
After
Hooks.cleanUserDetailsAfterTest()
2s 254ms
After
Hooks.deleteTransportAfterTest()
804ms
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.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "pskza1-carrier" and set token of apiUsername "super-admin-skz"
6s 275ms
And
Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz"
001ms
And
Prepare user "pskza1-carrier" details with all notifications and "" by JSON file
3s 447ms
And
Add transport by SKApi in "MGW" assigned to ""
018ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
7s 752ms
When
Click button advice in transport table "TRANSPORT_ORDER"
211ms
And
Set advice window in schedule
3s 437ms
And
Fill advice form
20s 388ms
And
Click advice save button and wait for advice form to disappear
18s 327ms
And
Go to "TRANSPORT_TABLE"
478ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
094ms
After
Hooks.cleanUserDetailsAfterTest()
3s 060ms
After
Hooks.deleteTransportAfterTest()
946ms
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.
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Login as "swisskrono-tradesman" and set token of apiUsername "super-admin-skz"
7s 780ms
And
Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz"
001ms
And
Prepare user "swisskrono-tradesman" details with all notifications and "automaty@test.pl" by JSON file
1s 880ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
018ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
000ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
4s 471ms
When
Click button advice in transport table "TRANSPORT_ORDER"
218ms
And
Set advice window in schedule
3s 341ms
And
Fill advice form
20s 459ms
And
Click advice save button and wait for advice form to disappear
33s 792ms
And
Go to "TRANSPORT_TABLE"
446ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
272ms
After
Hooks.cleanUserDetailsAfterTest()
1s 672ms
After
Hooks.deleteTransportAfterTest()
807ms
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
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
7s 282ms
And
Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz"
000ms
And
Add transport by SKApi in "MGW" assigned to ""
019ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
000ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 948ms
When
Click button advice in transport table "CONTAINER"
238ms
And
Set advice window in schedule in the past
3s 406ms
And
Fill advice form
20s 437ms
And
Click advice save button to check error message
194ms
Then
Check if possible advice alert is displayed
065ms
After
Hooks.deleteTransportAfterTest()
539ms
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.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 768ms
And
Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz"
001ms
And
Add transport by SKApi in "MGW" assigned to ""
022ms
And
Set "advice" inputs from JSON file "EDIT_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
5s 040ms
And
Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-skz" with window starts at "07:00" and ends at "08:00"
3s 910ms
And
Go to "TRANSPORT_TABLE"
413ms
When
Go to transport details "OWN_COLLECTION"
3s 015ms
And
Expand advice panel
224ms
And
Edit advice in transport details
19s 255ms
And
Fill arrival date field
2s 594ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 239ms
Then
Check advice data in database after edition "OWN_COLLECTION"
103ms
After
Hooks.deleteTransportAfterTest()
857ms
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.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 721ms
And
Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz"
001ms
And
Add transport by SKApi in "MGW" assigned to ""
021ms
And
Set "advice" inputs from JSON file "EDIT_ADVICE" "super-admin-skz"
000ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 939ms
And
Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-skz" with window starts at "07:00" and ends at "08:00"
4s 531ms
And
Go to "TRANSPORT_TABLE"
378ms
When
Go to transport details "CONTAINER"
2s 894ms
And
Expand advice panel
344ms
And
Edit advice in transport details
19s 159ms
And
Fill arrival date field
2s 568ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 223ms
Then
Check advice data in database after edition "CONTAINER"
092ms
After
Hooks.deleteTransportAfterTest()
877ms
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.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 800ms
And
Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz"
000ms
And
Add transport by SKApi in "MGW" assigned to ""
022ms
And
Set "advice" inputs from JSON file "EDIT_ADVICE" "super-admin-skz"
000ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 693ms
And
Create advice by JSON file "CREATE_ADVICE_FOR_TRANSPORT_ORDER" as "super-admin-skz" with window starts at "07:00" and ends at "08:00"
4s 756ms
And
Go to "TRANSPORT_TABLE"
365ms
When
Go to transport details "TRANSPORT_ORDER"
2s 983ms
And
Expand advice panel
235ms
And
Edit advice in transport details
19s 109ms
And
Fill arrival date field
2s 617ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 191ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
089ms
After
Hooks.deleteTransportAfterTest()
806ms