OpenText ALM / Quality Center Reviews

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.

The solution reduces testing time, although not in all cases. But it is capable and in some cases, like for web testing, where we are easily able to capture screenshots and videos within the ALM workflow itself, or the test execution steps, it really saves us time. Otherwise, the guys have to keep on capturing screenshots into a file. Here, they can upload  everything in one shot. In that aspect, we have seen some savings in execution and, while they are not that drastic, it does help.

When it comes to the test planning cycle, if I have my regression cases, they could be almost 40 percent of the cases and they are repeated. So instead of uploading them again, I can easily replicate them in ALM. That is one way I am able to save and I would estimate that saves around 25 to 30 percent. The other part is when it comes to the execution steps. The savings are not so drastic but they could be between 5 and 10 percent.

The best thing is that you can see your current status in real time. Our people are deployed mainly offshore, and we have some guys working onsite as well. We have close coordination of the teams using calls. To see real-time updates, you just log in to ALM and you can see exactly what the progress is. You can also see if the plan for the day is being executed properly, and it's all tracked. From the management side, I find those features very valuable.

The ability to connect all related entities and to reflect project status and progress is the main thing that, as a manager, you are able to see: progress in real time. If the guys are updating the status in real time, meaning that as soon as they finish execution they update the status, it is really helpful.

If you ask the testing guys what is most valuable, for them it's like a one-stop, central location for every project, where every artifact and everything else is recorded. It is a single point where you can store everything. It's very easy to track and escalate. The solution does a lot of things which will support you in your project delivery phase.

When it comes to managing multiple projects, as long as everybody is actually recording all the requirements in the Requirements module of the tool, and from there the test cases and test plans — if everybody is doing that — it is really helpful. When we look at the status, we can actually map it to the requirements and we can see which of the requirements have been completed end-to-end, what we're spending, and so on. However, one thing we see is that not everybody uses the Requirements module to log the requirements. For certain projects, people just start using ALM from the time they upload the test cases, during test planning. In such cases, I am not able to see all the information. But for the projects where ALM is being used end-to-end, it is really helpful. The tool itself is really good. It all depends on how you are using it.

In terms of the solution’s ability to handle a large number of projects and users in an enterprise environment, I am sure the solution is capable. Our current usage here is not so large. But I previously worked in companies where around 300 users were using ALM for everything. In that setting, it was a central location where we could see all the results in real time. Here, I handle around six or seven projects simultaneously. But I have seen people who are handling up to 30 or 35 projects simultaneously, all using ALM. I've seen other organizations where people use it completely, for all their projects. There may be different managers, but it is a single location where everything can be tracked. It is scalable and it is pretty user-friendly as well.

In ALM, when you start to execute something, you can record and capture screenshots and videos. Once the team was trained in those features, I could see that they started recording and that they were doing the execution. When they close the last test, the recording is attached automatically. The tool is capable and, again, it comes down to how people are using it. If they are using it in the right way, we are able to capture everything.

ALM only works on Internet Explorer. It doesn't work on any other browser. In my opinion, Internet Explorer is generally a bit slower. I would like to see it work on Chrome or on other browsers. We have other applications that work perfectly fine with Chrome. It is not a major problem, but browser compatibility is an issue. And if you're using a Mac, it doesn't work.

We have a digital platform and we have done a lot of automation using Selenium there. Those tools have the ability to work in Chrome. But I am not able to integrate ALM completely, end-to-end. For example, using the automation tools we have to initiate test execution from ALM and then take all the results and upload them back. So I'm not able to work end-to-end because of the browser compatibility issues.

The majority of our guys are working on Windows and they have IE. For manual execution, I've never seen a problem. But when it comes to automation, I have an issue.

We've been using Micro Focus ALM Quality Center for about eight years. Our company has been around for almost 11 years. Out of that, for about eight years we've been using HP QC, now known as ALM. We've been using it continuously throughout that time.

I just recently returned to this team. When we started the testing phases here, I was leading the team. I moved out and I just joined it again three months ago. When I left, we were on version 11 so we must be on 12.55 now.

The solution is on the cloud, it is not on our premises.

It is pretty stable. I don't think we have seen any issue. The availability is always 99.999 and it has never been down unless there is a planned outage. 

In the last two years, we have seen issues for two or three hours, but that is the maximum we have seen. 

