As far as I know there are only locigal conditions and wildcards.
Maybe if you have a description like This is my test-ticket you can search for it with something like *test*. This works like if you use the SQL-Statement LIKE with a front and a back %. So test* would not find the example as it does not start with test. Same with *test as there are ...
Yes, you can do that. For this you need to save your common/shared test steps in a new test case and then change it to a template using 'Mark as Template Test'. Then where ever you need these shared steps, open that test case and in the test step section of that case select the option 'Call to Test' and then select the shared test case template which you ...
Since you tagged this question with Quality-Center I am going to assume that you mean a Call to Test as in the example test case below which has several steps that are calls to other Tests.
There is no straight forward way to do this. However, you have either access to the database or a version of Quality Center which has the Dashboard you can query the ...
In addition to the answer from bish: You can also filter like this:
*text1*text2* - so you do not need to put the filter into double quotes.
Usually I filter on different fields like:
Assigned to - me
Status - "not closed and not tested and not rejected" (without quotes)
After you have configured a filter you can save it as a favorite....
It depends on the testing tool you use, if it creates a copy when you add the same test case to the suite or just link it. For example, in Microsoft's Test Manager you cannot verify in which testing suite was the test case created/used, only if the suite is a User Story/Product Backlog Item.
I would suggest you to test first your testing suite with a simple ...
So you need real-world examples of LOC metrics in a software sources and a test suite LOC volume, right? I can share some rough metrics for one real-world project. Never heard about representative figures. It highly depends on technologies and tools you're using.
The applications are written in C++ (Windows only though). Metrics were done with simple Python ...
Base from our project experience I cann tell you the following:
Our test cases are defined in HP ALM and automatic test cases also in HP UFT. After a couple of years we decided to move away from HP ALM and trying to find a solution for transferring the automatic test cases into another test automation tool. In this case we used Saucelabs and Selenium. In ...
For a functional requirement the Direct Cover Status depend on the test coverage for the same requirement.
In your example you have a functional requirement Req1 without test coverage and two requirement Scenario1 and Scenario2 with test coverage. The test coverage of Scenario1 and Scenario2 are not added to Req1 because they are not direct coverage tests.
Status of the requirement is automatically changed to Passed when all test cases from test set are passed, all test cases that cover the requirement are in this test set.
It's easy to do: when you add tests to the test set, select Requirements tree tab >> select the requirement >> press Add all tests that cover this requirement.
And do not forget that ...
You need to use SQL to join the BUG table with the audit log table and audit properties table. You can create an Excel under Analysis to execute the SQL as follows:
BUG.BG_PRIORITY as 'Prio',
BUG.BG_SEVERITY as 'Sev',
BUG.BG_BUG_ID as 'Defect ID',
BUG.BG_DETECTION_DATE as 'Detected',
BUG.BG_STATUS as 'Status',
Based on your question, the answer is to inform your superiors that their choices are for you or someone else to spend some huge amount of time manually entering the results (assuming you have been able to import test cases), or they can have someone with the proper programming knowledge uses the HP API to generate the import(which also could be a huge ...
What you want for this, assuming you have intelligent testers who aren't expected to follow a "click this button" script, is to define one test case for customer lookup, and in that test case, list the ways to search for a customer.
Depending on how your system works, you should be able to define the search methods as test parameters that can be used in ...
Since throughly testing would be unfeasible, have two options:
Do a risk analysis and perform only a subset of the possible tests, trying to cover all ways in a limited number of ways.
Do random testing. You would have to model the creation flow, so you could generate a random state and check if the output matches the model.
In both cases, you should sync ...
I suggest you use test parameters and create separate test configurations for each browser. So you'd do something like this:
Add a parameter for "Browser" in your test
Insert the parameter in a step such as "Load Firefox", where you are substituting the variable for "Firefox"
Add the tests into your test set and set the browser variable accordingly
You can ...
You can find the ALM REST API reference guide here:
These both require logins so I can't provide any other information that the links really.
It is possible:
Go to Test Lab and select a test set which you want to move.
Click on Select Tests button present on top of grid view of test cases.
After clicking it, a pane at the right side of the window will get opened.
Collapse the hierarchy and go to the folder from which you want to get the test set.
Select that test set and Click on (<-) left ...
It is not possible to copy test cases from test lab to test plan. Actually test lab doesn't have any test cases, it only has a reference to test plan's test cases. So only way to copy test cases is from test plan to test plan.
There is no directy way to filter tickets over history events as you can - as you already noticed - only filter about current attribute values. But you can search in the history of any objects by using the Dashboard. Here is an example how you can create a filter for your needs:
Go to Dashboard and there to Analysis View: Press the green cross and choose ...
I have no experience with the specific system, but it sounds to me like a culture or administrative problem.
Are the different phases part of the same department?
Who coordinates the test strategy?
Is there an overall test budget?
You can do that in a clean and bullet-proof way only if you enable (and license) the version control support in QC/ALM. Then, your user could check out the test, guaranteeing that nobody else can modify it.
For the cross-project work you outlined, QC also has features in the release manager module, but for those to work really good you also need to enable (...
From what I read in the documentation the Synchronizer does not support syncing of test cases, but only defect data between projects.
From the HP ALM Synchronizer user guide:
Welcome to HP ALM Synchronizer. Synchronizer enables you to
synchronize HP Application Lifecycle Management (ALM) data with data
in another application. You can: ➤ Synchronize ...
There is no staight-forward answer to your question but, here are a few guidelines that may help you choose the best approcah for your organisation.
Is having a consolidated test cases suite the most efficient method of managing test cases in the context of your organisation and projects undertaken? The reason it's important that you know the answer to this ...
There's a certain amount of flexibility in how you use these, although I'm sure the HPALM documentation has its own definitions for each of these items.
Ultimately, apart from Implementation and Post-Implementation (which are pretty obviously "while it's being developed" and "after it's done"), these categories are pretty vague and can mean whatever you ...