HPE Application Lifecycle Management Business Process Testing - upgrade lic

Mfg.Part: TB650AAE | CDW Part: 3528949 | UNSPSC: 43232402
Availability: In Stock
$81,691.99 Advertised Price
Advertised Price
Lease Option ($2329.04/month) Lease Price Information
Note: Leasing is available to businesses only. Leasing is not available to individuals.
Product Details
  • Upgrade license
  • 1 global concurrent user
  • upgrade from 1 site concurrent user
  • ESD (pack of 5)
View Full Product Details
Better Together
HPE Application Lifecycle Management Business Process Testing - upgrade lic
Quick View
Total Price:

Product Overview

Main Features
  • Upgrade license
  • 1 global concurrent user
  • upgrade from 1 site concurrent user
  • ESD (pack of 5)
Challenged by frequent releases and demands for shorter test cycles? Are your test maintenance costs too high? Invest in an HP Business Process Testing framework and move from serial testing to Component Based Testing: a way of creating reusable test modules that allow for changes to be made once then propagated to affected tests. Tests become more readable by modeling business processes, are easier to maintain, easier to tie to requirements, and help you quickly identify good candidates for automation.

HPE Application Lifecycle Management Business Process Testing - upgrade lic is rated 3.9 out of 5 by 32.
Rated 4 out of 5 by from You get the most value using all modules from Management to Defects. Valuable FeaturesALM: You cannot just say one feature is most important. You get the most valueusing all modules from Management to Defects. When you use the tool end-to-end, you can pull efficient project reports (especially scorecards) from theDashboard. So everything is integrated and only then you can evaluate the toolfairly. ALM is very flexible and each module can be used independently, butwhen you do that you are only using the tool as storage, not as a testmanagement tool.UFT: It became much more stable tool in terms of object recognition over theyears. It is easy to use as long as the user has basic software developmentknowledge and understands that the software automation process is not just arecord/playback.Improvements to My OrganizationALM: We currently successfully manage all testing projects due to ALM’s invaluable capabilities, which are listed below:* Built on best practices with a flexible structure, organization, and documentation for all phases of the application testing process.* Serves as a central repository for all testing assets and provides a clear foundation for the entire testing process.* Establishes seamless integration and smooth information flow from one stage of the testing process to the next.* Supports the analysis of test data and coverage statistics, to provide a clear picture of an application’s accuracy and quality at each point in its life-cycle.* Supports communication and collaboration among distributed testing teams.* Reduces time needed to create test execution summary reports.* Reduces the time needed to write and execute manual tests with HPE Sprinter tool.* Users can capture their actions automatically as steps in a formal test.UFT: We save time executing smoke and regression tests. We also use UFT to create test data.Room for ImprovementI would like to see better Reporting functionality especially more sophisticated graphs, for example Actual vs. Planned or high level progress graphs using indicators like traffic lights. I would like to see more sophisticated or flexible Dashboard views, such as editing and resizing. I use scorecards and pull them into the Project Reports using customized templates. Scorecards can only be refreshed from the Site Admin, which then test leads has to depend on the ALM Admin to refresh the reports if needed after the scheduled auto run. There should be ability to refresh scorecards (execute KPIs) from the project itself or give more frequent auto refresh option like even every 5 min. This is a really burden on the team.I would like to see Requirements mapped to test steps so we can combine multiple requirements validation in to one test case but map the verification steps to the associated requirements, so if the step fails only fails one requirement not all. When we are operating in an Agile world we do not have time to write test cases to capture one-to-one coverage. I know ALM allows many-to-many mapping but we cannot get true requirement pass/fail status if we use many-to-many option. Test configuration option kind of on the right path, but can only be use for data driven test cases, I cannot add design steps. If we can add design steps to a subset of a main test using Test Configuration option, I think we may be able to differentiate individual requirement that was failed without failing all the requirements mapped to the main test case.Use of SolutionWe have used this solution for 17 years.Stability IssuesI did not encounter any issues with stability.Scalability IssuesI did not encounter any issues with scalability.Customer Service and Technical SupportIn terms of technical support, I usually get solutions to my issues. I did not have any issues to call technical support for a long time.Initial SetupIf you follow the instruction, the setup is straightforward. It definitely requires an experience user to do the installation and setups, especially for upgrades.Other AdviceI always used ALM and UFT. However, I had training and evaluated IBM JAZZ tools.Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2018-01-24
Rated 4 out of 5 by from Enables management of all the important assets and metrics Valuable FeaturesThe overall task management. Managing all the assets and metrics.Room for ImprovementI'm not familiar with all the changes, but they definitely have to be more DevOps friendly. They have to certainly be more open source friendly. That's the world we live in, where we can cut costs away from large-scale vendor contracts and service contracts. The ability to seamlessly integrate and provide more capability for those, managing those infrastructures and solutions, is going to be critical historically.A lot of the vendor products - not just HPE or, in this case, Micro Focus, or whomever that I've dealt with over the years - were much more proprietary, much more exclusive. And what we're finding now is that the world doesn't work like that. Particularly as you move left and shift towards DevOps, application teams now don't consume from a central resource, they consume based upon decisions made internally to that application team.Ultimately, what they need is flexibility. So any vendor product needs to have that intrinsic in its fiber, to be able to adopt open source, and integrate basically into almost anything, to expand out the choices available to an application; to make the decisions that need to be made independently at the time that they need to make them.Not having looked at the latest, ALM Octane, just coming from the old world, at the time that it was necessary to implement a test management system to gather more information, metrics across different teams, different platforms, it served the purpose.Things change constantly these days. There's a lot more going on. There are a lot more integrations available. I think if we're looking at the legacy owned product, I think its kind of come and gone as far as its ability to do what you need to do in a DevOps world. Any solutions in the future - I know ALM Octane is the heir apparent to the old infrastructure - it's going to have to be more DevOps friendly. It will need to be able to enable the consumers, the application's users who ultimately become the developers, to see the value in a more organized test management practice, versus more of a kind of hidden, under the sheets unit testing.It's actually a whole trajectory of different solutions, different tests, that need to follow the pipeline for those folks. Anything that's not DevOps friendly, that's not DevOps easily consumable, to make the case for a more formal test management practice, is really going to end up by the wayside at the end of the day.Use of Solution11 years.Stability IssuesMy experience with the solution is that it has been fairly stable. What lies underneath is what creates the instability at the end of the day, the architecture that you are providing the solution on top of. I think once you figure out a viable, scalable approach to it, then the software itself, at least in my experience, has been very stable in running a test management operation.Scalability IssuesIt has met our needs. Just as long as you have the right architecture from the old days of physical server hardware to more of the newer stuff, which is VMware within datacenters - more virtualized.And certainly the next rage for everybody is moving into Cloud infrastructure. So things are becoming much more self-service. You're getting model scaling. You're getting the things that are making the system more maintainable. But from a scalability standpoint, you want to be able to scale to the needs at the time that you need them. The Cloud certainly provides that capability.Customer Service and Technical SupportI think like every company, they're changing the landscape. Support, in my experience, has been pretty good. There are always challenges based upon the routing/tier structure of who gets the issue first, how it gets routed, how it gets filtered down to the specific expertise that you need. That depends on your acumen as far as knowing your tooling, knowing your approach, what that's going to be.Somebody who is very savvy, will obviously have frustrations coming into a tier-one support desk. Who they really need to go talk to at the end of the day may be somebody, and it will vary by company, like a tier-three, real low-level, very experienced resource support tech who fixes those issues. So it's going to vary based upon the customer's competency versus how they are routed through a support desk.Other AdviceTesting is going to be testing. And the same challenges that you have in any of the different industries are going to be the challenges that you have in the ours, the insurance and financial industry, as well.You know from DevOps to Agile, to Shift Left to Cloud, to managing your test assets efficiently and effectively, industry is really not going to make a difference.I've been in a number of different sectors over the years. I've been in QA about 25 years, and having been in the natural gas industry, financials, insurance, HR systems. They are all pretty much the same challenges around testing. So I don't see a discrepancy in terms of the application you're testing. It's almost agnostic to the challenges that are innate with trying to test, within any type of development environment. Now, it just happens to be a more self-service DevOps model, where application teams make those decisions. But there's still always going to be those QA challenges.Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2017-11-24
Rated 3 out of 5 by from We​ have multiple teams across the globe where we have multiple projects set up in it. We have had some issues where the operation is not able to run tests. Valuable FeaturesIt gives me the ease of putting together the requirements, test cases, the release test schedules, and executing the test. It can generate the reports for each and every release that we need, and it's quick and easy enough to generate reports.Improvements to My OrganizationWe have multiple teams across the globe where we have multiple projects set up in ALM. One project is used by our team in Israel and our other project is used by a team in Atlanta. We have a centralized control or multiple projects going across the globe. So that's a good benefit for us.Room for ImprovementWe actually use Performance Center, too. Where what we need is: When we run any test to the Performance Center, the results are stored in ALM, too. But what happens instead, the results show a summary report in HTML or a .zip file. But if there was a way in the test lab for ALM, after running any Performance Center test, that the the results could be published in the test lab itself instead of going and opening the particular result (if it shows all the response time and whatever transactional data that we have) in the ALM lab itself, that would be beneficial for us.Also, on and off, we have had some issues with the operation itself where the operation is not able to run the test or something. We have to go back and forth with the vendor and HPE (now Micro Focus) to get this resolved.Use of SolutionFor the last 10 years.Stability IssuesFor ALM, we didn't have any specific downtime crashes, but we have had some issues with the database connection. The internal database where we put in the ALM data might crash or the database connection is lost. That's where we noticed some issues.Scalability IssuesWhatever version of ALM that we have, it is more than enough for what we have right now. In terms of scaling, I can say it will go beyond four to five years from now.Technical SupportFor any of the operators, the support is extremely useful. It's great, actually. They are always available on-time.Initial SetupIt's straightforward to operate, but you actually need to get involved with the concerning vendors when you need their support.We cannot just go download anything from online and put it. We need some support from the concerning team to make sure everything is right.Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2017-10-23
Rated 4 out of 5 by from Furnishes metrics that provide insights into the management and delivery of projects Valuable FeaturesAs a system administrator, HPE ALM can be flexibly configured so that it can accommodate a variety of defined project lifecycles and test methodologies. As a project user, HPE ALM can provide a logical approach in conducting comprehensive test planning, execution, and defect management.Improvements to My OrganizationMy organization uses HPE ALM to track the progress of testing and quality assurance efforts across projects that we are formally engaged in. The product has provided my team with metrics that provide various insights into the management and delivery of projects with respect to documented business needs.Room for ImprovementHPE ALM’s out-of-the-box reporting can be perceived as rigid and limited, to an extent. Knowledge of HPE ALM’s data model is important when setting up certain reports, and can be challenging depending on reporting requirements. Even so, these reports may not translate into appropriate insights that will provide value to a project or management team. The performance of the product may also be a concern, depending on the amount of active connections and data processing that it has to conduct at any given moment.Use of SolutionFour years.Stability IssuesHPE ALM is relatively stable, especially with more recent versions (12.5X). However, it is important to consider utilization frequency of HPE ALM at any given time and ensure that hosted application/database servers are configured to handle resource-intensive transactions to minimize performance/availability/data integrity issues. Micro Focus has published certified/supported configurations for running HPE ALM servers and client computing devices.Scalability IssuesIn general, HPE ALM has the potential to be very scalable from both a feature and usage perspective. HPE ALM has the capability to create project templates which may then be linked and applied to different projects. The solution also allows for customizations to be applied by individual project. However, an organization must exercise discipline in applying consistent processes to manage and govern any projects which use HPE ALM, to avoid data/information management problems.Technical SupportHPE’s technical support services are fair but leave a lot to be desired. An alternative to the direct HPE offering would be to pursue outside, well-known, thirrd-party professional support services that have extensive knowledge in HPE ALM and associated tools.Previous SolutionsNo, I have not used a different solution in the past.Initial SetupInitial setup of HPE ALM is relatively easy. However, it does become more complex when the product must be configured to meet company needs and compliance policies. This includes site configuration parameters, migrating existing projects from a previous version, securing access, and implementing integration to other HPE products such as HPE Performance Center. Many of these considerations are documented within the HPE ALM Installation and Upgrade Guide.Pricing, Setup Cost and LicensingIt appears that most companies choose HPE Quality Center Enterprise or HPE ALM. HPE ALM contains everything included with Quality Center Enterprise, and further adds features focused on cross-project customization, planning, and tracking.Seat and concurrent licensing models exist; the latter is recommended if a large number of different users will be utilizing the product. There is also the option of utilizing HPE ALM/Quality Center Enterprise as hosted on HPE’s SaaS platform.Other Solutions ConsideredThis product was already chosen from a historical perspective. Although some high-level research around alternative solutions (Helix/TestTrack, Microsoft) was performed, none of them seem to be as comprehensive or as well suited towards satisfying existing needs.Other AdviceHPE ALM is a relevant product that assists with test delivery, execution, and management within a project-driven environment. I would recommend others to check out the HPE ALM Help Center and product pages for additional information before making a decision.Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2017-10-09
Rated 5 out of 5 by from The most valuable features are overview, primary requirements, and test cases. Valuable Features:In ALM, the most valuable features are the overview, the primary requirements, test cases, defects, and traceability. Manual applications handle the regulations, so we must have the tracking capabilities. Even some of the core systems are not allowed to go down. It's very important that we know what we have tested and what is working and what is not working. That we can find out from ALM.Stability Issues:Stability is no problem.Initial Setup:The first time we installed it was a long, long time ago. We bought small, five license versions of Test Director from Mercury in 2007 and it has continuously grown since then. Today we have 600 users and 130 active projects. The environment gets bigger and bigger all the time.It's complicated to upgrade. For ALM, we have roughly 600 users. In ALM, we have roughly 130 active projects. So it takes a long time to upgrade. Some of the big projects are 5 GB of data. To migrate that to a new version takes maybe two or three hours, even if we have huge hardware.It's very complicated. We'd gladly like to upgrade to newer versions. We plan to use Octane, but we will not end up in a situation where we have two tools. We would like to, but we must find a smarter way to do some kind of migration. Several of the applications have regulations that we follow and we must be able to track 10 years back. We can't just throw away the data we have in there.If not upgrading ALM, probably they would like to search and would like to find something else. They really need to find a smart way to migrate some part of it. Of course, it's a totally different tool.Other Solutions Considered:We have looked at many alternatives. We have compared ALM to almost everything. We even have JIRA for smaller projects now. ALM and JIRA are two totally different products that are for two totally different needs.For example, we have an on-premises solution of ALM. You have to log into the active directory, so it's not so easy to give to someone outside the company. It's also struggling with different browsers. It's doesn’t work very well on a Mac, for example. The Mac developers and the Mac teams don't like ALM. Now it works much better on Chrome, but we're struggling there as well. They haven't been following the world with browser support. It's problematic to use ALM in Edge, for example.But with JIRA, on the other hand, you don't have any requirements. It's easy to set up. It's easy to start up and have your backlog there. But after a while, you figure out what is going on. For maintenance and for testing, you need a plugin for this, you need a plugin for that, and you need a plugin for something else. It's not so easy to get the overview or the helicopter view of it, if you compare that with ALM. But I understand why some like it and it has some kind of need. I hope we can mine that capital when we upgrade to Octane.Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2017-09-25
Rated 4 out of 5 by from ALM gives us a solution where we can keep all of our test artifacts (such as scripts, scenarios, test data, etc.) centralized. Valuable Features:It gives us a solution where we can keep everything centralized like our test scripts, test data, and our projects. It doesn't matter who is creating the project, everybody can access and execute it. Both our onsite and offshore teams working from different locations are able to benefit from this solution. That's the beauty of it.Improvements to My Organization:When we implemented this solution, we chose to virtualize, so we didn't implement any physical hardware. We're able to scale very quickly for very large projects when we need to run 5,000 user simulations. Afterwards, we can also scale down quickly. This gives us a lot of flexibility in our project executions.Room for Improvement:The web client doesn't match the quality of the rest of the features of this solution. HP needs to improve it.Deployment Issues:There are some challenges we faced during the deployment. But, we've had no major issues.Stability Issues:We've used versions 11, 12, 12.2, and now, 12.53. They've been very stable in our environment.Scalability Issues:We're able to scale up and down as needed. It has great flexibility when it comes to scaling.Initial Setup:There are challenges related to the network security during the set up. But, once you figure it out, solution is relatively easy.Implementation Team:We have done the implementation in-house.ROI:While comparing to the previous solution, this solution gave us as much as 60% cost savings.Pricing, Setup Cost and Licensing:Before you start implementing, make a solid plan and try to figure out the challenges before hand.Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2017-09-18
Rated 5 out of 5 by from This solution has improved collaboration between our test teams Valuable Features:* Templates: Allows us to standardize fields, workflows throughout hundreds of HPE ALM projects.* Customizable Events drive workflow: Saves a few seconds of time when we set default values, customizable dependent lists. When we translate this to hundreds of projects and hundreds of concurrent users, the productivity gains are immeasurable.* Traceability: Traceability from Requirement -> Test Plan -> Test Lab -> Test Runs -> Defects.* Rich sets of permission settings for different roles.* Business Views: It is easier to pull reports for novice users.* OTA, REST API: Utility for adding users and massaging data.Improvements to My Organization:It has improved collaboration between our test teams.Room for Improvement:* Client-side ActiveX with patch upgrades* Support TDD/BDD* Adding features like Kanban, project plans, resource utilization, and JIRA’s big picture.* Traceability reporting: If HPE can generate a traceability matrix - Traceability from requirement -> Test Plan -> Test Lab -> Test Runs -> Defects.* Defects aging report: A look at how long each defect is from the time it is created and how long it has remained at a particular status.* Reports to build information: Currently, HPE ALM does not support the copy and paste of test instances. *How can we duplicate a test set within a project?* How do we copy a test set from one project to another, and also copy the associated test plan along with it?* Reports on automation:* How do we capture the number of automation test cases as some automation test cases have multiple test cases in each automated test?How do we calculate the ROI of automation?How do we determine which test cases should be automated, because sometimes the effort of automation does not have a good ROI?How do we calculate the ROI of HPE Sprinter if (1) Automated Script generation is used? (2) Mirroring is used?How do we know which testcase is created using Sprinter?* Requirements coverage reports.* Cumulative trending reports for test execution and defects outstanding.* Auto-generation of test summary report.* Inbuild best practices for fields, such as root cause category.* Copy of test sets in the test lab.* Upload of test execution results.* Offline test defects to third parties and sync upon checking in.Use of Solution:We have been using the service for 18 years.Stability Issues:The solution is very stable, if you have the right person to manage it.Scalability Issues:The solution is very scalable, if you have the right person to manage it.Technical Support:The technical support has been deteriorating since the Mercury days. I would give technical support a rating of six out of 10.Previous Solutions:We were looking at other solutions, such as JIRA ( https://www.itcentralstation.com/products/jira ), due to all the issues I have raised.Initial Setup:The setup was straightforward.Pricing, Setup Cost and Licensing:HPE ALM has been sold to Micro-Focus. I am not sure if Micro-Focus ( https://www.itcentralstation.com/vendors/micro-focus ) will be flexible.If no flexibility is provided, you can easily move out in weeks, if you have the right resources.Other Solutions Considered:We evaluated Zephyr ( https://www.itcentralstation.com/products/zephyr-enterprise ), QASymphony ( https://www.itcentralstation.com/products/qtest ), XQual, Perforce ( https://www.itcentralstation.com/products/perforce ), and Rational Quality Manager.For integration purposes, we evaluated Tasktop, Orasi, HP Synchronizer, and ConnectALL ( https://www.itcentralstation.com/products/connectall ).For automation purposes, we evaluated UFT ( https://www.itcentralstation.com/products/hpe-uft-qtp ), Selenium ( https://www.itcentralstation.com/products/selenium-hq ), and Robot.Other Advice:Below is a checklist for others considering a test management solution:* CIO sponsorship* Number of projects* Number of concurrent users* Standardization needs* Ease of control and management* Access rights for individual roles* Event driven workflow customization* Extending beyond test management to TDD, BDD, test data management, test environment, and CI/CD tools.* Focus on where you want to solve each problem and identify relevant tools for each of these.* Availability of skilled resources* Hiring the right resources to manage: There are easily millions of test management users, but it is not easy to find a true-bred expert.* Keep in touch with what’s happening in the industry. You need to be focused and not swayed easily.* Know your stuff.* Support all your users and make life easier for them.* Integration with automation tools, performance tools, security tools, and Jenkins/Bamboo/Team City.* Define the test process that ties in with your test management too.l* Form a training team to constantly train users.* Open API for customization* Export of info to MS Excel.* Ease of migration.Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2017-09-11
Rated 4 out of 5 by from Customization is the most valuable feature. Other products don't have such a flexible tool. Valuable Features:Customization is the most valuable feature. I don’t see other products with such a huge and detailed customization feature.Room for Improvement:The Web UI and the Administration Page need to improve. These are not issues, but areas to improve.Web UI: In some version (I don’t remember exactly the version number, unfortunately), Web UI was introduced with limited functionalities but it was cool in my opinion. Web UI has a lot of advantages and the main advantage is that the customer doesn’t have to install a big thick client on his machine. Web UI is faster, lightweight and easy to configure compared to the on-premise installation. But for some reason, this functionality (all Web UI) was removed in the next release.Administration Page: It doesn’t have any issues. The main idea here is that it was written using old technologies and it would be great to improve/rewrite it using modern technologies. It doesn’t have an impact on the customer, it is more for developers who should support this area.Use of Solution:I have used this solution for five and a half years.Stability Issues:There were no stability issues.Scalability Issues:There were no scalability issues.Technical Support:Technical support is very good.Previous Solutions:Previously, I have used Redmine and JIRA ( https://www.itcentralstation.com/products/jira ). Switching to HPE ALM was not my decision, I changed my job.Initial Setup:The setup was straightforward.Pricing, Setup Cost and Licensing:Just want to advise to use ALM SaaS in case you don’t want to use ALM all your life. It is cheaper and provides you with all the ALM features but for some period of time. Also, you don’t need to install it manually, the entire environment is already installed.Other Advice:As an advise for developers who will develop such applications I would like to say - always try to support the area in an actual state, i.e., by using modern ideas/technologies if possible. Also, listen to the customer's needs, have flexible customization tools and do not forget about performance.Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2017-08-01
  • y_2019, m_1, d_20, h_19
  • bvseo_bulk, prod_bvrr, vn_bulk_2.0.9
  • cp_1, bvpage1
  • co_hasreviews, tv_0, tr_32
  • loc_en_US, sid_3528949, prod, sort_[SortEntry(order=SUBMISSION_TIME, direction=DESCENDING), SortEntry(order=FEATURED, direction=DESCENDING)]
  • clientName_cdw