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.

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.

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.

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.

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.

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.

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

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.

It's a business process requirement and is being used for test cases, test executions, defect locks, metrics, dashboards, etc.

In implementation projects, things work in the waterfall methodology so it's the best tool to collect all the requirements in one place to tie up into the test cases and test executions, so this solution is extensively being used in the company for implementation projects, particularly in test management activities. 

We were using Micro Focus ALM Quality Center for our test management for lots of products. I installed ALM myself, and we were using it for SAP deployment. We were using Requirement modules, Test Plan modules, Test Lab modules as well as the Defect modules in ALM. Not only for this product, but also for other companies like Cooper, Active, Delphi, Allegis and DLM for test management.

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.

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.

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.

We're pretty heavily dependent upon that tool, in terms of the test management overall and using UFT as an automation, as well.

We have it deployed in our Data Center and it integrates with it to write a custom application on it. You have to use a sole technology, which is risky. It takes more advanced developers than someone who does JavaScript and makes web pages.

Micro Focus is selling two test management solutions, ALM/Quality Center and ALM Octane, TM, which are identical, except ones built on newer technology

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.

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.

We use this solution primarily for doing test cases and running UFT cases.

When I use it, it is mostly for test management. The instances I've used are mostly on-prem.

We use it for managing requirements, testing, and defects.

We provide support for customers, which require this kind of solution.

I'm using Micro Focus ALM Quality Center for testing purposes.

I used the solution to manage the tests that I would plan and record, and I would manage the flow of defects.

I work for a bank company that has a license to use this solution. I am using the solution through the internal internet, not on the cloud. I am using version 12.

We primarily use the solution for test management.

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

It is underutilized at the moment because we use this solution for tracking the test scenarios, test results, and defects.

We are looking at integrating a tool that can provide integrations with the other DevOps tools.

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

We have been involved in a lot of IT projects which need test management and for the test execution process, we are using Micro Focus ALM Quality Center.

I primarily use ALM Quality Center as a conversion tool.

The primary use cases for this solution are testing, recording and auditing results, and creating test cases and test plans.  

We use Quality Center to track functional testing and record automation testing scenarios results. There are around 1,000 users at my company.