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-admin" and set token of apiUsername "super-admin-skz"
2s 717ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
015ms
And
Check is transport "CONTAINER" created in transport table and set transport id
12s 983ms
When
Click button advice in transport table "CONTAINER"
197ms
And
Set advice window in schedule
3s 327ms
And
Fill advice form
17s 706ms
And
Click advice save button and wait for advice form to disappear
33s 313ms
And
Go to "TRANSPORT_TABLE"
421ms
And
Go to transport details "CONTAINER"
2s 924ms
Then
Check are advice values equals
2s 916ms
After
Hooks.deleteTransportAfterTest()
899ms
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-admin" and set token of apiUsername "super-admin-skz"
2s 836ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
019ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
16s 171ms
When
Click button advice in transport table "OWN_COLLECTION"
214ms
And
Set advice window in schedule
3s 421ms
And
Fill advice form
17s 612ms
And
Click advice save button and wait for advice form to disappear
33s 208ms
And
Go to "TRANSPORT_TABLE"
420ms
And
Go to transport details "OWN_COLLECTION"
2s 867ms
Then
Check are advice values equals
2s 911ms
After
Hooks.deleteTransportAfterTest()
927ms
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 717ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 694ms
When
Click button advice in transport table "TRANSPORT_ORDER"
221ms
And
Set advice window in schedule
3s 364ms
And
Fill advice form
17s 713ms
And
Click advice save button and wait for advice form to disappear
18s 380ms
And
Go to "TRANSPORT_TABLE"
484ms
And
Go to transport details "TRANSPORT_ORDER"
2s 894ms
Then
Check are advice values equals
2s 865ms
After
Hooks.deleteTransportAfterTest()
922ms
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-2@qa.qa-test" and set token of apiUsername "super-admin-skz"
7s 751ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
015ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
7s 961ms
When
Click button advice in transport table "TRANSPORT_ORDER"
217ms
And
Set advice window in schedule
3s 264ms
And
Fill advice form
17s 666ms
And
Click advice save button and wait for advice form to disappear
33s 322ms
And
Go to "TRANSPORT_TABLE"
452ms
And
Go to transport details "TRANSPORT_ORDER"
2s 824ms
Then
Check are advice values equals
2s 865ms
After
Hooks.deleteTransportAfterTest()
965ms
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"
2s 768ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
4s 087ms
When
Click button advice in transport table "OWN_COLLECTION"
234ms
And
Set advice window in schedule
3s 318ms
And
Fill advice form
17s 663ms
And
Click advice save button and wait for advice form to disappear
33s 248ms
And
Go to "TRANSPORT_TABLE"
414ms
Then
Check advice data in SK API database "OWN_COLLECTION"
407ms
After
Hooks.deleteTransportAfterTest()
831ms
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"
2s 553ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
018ms
And
Check is transport "CONTAINER" created in transport table and set transport id
9s 913ms
When
Click button advice in transport table "CONTAINER"
212ms
And
Set advice window in schedule
3s 395ms
And
Fill advice form
17s 660ms
And
Click advice save button and wait for advice form to disappear
33s 217ms
And
Go to "TRANSPORT_TABLE"
401ms
Then
Check advice data in SK API database "CONTAINER"
230ms
After
Hooks.deleteTransportAfterTest()
873ms
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"
2s 671ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
015ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 604ms
When
Click button advice in transport table "TRANSPORT_ORDER"
234ms
And
Set advice window in schedule
3s 346ms
And
Fill advice form
17s 773ms
And
Click advice save button and wait for advice form to disappear
33s 276ms
And
Go to "TRANSPORT_TABLE"
448ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
095ms
After
Hooks.deleteTransportAfterTest()
936ms
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"
2s 656ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
018ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 943ms
When
Click button advice in transport table "CONTAINER"
238ms
And
Set advice window in schedule in the past
3s 263ms
And
Fill advice form
17s 800ms
And
Click advice save button to check error message
184ms
Then
Check if possible advice alert is displayed
073ms
After
Hooks.deleteTransportAfterTest()
616ms
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 675ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
019ms
And
Add transport by SKApi in "MGW"
018ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
017ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
4s 097ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
54s 442ms
And
Go to "TRANSPORT_TABLE"
403ms
When
Go to transport details "OWN_COLLECTION"
2s 842ms
And
Expand advice panel
300ms
And
Edit advice in transport details
16s 283ms
And
Fill arrival date field
2s 589ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 251ms
Then
Check advice data in database after edition "OWN_COLLECTION"
085ms
After
Hooks.deleteTransportAfterTest()
840ms
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 693ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
017ms
And
Add transport by SKApi in "MGW"
020ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
015ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 926ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
54s 599ms
And
Go to "TRANSPORT_TABLE"
410ms
When
Go to transport details "CONTAINER"
2s 884ms
And
Expand advice panel
304ms
And
Edit advice in transport details
16s 288ms
And
Fill arrival date field
2s 598ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 193ms
Then
Check advice data in database after edition "CONTAINER"
096ms
After
Hooks.deleteTransportAfterTest()
889ms
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 784ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
017ms
And
Add transport by SKApi in "MGW"
018ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
017ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
6s 640ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
54s 495ms
And
Go to "TRANSPORT_TABLE"
446ms
When
Go to transport details "TRANSPORT_ORDER"
2s 909ms
And
Expand advice panel
218ms
And
Edit advice in transport details
16s 325ms
And
Fill arrival date field
2s 575ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 233ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
091ms
After
Hooks.deleteTransportAfterTest()
960ms