In ALM 12.21:
How can I update the parameters in a test case (type businesss process) after I added new parameters to a business component that is part of the test script?
I have found now way to update the test case for the new parameters in the business component.
So far, the only way to get the new parameters into the test is to delete the business component from test script an add it again.
Which is cumbersome as I am creating lots of Test Cases using this workflow:
Create Test
Create Business Component request when new BC for Test is needed
Writing Business Component steps, including parameters when needed
Writing Test Configuration to fill the needed parameters in 1 to n iterations
Right now, between steps 3 and 4, I have to delete an re-add the BC from Test Script so that the new parameters show.
Any help appreciated!
Related
I'm working on a PoC with the Configurable Bundle Module on v1811, I configured a very basic BundleTemplate with one package and two components, each one with one product, one has a PickExactlyNBundleSelectionCriteria with N=1 associated and the other one with an AutoPickBundleSelectionCriteria.
I expect that once I start the bundle (selecting the pick 1 product marked as a starter) the second component marked with the auto-pick was going to be added automatically to the cart and bundle. But this is not happening.
In order to have available the AutoPickBundleSelectionCriteria ItemType, I had to add the subscriptionbundleservices extension to the localextensions.xml.
Am I missing some point?
I am running multiple test case in robot framework.
I wish to pass the result of one test case to another test case. Is there any way to do the same.
Example
TC01-Search and Navigate to Required Vessel
Given Home Page is Loaded
When Search Ship and Choose Required Vessel
${name} ${no} Navigate to the Vessel View
TC02-Verify Vessel Details in Case
Given Cases is Available in Apps
And I Navigate to Cases
Then Verify Vessel Details are present or not ${name} ${no}
Here I have to pass ${name} and ${no} from TC-01 to TC-02.
Is there anyway to do this?
You can use the below keyword
Set Suite Variable name, *values
Makes a variable available everywhere within the scope of the current suite.
The above keyword can be used to reuse the test data in different test cases
i need help on HP ALM Parameterization concept. what is use of Parameterization concept in HP ALM. how can we implement this concept ? give me any examples
In terms of manual test cases, parametrization comes very handy when you have scenarios that have pretty much same steps or at least same structure.
When you create a new test case, you will have a button to parameters on the header menu, you can list all the parameters you think you would need. For a simple login test on multiple pages ( home page, account page ) with similar layout, you will have username, password and url as parameters. It also allows you to give default value. You can add more parameter as you write steps in the step description window.
once you have the complete test case created, go to test configuration tab of the test case and add test configuration by clicking plus button. There will be one by default. You can create as many test configuration as you want. For above example you can add three; one for home page, one for account page and one for search page. The test configuration will help you have the test instances ready while pulling the test cases into test lab without having to drag the same test cases multiple times.
The test configuration allows you to define the actual/default value for each of configuration added reducing the time it takes to fill this info during execution.
Test execution - after you pull the test cases into lab, during the manual run a pop up comes to show the values for each of parameter being used for that test case. Te values can be added or updated.
Please find a video I found on YouTube.
https://youtu.be/vCrJcHrosio
I don't have ALM to show with diagrams. Hope this helps.
Create a test testcase to test this feature.
Thanks
Happy exploring !!
Parameters help the user to assign a value to a variable so as to execute the same test with different sets of data.
For example, the user name and password can be two parameters, for a login related test, which would be assigned with a value.
How to use parameters:
Create test case with steps in Test Plan module under selected Cycle and proper folder.
Select the test step against which you would like to add the parameter. The 'Parameter' Icon will be enabled. Click on the same. The 'Parameter' dialog box will open. Now, click on 'New Parameter' button. Add the parameter (here: username or password). Add the default and/or actual values, description for the same and save.
You can also add different test configurations to use these parameters for different use case scenarios.
More details can be found here: http://alm-help.saas.hpe.com/en/12.53/online_help/Content/UG/ui_menu_test_parameters.htm
I'm currently busy with an test automation project for mobile devices and I want to store my results in a database.
I do this with a custom assertclass which I created, this one stores the result.
The layout is as following -> There are runs which contain Tests which contain Steps.
When I want to run in parallel, I create a unique id for the run based on thread and date and store this one in a static list. This is #BeforeTest.
At the #BeforeClass, I search in the list for the right thread and assign the correct name to the variable of the class.
But I receive constantly a Nullpointerexception for the list in the beforeclass or the variable is null while it was filled in in the #beforetest.
What are we missing here? Or how is this done when you need to store a parameter that is generated once for the whole run?
Thanks in advance,
Jonas Vandevelde
Is it possible to send a list of parameters to a test case / step in soapUI? I want to perform some database validation, and I would like to be able to pass a list of the expected values to the test case and / or step that performs the validation.
I know it's possible to send single parameters ("properties") to a test case, but I don't think that's good enough for this use case. My idea is to write a single "test case" that performs the validation that can be called from other test cases, and they pass in the values they expect to find in the database.
If you can generate the list of Random parameters through Groovy script then the best solution is: Through groovy script set the property field's value and pass this value into request using property transfer. The property field value will change at each and every run of the groovy script.
Now run the request in loop in groovy script.
So we can able to run the one test request multiple times with different parameter values.
We have a similar issue. We need to run multiple XML-files as source files for the sequence of requests. We got about 15 steps in the test, and the only thing that changes is the initial XML.
We solved this by using groovy to set a propperty to a comma seperated list, then pick the first element, remove it from the list, and run the tests. In the end, we return to the "pick first element from list"-step if the propperty is not empty.
This is a goto implementation of a basic loop, and we would prefer to do this differently, but we have not figured out how to (we run soapUI via maven2).
If you are using soapUI Pro, you can create a data source step > request step > dataSource loop step.
dataSource step can take excel, XML, grid as the soure. You need to create a property and select the type of the source.
The next step is running the request.
Then you should create a dataSource loop step. This steps returns to the dataSource until running all the request.
Please check soapui documentation
if you are not using soap Pro version, creating a groovy script is the solution as described with the previous answer.