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 521ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
028ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
017ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 896ms
When
Click button advice in transport table "CONTAINER"
230ms
And
Set advice window in schedule
3s 411ms
And
Fill advice form
17s 819ms
And
Click advice save button and wait for advice form to disappear
33s 158ms
And
Go to "TRANSPORT_TABLE"
411ms
And
Go to transport details "CONTAINER"
2s 935ms
Then
Check are advice values equals
2s 886ms
After
Hooks.deleteTransportAfterTest()
831ms
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 891ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
021ms
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 106ms
When
Click button advice in transport table "OWN_COLLECTION"
225ms
And
Set advice window in schedule
3s 357ms
And
Fill advice form
18s 014ms
And
Click advice save button and wait for advice form to disappear
33s 261ms
And
Go to "TRANSPORT_TABLE"
400ms
And
Go to transport details "OWN_COLLECTION"
2s 855ms
Then
Check are advice values equals
2s 909ms
After
Hooks.deleteTransportAfterTest()
905ms
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 634ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
027ms
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
6s 613ms
When
Click button advice in transport table "TRANSPORT_ORDER"
225ms
And
Set advice window in schedule
3s 359ms
And
Fill advice form
17s 924ms
And
Click advice save button and wait for advice form to disappear
33s 429ms
And
Go to "TRANSPORT_TABLE"
433ms
And
Go to transport details "TRANSPORT_ORDER"
2s 835ms
Then
Check are advice values equals
2s 890ms
After
Hooks.deleteTransportAfterTest()
913ms
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 970ms
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"
015ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
4s 952ms
When
Click button advice in transport table "TRANSPORT_ORDER"
225ms
And
Set advice window in schedule
3s 235ms
And
Fill advice form
17s 918ms
And
Click advice save button and wait for advice form to disappear
33s 241ms
And
Go to "TRANSPORT_TABLE"
454ms
And
Go to transport details "TRANSPORT_ORDER"
2s 865ms
Then
Check are advice values equals
2s 912ms
After
Hooks.deleteTransportAfterTest()
964ms
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"
2s 860ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id
4s 159ms
When
Click button advice in transport table "OWN_COLLECTION"
240ms
And
Set advice window in schedule
3s 362ms
And
Fill advice form
17s 994ms
And
Click advice save button and wait for advice form to disappear
33s 276ms
And
Go to "TRANSPORT_TABLE"
398ms
Then
Check advice data in SK API database "OWN_COLLECTION"
457ms
After
Hooks.deleteTransportAfterTest()
945ms
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 660ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW"
025ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
017ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 944ms
When
Click button advice in transport table "CONTAINER"
218ms
And
Set advice window in schedule
3s 326ms
And
Fill advice form
18s 065ms
And
Click advice save button and wait for advice form to disappear
33s 339ms
And
Go to "TRANSPORT_TABLE"
423ms
Then
Check advice data in SK API database "CONTAINER"
203ms
After
Hooks.deleteTransportAfterTest()
903ms
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 750ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
023ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
017ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
4s 415ms
When
Click button advice in transport table "TRANSPORT_ORDER"
226ms
And
Set advice window in schedule
3s 302ms
And
Fill advice form
17s 917ms
And
Click advice save button and wait for advice form to disappear
33s 310ms
And
Go to "TRANSPORT_TABLE"
429ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
093ms
After
Hooks.deleteTransportAfterTest()
859ms
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"
2s 643ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
051ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
019ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 920ms
When
Click button advice in transport table "CONTAINER"
234ms
And
Set advice window in schedule in the past
3s 338ms
And
Fill advice form
17s 887ms
And
Click advice save button to check error message
197ms
Then
Check if possible advice alert is displayed
070ms
After
Hooks.deleteTransportAfterTest()
657ms
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 739ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW"
017ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
018ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
4s 094ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
54s 878ms
And
Go to "TRANSPORT_TABLE"
409ms
When
Go to transport details "OWN_COLLECTION"
2s 830ms
And
Expand advice panel
318ms
And
Edit advice in transport details
16s 511ms
And
Fill arrival date field
2s 614ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 184ms
Then
Check advice data in database after edition "OWN_COLLECTION"
110ms
After
Hooks.deleteTransportAfterTest()
892ms
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 564ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
018ms
And
Add transport by SKApi in "MGW"
022ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
016ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 923ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
54s 606ms
And
Go to "TRANSPORT_TABLE"
399ms
When
Go to transport details "CONTAINER"
2s 901ms
And
Expand advice panel
291ms
And
Edit advice in transport details
16s 586ms
And
Fill arrival date field
2s 620ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 254ms
Then
Check advice data in database after edition "CONTAINER"
109ms
After
Hooks.deleteTransportAfterTest()
900ms
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 701ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW"
019ms
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
3s 640ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
54s 967ms
And
Go to "TRANSPORT_TABLE"
446ms
When
Go to transport details "TRANSPORT_ORDER"
2s 872ms
And
Expand advice panel
291ms
And
Edit advice in transport details
16s 554ms
And
Fill arrival date field
2s 614ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 201ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
113ms
After
Hooks.deleteTransportAfterTest()
913ms