When there is a planned outage they always notify us in advance. Otherwise, the application is always available. Our guys work in multiple shifts. They work throughout the day and they work at night as well and it's always available.

If we request any kind of support, they are always there to help. They are very good.

Before ALM, we were only using Excel. But along with ALM right now, we also have some projects that are using JIRA, and there are some people who are using Confluence. The digital teams here are using JIRA.

The initial setup was pretty straightforward. We had engineers come in and they gave us training and showed us what we would be doing. They were very supportive, from the customer onboarding perspective. They did a very good job. Initially, there was all this complexity. We didn't know how to manage it because it was very new to the team. They came and trained us very well. To put it simply, the onboarding process was amazing. We have monthly sessions with their team and we have continuous contact. It's pretty organized.

They started the planning two months ahead. Everything happened in a proper, planned way. That is something I really like about Micro Focus. The initial installation took almost two months. In part, that was because of internal problems. We were using Excel and some other tools. To migrate from there to ALM took some time. That included moving the data. We had to make sure that whatever data we had was not lost and that even the number of test cases was the same as what we had before.

Upgrades happen in a single day, or sometimes two to three days.

In terms of the implementation, it happened a long time ago. They first asked us for a timeline and they then held multiple sessions on the features and the abilities of the tool, with multiple teams over the course of two to three weeks. After that they came and deployed ALM itself and tested the compatibility with our machines, because we had some desktops and laptops. That took some time. Micro Focus gave us an installer that we had to push to all our machines. Once all the machines were updated with the installer, we started using it.

We have definitely seen return on our investment in Micro Focus. Imagine the amount of hours that our guys would be spending tracking stuff in Excel. If you look at the number of man-days that my team would have to spend on that and at the licensing costs, of course it is worth it. I'm very happy with it.

The pricing has been the same for the past few years. It is reasonable. It is not very high. Of course, the cheaper the better, from our point of view. But the tool and its quality are amazing, really good. And including the support their team is giving us, I think the price is justified. It's a fair price.

We did not evaluate other tools at that time. My manager and I — we came from different organizations — had both been using HP. I was using HP QC 9.0 when I moved here. When we started off our testing stream, the only tool that came to mind was HP. In addition, HP was one of the vendors that was being used for testing other stuff in our company.

Even now, we are not looking at other tools. 

It's all about the mindset. ALM has a lot of features. We, ourselves, are only using about 30 percent of the features. If you are expecting that when you start deploying ALM you'll be using everything it has, that's not the case. Of course the tool has all the features, but there are some customizations that can be done based on your needs, and the Micro Focus team will be able to help you with that. It's all about setting expectations and telling them exactly what you want.

Initially, we were not sure what we wanted to see. But after some time we understood that there are so many features. For example, the reporting part: ALM has automated reports but they require some things to be entered at first. If your team has the skill to set up your own stuff, that's good. If not, the Micro Focus team can support you. ALM can automate reports so that, at the end of the day, it sends out an email so your team doesn't actually have to prepare all that information and send it.

To make full use of ALM you have to invest some of your time. It has a lot of features. Most people will just use the basic stuff and they will be happy with it. But if you start exploring it, you will find it has a lot of capabilities. And they are all included in the licensing cost. Don't just go with the flow and keep doing what you're doing. Spend some time and ask ALM the right questions and they'll be able to help you. You will get more benefit out of the tool. That is one thing I have learned in using the solution.

Micro Focus is still investing in the product and releasing valuable features. We have been asked to upgrade our version so that means they are working on upgrading features and are fixing bugs. In previous versions, I was seeing that things were a bit slower. It took time to actually load. But now, my team is saying that it is fine.

In terms of security, ALM has controlled access. Every user has his own login and password. We restrict access. There is one admin on our team and he's the guy who controls who accesses our systems. Before we create a user ID for someone, they have to go through a review process. We need to understand which team he is working for and for how long he will need access. In that way, we keep things in control. As for uploading our data, I don't think anybody will be able to access it. It's pretty secure.

Right now we have 35 licenses for 35 concurrent users. But the number of actual users is around 400. It's being used by our testing guys as well as business people and even our senior management. If they want to see reports in real time, they log in and see them. From that perspective, it is really helping us.

