OpenText™ ALM/Quality Center, formerly from Micro Focus, serves as the single pane of glass for software quality management. It helps users to govern application lifecycle management activities and implement rigorous, auditable lifecycle processes.
N/A
OpenText UFT One
Score 8.0 out of 10
N/A
Unified Functional Testing (UFT, formerly known as HP UFT and before that QuickTest Professional or HP QTP) is a functional and performance testing tool acquired by Micro Focus from Hewlett-Packard Enterprise, now from OpenText.
N/A
PTC Windchill RV&S
Score 2.1 out of 10
N/A
PTC Windchill RV&S (formerly Integrity Lifecycle Manager of the Integrity suite) is an MBSE (model-based systems engineering) suite. The former Integrity suite contains an Asset Library which supports systems-of-systems approach to design (i.e. linking models into higher-level models that subsume them), a Process Director which is designed to articulate, manage and improve the design process, and a Modeler for visualizing and controlling the product design process. The Integrity suite is…
We require a project management tool for waterfall projects with very heavy testing cycles (4-5 regression cycles), definitely no other tool in the market provides the level of support for test management that HP ALM provides.
HP ALM has always been the best tool in the industry for QA management. Thoroughly trusted and used by the top-notch organization through the industry. The USP is the total coverage of Test Cycle which other tools lack.
There is a desire from some areas in the company to move to TFS and Microsoft Test Manager. The issue with the MS tool set is that they are more geared for developers rather than testers and business users, so great for Agile (assuming developers do carry out testing) but if …
For requirements, we have also reviewed Blue Print, Version One, etc. Currently, the go forward solution is being decided. Whatever the final requirements application is, integration with HP ALM will be done to support traceability.
We have other tools in our organization like Atlassian JIRA and Microsoft Team Foundation Server, which are very capable tools but very narrow in their approach and feature set and does not come even close to the some of the core capabilities of HP ALM.
We have had ALM back when it was called QC (Quality Center) and this was before my time, so I cannot say why it was chosen over other applications. I do know that it has been our defacto standard for many years now and all users of the program are very happy with it.
We need to look at open source tools if the team has time to learn like Selenium.
Selenium can integrate with just about anything to give you a robust framework such as Maven for source code compilation, Test NG to drive tests, Jenkins or Hudson to integrate into a Continuous …
UFT has the advantages of supporting different types of technologies. Different competitive tools were not able to support the wide range of technologies which UFT does. UFT has a strong history and has been ranked one among all the Test Automation tools for quite some time. …
The only real competitor is Selenium but the simple ease and advanced features of UFT won out during the selection process. Also the ability to test against non-web based applications can come in handy.
Most of the test tools are similar in nature to what they do. Every tool has its own quirks, making them necessary to understand how and what they do, before we get to start using them; which also happens to be the key to good automation testing. Considering the HP toolset, …
HP UFT is an excellent tool for test automation; very flexible and powerful. It is much more intuitive than and easier to use than Selenium, however, the only downside when compared side by side with freelance tools like Selenium is the pricing. Selenium can be acquired for …
For an organisation that has completely adopted SAFe structure including naming terminology, it is less appropriate and apart from that. It can suit any organisation out there, and it can solve all your problems one way or another by customising it. It is a robust and highly scalable solution to support all the business needs. It improves a lot of productivity and visibility.
UFT is well suited if the price is not an issue, and if the requirement is about testing different technologies. If the application is based on Legacy platforms like Siebel or Mainframe, UFT fares quite well. For low cost web-based projects, there are other cheap and open source tools available. If it is about API testing or Mobile Testing, it is better to use other tools like TOSCA.
PTC Integrity is an excellent source code management and version control tool, and I would suggest anyone to use it for that purpose. We can even define our workflows using individual forms for implementing Change Management, Defect Management and Access management requests. If properly used, this tool is great for managing our code for very long periods, considering my 4-5 years of usage. Though the UI could be better, and integration with some application servers could be better implemented, this tool is a good tool.
If you have a mix of automation & manual test suites, HPALM is the best tool to manage that. It definitely integrates very well with HP automation tools like HP Unified Functional Testing and HP LoadRunner. Automated Suites can be executed, reports can be maintained automatically. It also classifies which test suites are manual & which are automated & managers can see the progress happening in moving from manual to automated suites. In HPA ALM all the functional test suites, performance test suites, security suites can be defined, managed & tracked in one place.
It is a wonderful tool for test management. Whether you want to create test cases, or import it, from execution to snapshot capturing, it supports all activities very well. The linking of defects to test runs is excellent. Any changes in mandatory fields or status of the defect triggers an e-mail and sent automatically to the user that the defect is assigned to.
It also supports devops implementation by interacting with development tool sets such as Jenkins & GIT. It also bring in team collaboration by supporting collaboration tools like Slack and Hubot.
This tool can integrate to any environment, any source control management tool bringing in changes and creates that trace-ability and links between source control changes to requirements to tests across the sdlc life-cycle.
The simple front end will allow novice users to easily grasp the basics of automation and give them confidence to try things for themselves.
UFT can scale up and run across multiple machines from a single controller, such as ALM, enabling hundreds of tests to be executed overnight.
There is an active support community out there, both official HPE based and independent users. This means if you do encounter a problem there is always someone out there to help you.
The later versions have many add-ins to plug in to other tools within the QA world.
Expert users are able to utilise the many native functions and also build their own to get the most out of the tool and impress people as they walk past and see the magic happening on the screen.
UFT also has LeanFT bundled with it, allowing automated testing at the api level - if you can convince the developers to let you in there.
The requirements module is not as user friendly as other applications, such as Blue Bird. Managing requirements is usually done in another tool. However, having the requirements in ALM is important to ensure traceability to tests and defects.
Reporting across multiple ALM repositories is not supported within the tool. Only graphs are included within ALM functionality. Due to size considerations, one or two projects is not a good solution. Alternatively, we have started leveraging the template functionality within ALM and are integrating with a third party reporting tool to work around this issue.
NET (not Octane) requires a package for deployment to machines without administrative rights. Every time there is a change, a new package must be created, which increases the time to deploy. It also forces us to wait until multiple patches have been provided before updating production.
Its licensing cost is very high making it a very expensive tool. due to this many organisations are exploring options of license free tools like Selenium for automation. Though learning curve is large in case of Selenium but it is very cost effective & you an get lot of support online for Selenium.
Though the scripting time is less since its easy to create automation scripts, the execution time is relatively higher as it takes the lot of CPU & RAM.
Though UFT is quite stable but during long execution cycles we do get frequent browser crashing issues.
In terms of costing TestComplete is also one option which is not free but comes with modular pricing. You can buy what you need, when you need.
It can be overwhelming with the number of tabs, functions and ways to achieve the same result. The average user may struggle with learning the tool.
The text editing in Integrity is weak and does not provide many options. Because of this, many user decide to use MS word instead, to document requirements.
I do not make decisions on what tool my company uses. I am just the user of the tool and such decisions are not handled by me. If I were to make such decisions, I would definitely renew MKS, considering the amount of data we have stored in MKS and the current number of users who are familiar with the system
Because it lets me track the test cases with detailed scenarios and is clearly separated in folders. Also the defect filter helps me filter only the ones that have been assigned to a particular area of interest. The availability of reports lets me see the essentials fields which I might be missing the data on and helps me to work on these instead of having to go through everything.
PTC Integrity comparatively could be considered a nice Source code management, Version controlling tool and could be compared with tools like StarTeam. If the integration to move/migrate code could be integrated into this tool, it would become an extremely powerful tool.
It is a great tool, however, it got this rating because there is a lot of learning that takes a lot longer than other tools. There are no mobile versions of ALM even with just a project summary view. I believe ALM is well capable of integration with other analytics tools that can help business solutions prediction based on current and past project data. This is Data held in ALM but with no other use apart from human reading and project progress. ALM looks like a steady platform that I believe can handle more dynamic functionality. You could add an internal communication platform that is not a third party. Limit that communication tool to specific project members.
HPE are quick to reply and it's possible to get through to the actual developers shuold the case warrent it. Their online system allows updates and tracking of all incedents raised.
PTC Integrity administration can be somewhat daunting. They have been able to help with every question that I have submitted. Their support website is very easy to understand and submit questions and their phone support is wonderful
We have other tools in our organization like Atlassian JIRA and Microsoft Team Foundation Server, which are very capable tools but very narrow in their approach and feature set and does not come even close to the some of the core capabilities of HP ALM. HP ALM is the "System of Record" in our organization. It gives visibility for an artifact throughout the delivery chain, which cut downs unnecessary bottlenecks and noise during releases.
1. It works solid for automate SAP and S/4 Hana applications and Fiori too. 2. Teams are well versed about UFT One 3. Able to handle maintained execution results 4. Publish Automation execution results in well manner to the leadership team/stake holders 5. More help content available 6. Able to understand non technical resources about normal view.
I think the reason that PTC Integrity was initially chosen is that it was the best product available in the mix at the time. This coupled with the PTC deal on multiple products was a no brainer based on the size and scope of potential users.
Reduces the total workload of keeping the team to test older (regression) functionality. QA testers can concentrate on ad-hoc and exploratory testing, saving time and effort across the entire project.
Has built a better infrastructure for the client applications on which we can rely on for stability and providing regression results for any new features being developed.
Led the applications a step closer to implementing agile practices and DevOps across the entire organization. Thus, providing a better turnaround time of new features to the customers and less maintenance headaches for the BAU team to address.
MKS Integrity has proved to be particularly useful in the software development process by increasing employee effieciency
MKS integrity has also made software development a very efficient process and makes feature releases and bug fixing a lot easier
In addition to the above, our organization has been able to support manufacturing easily by reverting to a previous software version in case of an emergency.
It has also led to faster time to market for new products.