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 680ms
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 535ms
And
Add transport by SKApi in "MGW" assigned to ""
022ms
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
3s 907ms
When
Click button advice in transport table "CONTAINER"
221ms
And
Set advice window in schedule
3s 387ms
And
Fill advice form
20s 357ms
And
Click advice save button and wait for advice form to disappear
33s 320ms
And
Go to "TRANSPORT_TABLE"
392ms
And
Go to transport details "CONTAINER"
2s 910ms
Then
Check are advice values equals
4s 956ms
After
Hooks.cleanUserDetailsAfterTest()
2s 307ms
After
Hooks.deleteTransportAfterTest()
777ms
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 421ms
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 408ms
And
Add transport by SKApi in "MGW" assigned to ""
021ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 166ms
When
Click button advice in transport table "OWN_COLLECTION"
208ms
And
Set advice window in schedule
3s 376ms
And
Fill advice form
20s 523ms
And
Click advice save button and wait for advice form to disappear
33s 266ms
And
Go to "TRANSPORT_TABLE"
396ms
And
Go to transport details "OWN_COLLECTION"
2s 948ms
Then
Check are advice values equals
4s 944ms
After
Hooks.cleanUserDetailsAfterTest()
2s 109ms
After
Hooks.deleteTransportAfterTest()
779ms
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 208ms
And
Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz"
000ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 329ms
And
Add transport by SKApi in "MGW" assigned to ""
023ms
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 429ms
When
Click button advice in transport table "TRANSPORT_ORDER"
222ms
And
Set advice window in schedule
3s 339ms
And
Fill advice form
20s 363ms
And
Click advice save button and wait for advice form to disappear
33s 339ms
And
Go to "TRANSPORT_TABLE"
475ms
And
Go to transport details "TRANSPORT_ORDER"
2s 919ms
Then
Check are advice values equals
4s 937ms
After
Hooks.cleanUserDetailsAfterTest()
2s 275ms
After
Hooks.deleteTransportAfterTest()
814ms
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 551ms
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 490ms
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
3s 872ms
When
Click button advice in transport table "TRANSPORT_ORDER"
225ms
And
Set advice window in schedule
3s 360ms
And
Fill advice form
20s 478ms
And
Click advice save button and wait for advice form to disappear
33s 293ms
And
Go to "TRANSPORT_TABLE"
494ms
And
Go to transport details "TRANSPORT_ORDER"
2s 840ms
Then
Check are advice values equals
5s 036ms
After
Hooks.cleanUserDetailsAfterTest()
2s 714ms
After
Hooks.deleteTransportAfterTest()
848ms
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 889ms
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 467ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
023ms
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 324ms
When
Click button advice in transport table "TRANSPORT_ORDER"
246ms
And
Set advice window in schedule
3s 521ms
And
Fill advice form
20s 105ms
And
Click advice save button and wait for advice form to disappear
33s 954ms
And
Go to "TRANSPORT_TABLE"
485ms
And
Go to transport details "TRANSPORT_ORDER"
2s 909ms
Then
Check are advice values equals
5s 042ms
After
Hooks.cleanUserDetailsAfterTest()
1s 744ms
After
Hooks.deleteTransportAfterTest()
788ms
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 526ms
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 369ms
And
Add transport by SKApi in "MGW" assigned to ""
025ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 173ms
When
Click button advice in transport table "OWN_COLLECTION"
222ms
And
Set advice window in schedule
3s 393ms
And
Fill advice form
20s 448ms
And
Click advice save button and wait for advice form to disappear
33s 309ms
And
Go to "TRANSPORT_TABLE"
480ms
Then
Check advice data in SK API database "OWN_COLLECTION"
423ms
After
Hooks.cleanUserDetailsAfterTest()
2s 080ms
After
Hooks.deleteTransportAfterTest()
780ms
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 452ms
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 333ms
And
Add transport by SKApi in "MGW" assigned to ""
019ms
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 928ms
When
Click button advice in transport table "CONTAINER"
233ms
And
Set advice window in schedule
3s 363ms
And
Fill advice form
20s 425ms
And
Click advice save button and wait for advice form to disappear
33s 824ms
And
Go to "TRANSPORT_TABLE"
450ms
Then
Check advice data in SK API database "CONTAINER"
232ms
After
Hooks.cleanUserDetailsAfterTest()
2s 311ms
After
Hooks.deleteTransportAfterTest()
881ms
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 440ms
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 489ms
And
Add transport by SKApi in "MGW" assigned to ""
024ms
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
7s 217ms
When
Click button advice in transport table "TRANSPORT_ORDER"
265ms
And
Set advice window in schedule
3s 372ms
And
Fill advice form
20s 481ms
And
Click advice save button and wait for advice form to disappear
33s 319ms
And
Go to "TRANSPORT_TABLE"
536ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
092ms
After
Hooks.cleanUserDetailsAfterTest()
2s 140ms
After
Hooks.deleteTransportAfterTest()
794ms
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 252ms
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 573ms
And
Add transport by SKApi in "MGW" assigned to ""
023ms
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 829ms
When
Click button advice in transport table "TRANSPORT_ORDER"
229ms
And
Set advice window in schedule
3s 326ms
And
Fill advice form
20s 556ms
And
Click advice save button and wait for advice form to disappear
33s 832ms
And
Go to "TRANSPORT_TABLE"
471ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
099ms
After
Hooks.cleanUserDetailsAfterTest()
2s 959ms
After
Hooks.deleteTransportAfterTest()
855ms
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-tradesman" and set token of apiUsername "super-admin-skz"
7s 782ms
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"
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 548ms
When
Click button advice in transport table "TRANSPORT_ORDER"
228ms
And
Set advice window in schedule
3s 381ms
And
Fill advice form
20s 667ms
And
Click advice save button and wait for advice form to disappear
33s 846ms
And
Go to "TRANSPORT_TABLE"
411ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
264ms
After
Hooks.cleanUserDetailsAfterTest()
1s 682ms
After
Hooks.deleteTransportAfterTest()
792ms
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 417ms
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"
000ms
And
Check is transport "CONTAINER" created in transport table and set transport id
7s 031ms
When
Click button advice in transport table "CONTAINER"
255ms
And
Set advice window in schedule in the past
3s 357ms
And
Fill advice form
20s 436ms
And
Click advice save button to check error message
187ms
Then
Check if possible advice alert is displayed
073ms
After
Hooks.deleteTransportAfterTest()
529ms
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)
000ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 843ms
And
Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
7s 143ms
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"
4s 051ms
And
Go to "TRANSPORT_TABLE"
363ms
When
Go to transport details "OWN_COLLECTION"
2s 935ms
And
Expand advice panel
269ms
And
Edit advice in transport details
19s 327ms
And
Fill arrival date field
2s 618ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 256ms
Then
Check advice data in database after edition "OWN_COLLECTION"
097ms
After
Hooks.deleteTransportAfterTest()
804ms
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 849ms
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
3s 945ms
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 662ms
And
Go to "TRANSPORT_TABLE"
424ms
When
Go to transport details "CONTAINER"
2s 910ms
And
Expand advice panel
381ms
And
Edit advice in transport details
19s 184ms
And
Fill arrival date field
2s 649ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 208ms
Then
Check advice data in database after edition "CONTAINER"
084ms
After
Hooks.deleteTransportAfterTest()
875ms
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)
000ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 760ms
And
Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "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"
000ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 749ms
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 753ms
And
Go to "TRANSPORT_TABLE"
376ms
When
Go to transport details "TRANSPORT_ORDER"
2s 950ms
And
Expand advice panel
269ms
And
Edit advice in transport details
19s 146ms
And
Fill arrival date field
2s 645ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 269ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
099ms
After
Hooks.deleteTransportAfterTest()
840ms