The most valuable features of ALM are in the new upgraded version of 12.53. We're able to more accurately document our test results, our actual versus our expected results, with the new screenshot functionality. That is the most useful part of the tool for me right now. Of course, we use it as our testing repository, and it's basically the way to show the work that we do as QA testers, and to have a historical view of those executions.
Quality Assurance Software Management at a healthcare company with 10,001+ employees
Allows us to more accurately document our actual versus expected test results
Pros and Cons
- "It's basically the way to show the work that we do as QA testers, and to have a historical view of those executions."
- "I'd like to be able to improve how our QA department uses the tool, by getting better educational resources, documentation to help with competencies for my testers."
What is most valuable?
How has it helped my organization?
Because we can trend repeatable results, we can look at trends of things that are continuously working well, and things that continuously get broken within the software development process. So it helps us improve our testing quality.
What needs improvement?
Sprinter, I think, is a good part of this ALM tool, but it has some limitations for us. Based on the type of software we use - we have some web based applications and also some power built applications - not able to capture all the objects, or the way that we develop our software. We're not able to use it as much as we would like to. So Sprinter would be something I would like to see better integrated with the different types of technologies used by the software companies.
I'd like to be able to improve how our QA department uses the tool, by getting better educational resources, documentation to help with competencies for my testers, to make sure they understand how to use the tool. Do they really understand how they're using it? Why they're using it. So, for me, that would useful.
What do I think about the stability of the solution?
For us, so far, it's been pretty stable. Because we have such a ginormous amount of historical data, we've had a little bit of an issue with performance. We were working on copying and creating a new database for that because we have products that we use, FDA regulated products, and we can't get rid of those testing results. So we have to keep them for the life of the product.
So of all of the things that we've experienced, or had issues with, it would be the amount of data we're able to store, because we have to keep everything.
Buyer's Guide
OpenText ALM / Quality Center
January 2025
Learn what your peers think about OpenText ALM / Quality Center. Get advice and tips from experienced pros sharing their opinions. Updated: January 2025.
832,138 professionals have used our research since 2012.
What do I think about the scalability of the solution?
That would go to what I just mentioned above. We're looking at ways to improve being able to capture more results without impacting our products.
How are customer service and support?
I haven't used tech support because we have a couple of different layers within the business unit. So I have people that I can go to, and then those people go to tech support. So it is utilized on a different level, just not by me.
What other advice do I have?
When selecting a vendor to work with, the most important criteria are flexibility, availability, and scalability.
I would say it's a good tool. You have to invest the time into learning the different ins and outs of the tool, and become educated on it. I think it can scale as much as you allow it to, but you have to put the time into learning what it has to offer.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Subject Matter Expert at a insurance company with 10,001+ employees
Cross project customization helps to maintain standards for fields and workflows throughout projects
Pros and Cons
- "Cross project customization through template really helps to maintain standards with respect to fields, workflows throughout the available projects."
- "Defect ageing reports need to be included as built-in."
What is most valuable?
Cross project customization through template really helps to maintain standards with respect to fields, workflows throughout the available projects.
Traceability feature really allows you to maintain linkage between all the test artifacts, starting from Releases>Requirements>Test Coverage>Test Execution>Defects. ALM allows you to maintain complete end-to-end process.
Business Views has really come in handy for all users, as different kinds of reports can be created very easily and published to all the stakeholders.
Synchronizer add-in has allowed us to integrate Microfocus ALM to other third-party tools like JIRA, ClearCase and ClearQuest, and helps to eliminate the isolation between these tools.
ALM has brought great collaboration among the team members.
How has it helped my organization?
Helps to maintain all the test artifacts in one place as a central repository where all teams can contribute and collaborate with each other.
What needs improvement?
Dashboard
- Defect ageing reports need to be included as built-in
- Availability of built-in report related to Defect Removal efficiency
- Availability of built-in report for calculating Defect Density
- Availability of built-in report for end-to-end traceability
- Availability of reports specific to Automation projects.
Management- Libraries
- Ability to include Test Set data in Libraries so that Test Set execution can be transferred to other projects using Library functionality
Test Lab
- Ability to upload Test Execution results from Excel to HPE ALM
Test Plan
- Ability to maintain Manual and Automation projects in single HPE ALM project
- Composite execution of manual and automated scripts would be helpful
Defects
- SLA-related ability for defect module where ALM would send automail to stakeholders for the defects which have not been updated in a long time
For how long have I used the solution?
I have been using the solution for 10 years now.
What do I think about the stability of the solution?
ALM is quite a stable application. We had some issues during the initial setup but it's been stable since, due to right level of competency/expertise we have in the organization to maintain the ALM setup.
What do I think about the scalability of the solution?
No scalability issues.
How are customer service and technical support?
Technical support is not that great. We really need to push to get HPE support to provide a resolution for technical issues. Tech support needs to improved now, as it has deteriorated badly.
Which solution did I use previously and why did I switch?
HPE ALM was our first choice.
How was the initial setup?
Initial setup was not that complex.
What's my experience with pricing, setup cost, and licensing?
HPE has always been flexible in terms of pricing and licensing, but we are a bit concerned with the fact that it is now in the hands of Micro Focus and things may change.
Which other solutions did I evaluate?
No.
What other advice do I have?
Think about the below before you start implementing this product:
- What’s the total user base you are expecting to on-board?
- How many projects/countries/entities are going to be on-boarded to the platform, and then design the hardware configurations accordingly.
- Do you have any other tools which need to be integrated with this product? Is there any ready-to-use integration already available or do you need to build it from scratch?
- Note that this product does provide the ability to control user access and provides security.
- Talk to your network security team and check if anything specific needs to implemented along with this product, like dual factor user provisioning, reverse proxy, TLS 1.1, TLS 1.2. Does this product support all these?
- Check the organization plan in terms of roll-out of latest Operating Systems, Browsers. Does this product support those latest OSs, browsers, versions, etc?
- Hire a HP ALM administrator expert who can guide you to implement the product in the right manner.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
OpenText ALM / Quality Center
January 2025
Learn what your peers think about OpenText ALM / Quality Center. Get advice and tips from experienced pros sharing their opinions. Updated: January 2025.
832,138 professionals have used our research since 2012.
Senior Systems Engineer at a financial services firm with 1,001-5,000 employees
The advantage is that we can test applications before they go to production.
What is most valuable?
ALM is a giant library, and Performance Center and LoadRunner require it to run.
How has it helped my organization?
We use it to support Performance Center and it runs underneath it as one big system. The advantage is that we can test applications before they go to production, and as long as we're testing in a production-sized environment, we have a pretty good idea how an application will perform in production.
What needs improvement?
It's like the overall software framework, and Performance Center is just leveraging that framework for storing things such as tests, scripts and test results. ALM works together with LoadRunner and Performance Center as one big system. As newer protocols are developed and newer technologies come along, it's nice to see HPE be ahead of that as much as possible so that by the time that it's really needed, they're already ahead of the curve and they've got most of their performance issues resolved as far as how the software's going to run.
What do I think about the stability of the solution?
The stability on the old versions is good. On the newer versions, the bleeding edge is still being worked on.
What do I think about the scalability of the solution?
It's very scalable. No issues with scalability.
How are customer service and technical support?
Premium support is great, but before that when we just had general support, it was not all that great. We had issues with trying to get support to call us back on tickets and turnaround time on resolution.
Which solution did I use previously and why did I switch?
We previously used IBM Rational.
How was the initial setup?
It's not exactly straightforward. Their instructions were not all they could have been, but we still got it installed.
What other advice do I have?
As far as we know, it's the best tool on the market right now. They're considered the Cadillacs of the testing tools right now. Don't necessarily go with their most recent version code release right now. It kind of depends on what your needs are and the size of computer shop that you've got.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior Analyst at a financial services firm with 10,001+ employees
When it records a test, it will produce analyses to do cross-project reporting. This becomes a large repository of data and information that's valuable for us to make necessary improvements.
Valuable Features
The most valuable feature for us is probably the full Oracle component of ALM. It allows our users to be connected to other products.
Improvements to My Organization
We're able to use it with UFT/QTP for defect management. When it records a test, ALM will produce analyses to do cross-project reporting. This becomes a large repository of data and information that's valuable for us to make necessary improvements.
Room for Improvement
I'd like to see them move away from a desktop-type client and towards a web-based client, although we've also had ActiveX issues with web clients.
Use of Solution
ALM, as a group, has probably been in use for 10 years plus.
Deployment Issues
Once installed, no issues with deployment.
Stability Issues
The application itself tends to be very stable, but when switching to an open-source website, that's where the issues are. So it's not so much the core application having issues. For example, you may find that it would be an Oracle issue and not an ALM issue. But really there are very few occurrences, even after all these years, of a serious application fault.
Scalability Issues
Scalability is fine. We have in the region 15,000 registered users and up to 2,200 concurrent users of ALM. We don't really have any scalability issues.
Any issues would have to do with what a certain server application is up to. You just need to keep an eye on it.
Customer Service and Technical Support
We have the higher level, premium support. Technical support tends to be quick and reactive to issues and we don't have any major issues with it.
Initial Setup
As large as it is, it's pretty straightforward to put in and you can configure it in probably less than an hour.
Other Advice
My advice would be to research the full system requirements you need for the initial install. In corporate environments, once you've got it up and running, it's more difficult to get off of it. Also, plan to scale up based on projected CPU and space that you'll need to get.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
System Analyst at a mining and metals company with 1,001-5,000 employees
The Business Process Change Analyzer (BPCA) feature can analyze objects on SAP transport requests to create a Test Set according to scenarios created.
What is most valuable?
All features have their own value, but the most valuable ones are--
- Customizations
- SAP Solution Manager integration
- Test set building
How has it helped my organization?
Change Management integration - The ability to create change documents on Solution Manager linked to an event and to change its status according to ALM status or to customize it. This is new and I've only used it on one project so far.
Business Process Change Analyzer (BPCA) - It can analyze objects on SAP transport requests to create a Test Set according to scenarios created. Also, because ALM is integrated with blueprints that generate requirements that are converted into a test scenario to validate the changes, it checks if those changes will cause an impact on the selected business process.
Manage Regression Testing and Integrated Test - It's the most important and most popular feature for all the projects I have worked on.
For how long have I used the solution?
I've been using it for five years, and currently use it alongside HP ALM v11.52.
What was my experience with deployment of the solution?
We had problems with Solution Manager/SAP integration and use through customizing RFC calls.
What do I think about the stability of the solution?
Not with the tool. Usually problems happens because of a network delay or instability.
What do I think about the scalability of the solution?
An HP expertise team was put together for implementation if needed, but there was no need for them.
How are customer service and technical support?
Customer Service:
10/10
Technical Support:10/10.
Which solution did I use previously and why did I switch?
I had already used IBM Rational, which is good too, but the HP tool is more complete.
What about the implementation team?
It was done in-house. The team that works here has experience with HP Quality Center and ALM on other projects. The team expertise is high.
What's my experience with pricing, setup cost, and licensing?
Depends on how much you pay for this product and the size of the project. For a big project, it's a great tool that will help a lot.
What other advice do I have?
Use all that his product can offer as there is no need to buy others that can do the same tasks that HP Quality Center does. It's a complete tool that you can customize according to business/IT/user needs.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Architect with 1,001-5,000 employees
Decent support in resolving issues but steep learning curve
HP ALM 11.0
The ALM market is rapidly maturing as organizations recognize benefits of the holistic approach to managing requirement, builds, tests and releases, and vendors rush to satisfy the demand.
In addition to the numerous commercial offerings one might be able to assemble his own ALM stack with best-of-breed components. There are many tools that excel in specific are of ALM such as requirements management, or defect tracking (e.g. Atlassian Jira); then there are suites that integrate most of the capabilities (e.g. CollabNet, RallySoftware), and there are integrated stacks focused on specific technology (e.g. Microsoft TFS, even with a limited support for Java platform)…
But there are currently only two fully integrated enterprise class technology vendors - HP and IBM – that rule the ALM universe.
Most of the vendors offer the standard set of capabilities: requirements management, defect tracking, release management, IDE integration etc. The one component missing from the most ALM vendors is integrated Quality Assurance, and HP with its acquisition of Mercury Interactive in 2006 leapfrogged every other vendor (including IBM), and currently holds about 40% of the automated testing market with its Quality Center and Performance Center suites (QuickTest Pro, Sprinter, Service Test and LoadRunner) - all integrated into HP ALM 11.
HP ALM also takes top spots in Requirement Management and Integrated Software Quality Suites (Forrester Wave, Gartner's Magic Quadrant), with respectable showing in other areas. Ultimately, selection of the ALM suite would depend on number of criteria - strategic enterprise architecture, technology affinity, maturity of the enterprise, costs, to mention but a few.
In my case, after weighing a number of factors for my own organization, the decision was made in favor of HP ALM, strongly influenced by the suite's capabilities, QA integration, relatively low pricing (into seven figures), and ability to start right away with with preconfigured application (with SaaS deployments option).
What's included'
- Project Planning and tracking
- Release management
- Requirements management (definition and management - including versioning support)
- Quality Management (functional, performance, security)
- Development management (defect tracking, IDE and source code control integration)
HP offers both on premises and SaaS options for its ALM suite. The latter option provides convenience of a fast deployment but you do cede some control; some of the features (e.g. LDAP integration) might present challenges and incur additional costs.
The HP ALM application is a JEE app, with its server portion running on variety of platform - Solaris, HP-UX, AIX, Linux and Windows.
The user access is either through a browser or a desktop client, and, unfortunately, it currently imposes severe limitations - while administration can be performed through any browser (Firefox, Chrome, IE), the main user functionality is IE only (an attempt to access ALM from any other browser would give you a message "Only Internet Explorer 7 and Internet Explorer 8 are supported." - leaving IE 9 and 10 out of equation, as well. Hopefully, this deficiency will be addressed soon. Since the desktop client is Windows only as well, this makes all client activity "Windows only" (same goes for the rest of the tools - QTP, Sprinter etc.)
There are several licensing models available, and selection should be made based upon both your current and future needs, as well as anticipated mode of operation (e.g. concurrent license vs named license vs floating license); it also affects the pricing.
The next big decision is selecting topology of the projects; HP provides a best practices white paper to help you select the most appropriate one for your organization. While the application allows for mix-and-match approach, some capabilities such as sharing artifacts across domains and projects might be affected.
Security considerations are standard for any JEE application: firewalls, DMZ, reverse proxy, security certificates etc. Most of these would be taken care of with SaaS option; it is DIY for on-premises one. The application itself provides robust role-based security, with configurable attributes and customization.
SaaS option comes with a number of benefits as well as drawbacks, and deserves a consideration of its own. Keep in mind that you do lose some control with it: for instance, you won’t be able to have “Site Admin” privilege, the highest one will be TDAdmin - plenty to administer domains, projects and users - but for everything else you’d have to go through “official channels”, namely your HP SaaS representative (like, configuring third party integration, or enabling/disabling Performance/Quality Centers integration); the LDAP integration also becomes a separate integration project instead of a built-in feature and so on. Make sure that you weigh all the options before you choose the deployment model.
Once the application is up and running it is pretty straightforward to administer through a browser of your choice; keep in mind that your users will still have to use IE 7/8 or a desktop client. It is recommended to use the desktop client - especially on newer machines where older versions of IE are hard to come by. In order to provide rich client functionality, both IE and the desktop client will install sizeable .Net libraries, and will require VC++ redistributable to be installed first; for HP Service Test WSE 2.0 SP3 Runtime and MS Access Database Engine 2007 will be installed - a minor inconvenience but something to keep in mind when planning rollout.
The HP provides a number of tutorials (PDF, movie files, online resources) on how to use the application, as well as a number of classes to familiarize yourself with the product. While the tutorials are of high quality, and will get you through the initial steps, the complexity of the suite is such that budgeting some classes - online/on site - is highly recommended. You’ll learn about many best practices, ways to organize your projects for maximum reuse through libraries and templates, configuring KPI and dashboards; consider it as an upfront investment to jumpstart your efforts.
The product is geared towards traditional SDLC but can accommodates various project management styles (e.g. an Agile Accelerator plug-in is provided at additional cost), and does not impose many constraints - for instance, one could decide to start cranking out requirements, and then associate them with release cycles, and another might spend some time honing her release management strategies. The application provides built-in versioning control (an option to be enabled once project is created); use it - if something is not under version control, it does not exist. This goes for requirement, source code, attached documents - everything!
Once created, requirements can be converted into manual tests with a built-in wizard, accessible from pop-up menu. It creates an editable test suite which traces back to original requirements, and could be run - either in Sprinter or through manual runner - almost right away; this might prove to be a significant time saver. One of the most important features to maintain control over your project is traceability matrix - ability to link requirements to tests to test results to source code to defects - would allow you to keep tabs on your project, and drill down to the root cause quicker than otherwise possible.
The application supports variety of reposting options - from configurable graphs (trend, pie, bar etc), to reports in PDF, Microsoft Word and Excel formats. Reports could be assigned public or private folders, and be combined into dashboards of the same visibility.
The HP Quality Center and Performance Center are tightly integrated with HP ALM suite. These are based on LoadRunner (load and stress testing) and QuickTest Pro which, together with Sprint and Service Testing, is known as UFT - Unified Functional Testing. Both QC and PC are integrated into administrative console, and are available to the users based upon assigned role.
The HP ALM suite integrates into Software Configuration Management environments you might have assembled in your organization, including support for SCM suites (e.g. AccuRev, IBM ClearCase) the most popular products in each category: development environments (Eclipse, Microsoft Visual Studio, InteliJ IDEA - no out-of-box integration with Oracle JDeveloper/NetBeans), source code version control (Git, SVN, Perforce, TFS), continuous integration build servers (Jenking/Hudson, TeamCity, Microsoft TFS), source code quality tools (JUnit, NUnit, TestNG), code coverage analysis tools (NCover, Cobertura), static code analysis (Coverity, Fortify). Some of the integration capabilities are fee add-ons, and some require third party software (for example, IBM ClearCase is integrated through OpsHub, and IBM Rational Team Concert/Jira, Rally or Collabnet - with TaskTop connectors)
To sum it up:
Pros:
- Tight integration with quality assurance suite including functional testing, performance testing and security testing.
- Costs (compared to other integrated ALM vendors)
- Provides two deployment options - on premises, and SaaS, and for on-premises gives a choice of the platform - from Unix to Windows.
- Enterprise class application supporting variety of project management styles, fully integrated stack with full traceability between requirements to tests to defects to source code to release cycles.
- A number of integration options with developers’ tools, software configuration management suites, and third party tools (continuous integration, ALM and more).
- Decent support in resolving issues.
Cons:
- Complexity.
- Costs (well into seven figures, depending on configuration options)
- Steep learning curve.
- Limited choice for the desktop clients (Windows only), including both QA and HP ALM proper. Occasional bug requiring user to submit ticket to HP.
- Integration options are limited, some require third party software.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Thanks for the information about integration - it really helped (I didn't know that 3rd party tools like www.opshub.com has these integrations)
Executive Vice President at a financial services firm with 10,001+ employees
Does not integrate with DevOps tools, support needs improvement, and it does not scale well but it's stable
Pros and Cons
- "Micro Focus ALM Quality Center is quite stable."
- "It is not a scalable solution."
What is our primary use case?
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.
What needs improvement?
At this time, we don't feel that this solution has any value. We are communicating with Micro Focus to address this commission where we feel that it has more value added to it.
The integration needs improvement. It is not integrated with the rest of the ecosystem. It's a stand-alone tool right now used for testing and defects. We are considering and testing Octane because it seems to have more integration with the DevOps ecosystem.
For how long have I used the solution?
I started using this solution when it was Test Director. This was before it was upgraded to Micro Focus ALM Quality Center.
I have been using it for the last 10 years.
We are not working with the latest version. Rather than upgrade to the latest version, we are considering moving to Octane.
What do I think about the stability of the solution?
Micro Focus ALM Quality Center is quite stable.
What do I think about the scalability of the solution?
It is not a scalable solution. I am not satisfied with the scalability of this product.
We have less than 50 concurrent users.
How are customer service and technical support?
This is a product acquired from HPE. Before this, we were not satisfied with technical support. Micro Focus seems to be trying to improve their support quality, but we haven't seen it yet.
How was the initial setup?
It doesn't take a long time to install this solution.
What's my experience with pricing, setup cost, and licensing?
It's a perpetual license.
Which other solutions did I evaluate?
We are reviewing other solutions and looking to upgrade to Octane. We are currently, in the testing phases with Octane.
What other advice do I have?
I would rate Micro Focus ALM Quality Center a four out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Consultant at a tech services company with 501-1,000 employees
A straightforward setup with good analytics and very helpful technical support
Pros and Cons
- "Most of the features that I like the best are more on the analytics side."
- "The uploading of test scripts can get a little cumbersome and that is a very sensitive task. They could improve on that a lot. It's really important that this gets better as I'm loading close to a thousand test scripts per cycle."
What is our primary use case?
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.
How has it helped my organization?
The ability to really deeply analyze everything down to individual users has been very useful for the organization as a whole.
What is most valuable?
Most of the features that I like the best are more on the analytics side. We are generating our analytics from the execution module. After your tests are executed, we're able to generate all of our analysis for our presentations and to present findings to leadership. There are a lot of different views that you have access to. You can show your pass rate, your fail rate, etc. You can pretty much drill it down all the way to what each tester is doing. That's one of the really good features that they have at ALM.
The initial setup is very straightforward.
The solution is very easy to use, even right out of the box. You don't need to do a lot of configurations.
You can create roles and assign various rights to each of the roles per project. You can really customize the product.
What needs improvement?
The uploading of test scripts can get a little cumbersome and that is a very sensitive task. They could improve on that a lot. It's really important that this gets better as I'm loading close to a thousand test scripts per cycle.
For how long have I used the solution?
I've been using the solution for about three years at this point. It's been a while.
What do I think about the stability of the solution?
The solution is extremely stable. We really have not had any issues even after upgrading and taking the whole system down. It's very user-friendly right out of the box. There aren't bugs or glitches. It doesn't crash or freeze. It's reliable.
What do I think about the scalability of the solution?
The solution can scale well. If we need to add different modules to it, it has the ability to expand. You do need licensing for that. However, the out-of-the-box features included in the solution are great.
We haven't really scaled it just yet. We have about 250-300 users right now. They are largely tester, developers, admin and project managers.
How are customer service and technical support?
Technical support so far has been great. I've found that we can tell them about an issue, and they're usually back to us within the same day with a solution. We're quite satisfied with the level of service provided. I'd rate them ten out of ten.
Which solution did I use previously and why did I switch?
This is the only solution I have ever used. I don't know if the company worked with something else previously.
How was the initial setup?
The initial setup is quite straightforward. It's easy. We didn't face any difficulties at all. I wouldn't describe the process as complex.
What other advice do I have?
We're just customers. We don't have a business relationship with ALM.
If you want a good tool that is robust and is very user-friendly and capable of supporting a program with multiple streams or multiple workstreams, ALM would be the perfect tool. It can basically track all of your testing. It also allows you to collaborate with all of your testers, stakeholders, etc.
I would rate the solution at an eight out of ten due to the fact that it's user-friendly, and it has the ability to track various projects or various workstreams of a program. Also, the test scripts are reusable. For example, let's say if we are going to utilize those same test scripts for another project, a couple of years down the line, they are available, and you can do real-time updates within ALM. That's really helpful.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free OpenText ALM / Quality Center Report and get advice and tips from experienced pros
sharing their opinions.
Updated: January 2025
Popular Comparisons
Microsoft Azure DevOps
Rally Software
Polarion ALM
OpenText ALM Octane
Jama Connect
IBM Engineering Lifecycle Management (ELM)
Digital.ai Agility
Planview AgilePlace
Buyer's Guide
Download our free OpenText ALM / Quality Center Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Has anyone tried integrating HP ALM and JIRA ?
- Do you have any feedback on the HPE ALM Octane release that came out in June 2016?
- What is the biggest difference between JIRA and Micro Focus ALM?
- Has anyone tried QC - JIRA Integration using HPE ALM Synchronizer ?
- Integration between HP ALM and Confluence
- Which product do you prefer: Micro Focus ALM Octane or Micro Focus ALM Quality Center?
- When evaluating Application Lifecycle Management suites, what aspects do you think are the most important to look for?
- Looking for suggestions - we need a test management and defect tracking tool which can be integrated with an automation tool.
- Looking for a Comparison of JIRA, TFS & HP ALM as a Test Management Tool
- Do you have any feedback on the HPE ALM Octane release that came out in June 2016?
I love the requirement traceability functionality of ALM, make it good for reconciliation of test cases