We don't have many people involved in maintaining it. I don't have a dedicated person on our side to manage it. Micro Focus manages everything. I have one point of contact and she takes care of everything.

For me and for our organization, it's a really good product. I'm really happy with it. It's a 10 out of 10. It meets my needs completely.

• Requirements sync and traceability: This allows us to see how many requirements have been tested and to show auditors this information easily.
• Test Execution (Test Lab): This allows us to track our manual tests with date and time and enter actual results and screenshots.

QC has been invaluable in the past for documenting our testing process, especially when needed for audits.

The Active-X technology requires client-side installations that are difficult to manage in environments where the tester's PCs are locked down to prevent installs. Test management is too rigidly dedicated to older ways of testing with scripted test cases. More support for newer approaches, such as exploratory testing or behavior driven testing would make QC more relevant to the way testing is done in many current contexts.

ALM requires that you install client side components. If your organization does not allow admin rights on your local machine, this means you will need someone to run the installation for you with admin rights. This client side install is also limited to Internet Explorer and does not support any other browsers.

As far as the test structure goes, you are limited to to a step-by-step test case with description, expected result, and actual result for each step by default. This makes it difficult to support an exploratory testing approach with ALM. Of course, much of this part of the tool can be customized, but it still pales in comparison to something like the Test and Feedback tool that Microsoft provides for exploratory testing.

My understanding is that the newer Agile Manager product is more friendly to exploratory approaches, but I have not used this product yet.

We have been using this solution for 16 years.

In terms of stability, the QC client crashes often when attempting to expand a node on a tree. Upgrades are a nightmare and documentation is difficult to understand.

There were no issues with scalability, but I have never managed a large user base.

Technical support has gotten better than it was a few years ago, but Tier-1 seems to just go through the motions of asking questions I've already answered.

I have used other solutions, but many do not have the traceability requirements that ALM does.

The initial setup was highly complex, mostly because of the database setup. Upgrades are even worse, especially if you need to migrate to a new server, since the repository needs to be copied over.

Make sure you get the correct license for your needs. The full ALM license lets you use the requirements tab, along with test automation and the Performance Center. You can also just buy the Quality Center edition (Manual testing only), or the Performance Center version (Performance Testing only). I have no idea where they get their pricing numbers from, but they seem to always be negotiable.

I have used Oracle's Test Management solution, Zephyr, Bugzilla, TestTrack, JIRA, and others.

Be sure to have a DBA available when you install. There have almost always been changes needed to the DB when I have installed the application.

In our company, the most interesting thing is that ALM can be used for manual testing. The testers can define, by themselves, how they structure the test and then execute it. All the results, both the positive and negative one, are collected. There is easy defect creation.

On the other side, if you look at it as a project manager, you have to see the results, i.e., the current status of the project.

Afterwards, if you get an outage, it is important that you can show the regulators that you did a good job, you executed everything, and you went in production with a concrete status, with no big issues or critical errors.

Our biggest problem with ALM is the version upgrade and especially the migration.

We have 1400 projects which are active. With the next version upgrade, we expect more than 3000 projects that have to be migrated.

The migration itself takes months. Here is something that can be improved. It is very important for us, otherwise each migration would kill us.

I’ve been using ALM since 2004.

If you find the right patch, then it is stable. You can stay with that for years. In our situation, it takes a very long time to roll out a patch and even more time to bring a new release.

ALM is for sure scalable. We are running 1400 active projects with 15,000 users. Concurrently, we have around 1000 users. If there is a performance issue, we have to find out what the reason is. It is true, in most cases, that we need an additional database server. The application servers, if they have enough power, scale a lot.

For such an experienced team as my mine, who have been working with the product for more than ten years, it is not that easy dealing with technical support. They often do not have the knowledge that we have. It takes a while to train them so they understand what our issues are and we have to connect to second or third level support.

The collaboration between HPE and us, especially over the past ten years, has been very good. For that reason, I try to bring in more HPE products, if needed.

This is managed by Tieto, our managed service testing partner. We use ALM as a repository for our automated test scripts. This is only the very beginning of the of our testing and managed testing service journey. The reason we use ALM is it's ability to schedule tests and nightly runs. It creates reports and statistics.

We are only starting off now. I'm able to present the progress on our work with the test-information initiative. I can keep a close eye on what's going on to monitor the progress and to schedule the test runs.

