Please share with the community what you think needs improvement with Micro Focus ALM Quality Center.
What are its weaknesses? What would you like to see changed in a future version?
It takes time because it has a 360 view of all the processes when talking about test case, design, and defects. There are so many things to track. Therefore, if I try to inject Micro Focus ALM into a small agile, delivery project, there is resistance. If there is resistance, is there flexibility for customization based on project scale? I don't know if this is possible. Also, it adds time when I upload and execute all my test cases to Micro Focus ALM. For example, when I prepare test cases, I need to run them individually, then upload them to my sheet. After 10 days, I might have finished all my testing after tracking everything in Excel. Moving to ALM at this point adds time and overhead. It increases my testing timeline, e.g., if my testing takes eight days, when I add on time for ALM, the testing time is now 10 days. The version of Micro Focus ALM that we use only works through Internet Explorer (IE). We have to communicate to everyone that they can only use IE with the solution. This is a big limitation. We should be free to use any type of browser or operating system. We have customers and partners who are unable to log into the system and enter their defects because they work on a different operating system.
We would like to have support for agile development. As we do not have this capability, we are now investigating the use of Octane.
Licensing model is awful.
Release management and integration with other tools.
Bridge to JIRA and Tableau.
ALM uses a waterfall approach. We have some hybrid approaches in the company and need a more agile approach. We have also installed ALM Octane and are trying to see if it fills the approach that we are looking for our company.
Certain features are lousy. Those features can drag the whole server down. There are times that the complex SQL queries are not easy to do within this solution. Micro Focus ALM needs to bring the features of this ALM into the newer version of Octane.
* I would love to see QC update and use metric dashboards at the individual and project level. * The UI also needs some updating with a fresh new look and feel.
There needs to be improvement in the requirement samples. At the moment, they are very basic. They could also improve the usability.
* Pure-FTPd WebUI * Single sign-on
When a particular version of Quality Center has reached end of life, the customer is forced to upgrade to the newer version to be eligible to get technical support. The upgrade process can be time intensive and requires a lot of planning. Quality Center seems to originally designed for a Waterfall process. However, the newer versions of ALM are more adaptable to Agile testing methodology. The BPT also known as Business Process Testing can sometimes be very time intensive and sometimes might not be very intuitive to someone who is not familiar with BPT. ALM/QC supports IE but does not support Chrome which a lot of users like/want to use. History of Quality Center including other names and versions: On September 1, 2017 the HPE testing tools officially became Micro Focus. It is too early to see how the transition to Micro Focus will change things. I am keeping an optimistic view that Micro Focus will continue to invest in R&D and place a priority on customer support. I believe a lot of long-time customers would like to see things run like they were back in the Mercury Interactive days, which was one of the most innovative software companies of its time. If Micro Focus develops the right strategy, they could become a dominant player in the software testing market. It is beneficial for the reader to understand the history of Quality Center since it has gone through several name changes and versions, so I have listed the chronological events below: * Mercury Interactive originally came out with TestDirector that included versions 1.52 to 8.0. * Mercury renamed the product TestDirector to Quality Center in version 8.0. * HP acquired Mercury and rebranded all Mercury products to HP. Therefore, Mercury Quality Center became HP Quality Center. * HP released version 11.00 and renamed it to HP ALM (Application Lifecycle Management). * In June 2016, HP released ALM Octane. So essentially, the tool at one time or another has had the names TestDirector, Quality Center, ALM, and ALM Octane. Essentially, with each version and name change there has been added functionality.
The project tracking is a bit complex. It takes some time to maneuver around it. It would also help if you could export some of the reports generated from it e.g. the Master Plan.