What is your primary use case for Micro Focus ALM Quality Center?

Mine is a testing project. All my requirements, test cases, test executions, and results are maintained within OpenText ALM Quality Center. Both automated and manual testing results are generated from there.

Our primary use case for OpenText ALM is for automation use cases. We can map all the test cases with the requirements. The automation test cases allow the business to clearly see what is automated.

We use OpenText ALM Quality Center for defect tracking and test management. We test the software which we get from our suppliers and do the tests and test management.

I use the solution in my company for test management. In our company, we were creating and mapping our requirements with the scenarios. The tool is used to map defects with test cases for the traceability part. My company has made use of the complete application.

We use the solution mainly for test cases, SAP projects, and login defects.

We used Quality Center for test case management. We wrote and uploaded test cases into it, and we also executed them manually. We could track the results of the test cases, and we could also track the defects that were found. We also used it for higher-end requirements management and traceability. The managers and other stakeholders could track the requirements and see how they were being tested.

We've primarily used most of the solution. Our requirements included test cases and defect handling in the past. We are using it for regression testing and maintenance of test cases to do regression testing when we are upgrading the system.

We used Micro Focus ALM for the bifurcation process. We have different health associations registering on our portal. We import their data into our channels or segments created by us. So, whenever the users import the data, we require a medium to bifurcate it into different divisions. The solution helps us segment the data.

We've mainly been using the product for service requests and for migrating code and scripts for Oracle events.

We are customers of Micro Focus and I'm a senior director of our company.

We primarily use Micro Focus ALM Quality Center for test management, including test case creation and execution, and we also use it for planning different test cycles during regression tests. We handpick the cases, plan different test cycles, and use Micro Focus ALM Quality Center for defect creation.

We primarily use the solution for test management.

ALM is a well-known product and is one of the pioneers in providing test management facilities with a 360 degree view of requirements.

I am using Micro Focus ALM Quality Center for test script preparation and test script execution and defect management. This will enable the programme to capture and store tests for easy re-usability for future deployments.

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

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

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 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.

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.

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

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 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

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

We primarily use the solution for test management.

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 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 planned on using the solution for defect testing but it was a low priority for us, we never got around to it.

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

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

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

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.

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 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.

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

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 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.

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.

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.

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 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.

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.

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.

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

* Test management * Defect management, and * Test case storage.

Quality assurance, requirement, and testing.

* Test management for multiple products * Risk-based testing * Requirements mapping * Reporting.

We use it for manual and automatic testing along with defect and requirements management. We can check everything, know who is the sponsor for it, and make a test plan. Everything is very visible.

I use 80 to 90 percent of the product's features.

My prior organization used the test execution and defect modules for QC. As a manager, I was able to set up reports that allowed me to finds areas of improvement for my team. We used the import functionality to import test cases for reusability and execution.

We use this solution for model testing and as a central location for the test case responses and some test automation.

It is a complete AQM suite: single repository for tests, requirements, defects, etc.

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.

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.