Micro Focus ALM Quality Center Primary Use Case

We use all the major modules in ALM Quality Center. From the releases and management portion, we use the requirements, and we create our releases. We create requirements. We link our test spaces to these requirements and we schedule the execution in the test lab. Then we capture our results in Quality Center and we follow the management process that is not only for manual testing. We also have quite extensive automated testing in our environment with some of the other Micro Focus products. They are all integrated into Quality Center, like the UFT, we use service virtualization, we have RPA and we also use Mobile Center. Quality Center plays a major role in our test artifacts, our execution, and our order tracking, both in manual and automated. View full review »

We use it for defect management and for test cases. We synchronize it with JIRA for the requirements and the defects side of things. We're also using it for our UFT script repositories, but that is more than likely going to change, in the next couple of months, as we go across to GitLab. It's just simpler to have all the artifacts for a particular iteration in one place. Quality Center is cloud-based with a local client. View full review »

We use it for recording our requirements. We use it for recording our test cases and the data is done within the ALM itself. And, during execution, we use it to update services and to log defects. View full review »

We are using it for test management. We have distributed teams in three locations with one location in Portland, which is the newest, and also in India. We have a team of around 150 people (developers plus three testers). We are implementing an order migration legacy system to a new system based on AngularJS 5.0. We also have test automation being implemented on this account using Micro Focus UFT. Automation is triggered through ALM. We have the test scripts stored in ALM that are triggered through the execution dashboard. Also, the reports are available on the dashboard. We do defect management through ALM, which is the typical use case. The defects are raised in our different locations, then the collaboration between the development leads and testers happen through ALM. We use the Test Plan module where we have test cases related to all our different releases up until now with a few current releases as well. We use the Test Lab tab to pull test cases from Test Plan and do executions accordingly. We have also created some smoke and sanity testing suites where we pull test cases, then execute them when required during the project phases. View full review »

The primary use case is test management, e.g., test executions using UFT combined with Business Process Testing. We do also requirement traceability, where we pull requirements out of a source system, then we link test cases to those requirements in order to have a coverage matrix. View full review »

We are from a Vodafone department that manages testing and quality. We brought this tool in to assist us. We are constantly using it. 95 percent of projects are running on it. We mostly use this solution on our laptop devices. View full review »

We use it as a test management tool where our requirements and everything we need are entered into it and we manage the test cycles. When new products come out, the requirements are gathered and captured. Based on that, the test scripts or test cases are created and uploaded. Eventually, the functional analysts or testers run different test cycles, such as integration, user interface, and user acceptance test cycles. We log the defects with it as well. Based on the metrics, if a product qualifies, it is moved to the next cycle. View full review »

To store all tests including manual and automated tests along with the results of tests after they were executed. Tracking defects, scheduling test sets for automated UFT tests to run unattended from the Test Lab, storing the test cases, and also storing the test requirements in the Requirements Module. The Application Lifecycle Management Process with ALM includes the following phases * Release Specifications: Develop a release-cycle management plan to help you manage application releases and cycles efficiently. * Requirement Specifications: Define requirements to meet your business and testing needs. * Test Planning: Based on the project requirements, you can build test plans and design tests. * Test Execution: Create a subset of the tests in your project designed to achieve specific test goals. Execute scheduled tests to diagnose and resolve problems. * Defect Tracking: Submit defects and track their progress and status. View full review »

In our organization, the manual testing guys write manual test cases through Excel. Then they import them to ALM. They'll move in all the details. Based on that, the automation team will take care of developing the scripts through Micro Focus Unified Functional Testing and they'll add the script into the test plan. Once the lead has approved the test plan he will move all the test cases into the test labs. If any defect is found in new releases, it is logged in the defects column. View full review »

We started an SAP implementation about four years ago and it was selected as the test management tool at the time. View full review »

I'm the admin for our organization's Quality Center. I define the guidelines and projects for use. We use also use it for management requirement testing. Though, we are not doing automated tests or defect management right now. We can't use the Quality Center for everything because the login is only about the user ID and password. Because of this, we are not using the data in Quality Center for all projects. It is quite complicated because I have about 200 projects, mostly SAP, and all of them have to work in the same way. I do a lot of reporting and everything has to be more or less the same. View full review »

We're primarily using the solution as a testing tool where we're recording our testing data. Our use cases vary, however. Right now, for example, we're merging two companies together. When we are doing that, we have various test cycles and we have gone through three test cycles so far. aNow we're heading into UAT. So we're testing all aspects of the business, including HR, operations, gas, and electric generation. We're doing pretty much our stand-alone tests, or unit testing. Then we will then go into our end-to-end testing where all of the systems are working together. After that is done, we'll be heading into more of our business testing, our UAT. View full review »

We used it for multiple platforms in our organization. The IT platform was divided into groups, into towers, and each tower was using it. I used it for multiple towers together. I was managing it for my individual tower. But if there was a roll-out of the regression plan and we needed to see how many would be impacted, we were pulling out the ALM regression part from each and every tower and building it into one. View full review »

I primarily use the models from Quality Center. The requirements, the plan, lab, and effects, et cetera. I use it to merge my entire cycle of debts. View full review »

It is a test management tool where you write the test plan, test scripts, and test cases. You can log the defects that you found during the testing. You can also use it with other integrations, such as automation using UFT, where you execute the scripts from Micro Focus ALM Quality Center. We are using the latest version of this solution. View full review »

We are a consultancy. We use ALM Quality Center for handling waterfall type projects. If our clients are taking an agile approach, then we talk to them about Octane, which is the agile solution. View full review »

We use it for managing requirements, testing, and defects. View full review »

We provide support for customers, which require this kind of solution. View full review »

We primarily use the solution for test management. View full review »

We use this solution for test management purposes. For sorting set cases, testing for possible defects, executions, and so on. View full review »

Consolidate the testing process, centralised reporting, ease of analytics on metrics, easier bug management, consistent flow of requirements, flow of test cases, reusable test cases, testing history, bugs. View full review »

We planned on using the solution for defect testing but it was a low priority for us, we never got around to it. View full review »

We use this solution for an Avionic System to test for integration and verification with real and simulated hardware. View full review »

* Test management * Defect management, and * Test case storage. View full review »