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 731ms
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 425ms
And
Add transport by SKApi in "MGW" assigned to ""
023ms
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 909ms
When
Click button advice in transport table "CONTAINER"
254ms
And
Set advice window in schedule
3s 386ms
And
Fill advice form
20s 293ms
And
Click advice save button and wait for advice form to disappear
33s 317ms
And
Go to "TRANSPORT_TABLE"
427ms
And
Go to transport details "CONTAINER"
2s 882ms
Then
Check are advice values equals
5s 004ms
After
Hooks.cleanUserDetailsAfterTest()
2s 340ms
After
Hooks.deleteTransportAfterTest()
729ms
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 723ms
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 398ms
And
Add transport by SKApi in "MGW" assigned to ""
020ms
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
4s 069ms
When
Click button advice in transport table "OWN_COLLECTION"
232ms
And
Set advice window in schedule
3s 333ms
And
Fill advice form
20s 505ms
And
Click advice save button and wait for advice form to disappear
33s 222ms
And
Go to "TRANSPORT_TABLE"
440ms
And
Go to transport details "OWN_COLLECTION"
2s 883ms
Then
Check are advice values equals
4s 941ms
After
Hooks.cleanUserDetailsAfterTest()
2s 119ms
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 441ms
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 ""
026ms
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 311ms
When
Click button advice in transport table "TRANSPORT_ORDER"
217ms
And
Set advice window in schedule
3s 330ms
And
Fill advice form
20s 065ms
And
Click advice save button and wait for advice form to disappear
33s 253ms
And
Go to "TRANSPORT_TABLE"
516ms
And
Go to transport details "TRANSPORT_ORDER"
2s 912ms
Then
Check are advice values equals
5s 056ms
After
Hooks.cleanUserDetailsAfterTest()
2s 311ms
After
Hooks.deleteTransportAfterTest()
787ms
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 397ms
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 561ms
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 "TRANSPORT_ORDER" created in transport table and set transport id
3s 999ms
When
Click button advice in transport table "TRANSPORT_ORDER"
255ms
And
Set advice window in schedule
3s 342ms
And
Fill advice form
20s 422ms
And
Click advice save button and wait for advice form to disappear
33s 287ms
And
Go to "TRANSPORT_TABLE"
503ms
And
Go to transport details "TRANSPORT_ORDER"
2s 854ms
Then
Check are advice values equals
4s 977ms
After
Hooks.cleanUserDetailsAfterTest()
2s 759ms
After
Hooks.deleteTransportAfterTest()
759ms
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)
000ms
Given
Login as "swisskrono-tradesman" and set token of apiUsername "super-admin-skz"
9s 008ms
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 530ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
028ms
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 226ms
When
Click button advice in transport table "TRANSPORT_ORDER"
258ms
And
Set advice window in schedule
3s 494ms
And
Fill advice form
20s 372ms
And
Click advice save button and wait for advice form to disappear
33s 856ms
And
Go to "TRANSPORT_TABLE"
440ms
And
Go to transport details "TRANSPORT_ORDER"
2s 853ms
Then
Check are advice values equals
4s 953ms
After
Hooks.cleanUserDetailsAfterTest()
1s 744ms
After
Hooks.deleteTransportAfterTest()
746ms
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-admin" and set token of apiUsername "super-admin-skz"
7s 610ms
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 479ms
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 "OWN_COLLECTION" created in transport table and set transport id
7s 132ms
When
Click button advice in transport table "OWN_COLLECTION"
203ms
And
Set advice window in schedule
3s 313ms
And
Fill advice form
20s 561ms
And
Click advice save button and wait for advice form to disappear
17s 796ms
And
Go to "TRANSPORT_TABLE"
455ms
Then
Check advice data in SK API database "OWN_COLLECTION"
470ms
After
Hooks.cleanUserDetailsAfterTest()
2s 079ms
After
Hooks.deleteTransportAfterTest()
817ms
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 320ms
And
Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz"
001ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 469ms
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 "CONTAINER" created in transport table and set transport id
3s 976ms
When
Click button advice in transport table "CONTAINER"
204ms
And
Set advice window in schedule
3s 357ms
And
Fill advice form
20s 349ms
And
Click advice save button and wait for advice form to disappear
33s 265ms
And
Go to "TRANSPORT_TABLE"
466ms
Then
Check advice data in SK API database "CONTAINER"
240ms
After
Hooks.cleanUserDetailsAfterTest()
2s 323ms
After
Hooks.deleteTransportAfterTest()
757ms
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 578ms
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 398ms
And
Add transport by SKApi in "MGW" assigned to ""
020ms
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 320ms
When
Click button advice in transport table "TRANSPORT_ORDER"
207ms
And
Set advice window in schedule
3s 474ms
And
Fill advice form
20s 326ms
And
Click advice save button and wait for advice form to disappear
33s 231ms
And
Go to "TRANSPORT_TABLE"
521ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
095ms
After
Hooks.cleanUserDetailsAfterTest()
2s 114ms
After
Hooks.deleteTransportAfterTest()
777ms
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 301ms
And
Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz"
000ms
And
Prepare user "pskza1-carrier" details with all notifications and "" by JSON file
3s 479ms
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
3s 831ms
When
Click button advice in transport table "TRANSPORT_ORDER"
195ms
And
Set advice window in schedule
3s 374ms
And
Fill advice form
20s 260ms
And
Click advice save button and wait for advice form to disappear
33s 163ms
And
Go to "TRANSPORT_TABLE"
489ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
092ms
After
Hooks.cleanUserDetailsAfterTest()
2s 928ms
After
Hooks.deleteTransportAfterTest()
895ms
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 756ms
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 971ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
021ms
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 526ms
When
Click button advice in transport table "TRANSPORT_ORDER"
233ms
And
Set advice window in schedule
3s 360ms
And
Fill advice form
20s 364ms
And
Click advice save button and wait for advice form to disappear
33s 373ms
And
Go to "TRANSPORT_TABLE"
377ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
252ms
After
Hooks.cleanUserDetailsAfterTest()
1s 743ms
After
Hooks.deleteTransportAfterTest()
794ms
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)
000ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
7s 343ms
And
Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz"
001ms
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 "CONTAINER" created in transport table and set transport id
6s 964ms
When
Click button advice in transport table "CONTAINER"
236ms
And
Set advice window in schedule in the past
3s 360ms
And
Fill advice form
20s 413ms
And
Click advice save button to check error message
188ms
Then
Check if possible advice alert is displayed
070ms
After
Hooks.deleteTransportAfterTest()
569ms
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 714ms
And
Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz"
001ms
And
Add transport by SKApi in "MGW" assigned to ""
025ms
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
7s 812ms
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 819ms
And
Go to "TRANSPORT_TABLE"
355ms
When
Go to transport details "OWN_COLLECTION"
2s 904ms
And
Expand advice panel
266ms
And
Edit advice in transport details
19s 158ms
And
Fill arrival date field
2s 639ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 216ms
Then
Check advice data in database after edition "OWN_COLLECTION"
094ms
After
Hooks.deleteTransportAfterTest()
779ms
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 776ms
And
Set "transport" inputs from JSON file "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id
6s 977ms
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 264ms
And
Go to "TRANSPORT_TABLE"
365ms
When
Go to transport details "CONTAINER"
2s 897ms
And
Expand advice panel
314ms
And
Edit advice in transport details
19s 140ms
And
Fill arrival date field
2s 621ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 153ms
Then
Check advice data in database after edition "CONTAINER"
101ms
After
Hooks.deleteTransportAfterTest()
826ms
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 916ms
And
Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz"
001ms
And
Add transport by SKApi in "MGW" assigned to ""
023ms
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 653ms
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 413ms
And
Go to "TRANSPORT_TABLE"
354ms
When
Go to transport details "TRANSPORT_ORDER"
2s 968ms
And
Expand advice panel
309ms
And
Edit advice in transport details
19s 263ms
And
Fill arrival date field
2s 630ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 254ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
110ms
After
Hooks.deleteTransportAfterTest()
798ms