I used Quality Center 5-10 years ago, and I had no issues with it. It is also the de facto industry standard of test management tools. I don’t have enough insight at this point in time. If you ask me in half a year's time, I'm sure I'll have loads more information.

We have had no stablity issues so far.

I know for a fact that it's possible to scale it up. We might add another test management tool in-house that's been there for a long time called Rec Test; a Swedish solution.

It’s a very simple test management and requirement tool. But in the long run, ALM will probably support us better, so that is on my radar to keep track of and see how we can implement them better. This will take a lot of training and convincing of end-users.

I have not used technical support myself, but Tieto is actually doing that in an effort to improve their own framework and initiate a closer relationship with HPE.

Setup was a very smoothly written, spot-on theater.

Not formally, but informally through my own experience. Our use with Rec Test, as well certainly requires more training. It requires a more structured way of working. You really need to set up a good structure, and make sure everyone is following that structure. Otherwise you'll have a mess in no time.

Being able to manage tests as this is something very difficult to find in other products. There are a few open source ones that handle test management, but right now HPE ALM is still the best solution to handle tests.

It helps us to keep track of everything happening. When you test the software you've got results. Results can be OK or not OK. If you just get the results in Excel or things like that, you cannot work as a team because just one person at a time will be able to access it. With ALM, we can have several people working on the same product at the same time. Then we use it a lot for trustability, so we can add trustability to the facts, to requirements. It's very useful for that to verify everything that happens.

As soon as it's available on-premises we want to move to ALM Octane as it's mainly web based, has the capability to work with major tests, and integrates with Jenkins for continuous integration. This is lacking in the standard ALM which was great a few years ago but it did not evolve enough, and that's why we are waiting for Octane.

We've used it more than 15 years, so it's very stable. There is a new version coming, ALM Octane. Octane is new so we don't use it yet.

We have plenty of projects with the current ALM, so it scales well. I'm not afraid of an issue with Octane and believe it will be the same.

I'm disappointed with the support as they're not reactive enough. They don't know the product very well, and to have things changed we need to access R&D directly and then things move. Otherwise, it's kind of difficult.

Beforehand we were using just paper and Excel, and things like that. As soon as ALM was tested at the time we began to use it and sensed it's presence in the company and now every tester is using it.

For ALM it was complex because it's not fully web based so you need to install a client on your desktop and with all the Windows security stuff you need to be an admin on your desktop so it's a very complex set up. On the service side it's kind of complex but we have tech experienced people to do that and to set up the database and everything, so it's OK. With Octane it should be really much simpler because for the user because it's just a web application so you've got nothing to do.

I'd rate the pricing as 3/10 as it's very expensive.

The first criteria we look at is functionality. We have plenty of different projects so we need a full spectrum of functionality. The problem we have today is the price. It's a very good solution but it's expense so we are challenged by our finals and everything but the price.

If you have the money then you can go with ALM, as it's a very good product. You won't have any surprises with it so that's good. Otherwise, there are some open source solutions that are a little bit less functional, but you can play with them and get them to work, products like Squash TM or things like that.

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.

We are able to use Micro Focus ALM Quality Center for test management, defect management, test process, test governance activities, and requirement management. We are able to achieve all of this, the solution is very useful.

Micro Focus ALM Quality Center could improve how the automation process works. Addiotnlally, the parallel execution needs to be optimized. For example, if multiple users, which are two or more users, are doing an execution, while we execute the cases, I have seen some issues in the progress.

Most enterprise solutions are moving into the cloud and this solution could work on its cloud compatibility. For example, if I have an Amazon or a Google cloud, I would like to know how would it best fit into their cloud environment.

I have been using Micro Focus ALM Quality Center for approximately eight years.

Micro Focus ALM Quality Center is a stable solution.

I have found Micro Focus ALM Quality Center to be scalable.

The technical support from Micro Focus ALM Quality Center is good, they are responsive.

I rate the technical support from Micro Focus ALM Quality Center a four out of five.

The initial setup is straightforward, it was not any more difficult than other setups.

The enterprise pricing and licensing are reasonable.

I would recommend Micro Focus ALM Quality Center to others.

I rate Micro Focus ALM Quality Center an eight out of ten.

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

• Reusable test cases
• Requirement traceability
• Reporting.

Test cycles.

Bridge to JIRA and Tableau.