Reviews (1-14 of 14)
- ALM/QC has a very useful function of sending an email directly to an assignee when they are selected. This is a time-saver so that you don't have to follow up with your own email every time you assign a ticket.
- Tracking the history of changes made whenever someone modifies a ticket is a big plus for ALM/QC.
- Ease in attaching items and linking tickets to other tickets allows for quick UI navigation.
- Licensing behind ALM/QC can pose a problem if many users will be accessing it. If an IT project is occurring, and many testers, analysts, developers, architects, PMs, etc. are using ALM/QC, there exists a problem in too many users being in the environment at once and causing active users to be kicked out. Having many licenses will alleviate this issue, but the trade-off is expense.
- One of the great features of ALM/QC is that it sends emails. However, when this doesn't occur, and you assume that it does, it can be frustrating, as the assignee of a ticket will have no way of knowing something is assigned to them (or at least won't know in a timely manner, until they manually check themselves).
- UI and navigation layout seems dated, as if it is a late 90s product. Many similar looking fields can be confusing to users and cause them to miss something because they are not able to discern.
- Well-structured folder system for all projects.
- Easy to import data from Excel files.
- There is room for integration improvement with other tracking tools.
- Automate Backlog/Project items notification to all team members.
We are using this tool for managing projects working with waterfall methodology, HP ALM is sued to store requirements, estimates, test scenario creation, management, execution, reporting & tracking project status. Its rich reports & dashboard help in keeping the transparency & helps higher management in taking decisions.
For agile teams where JIRA is being used, we also use HP ALM for test management. The model is requirements, tasking and tracking in JIRA while test cases, creation, execution, snapshot capturing in HP ALM. Definitely trace-ability is an issue with this kind of model where two tools are used & add up to some waste. It is used at program level.
- 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.
- It has a very rich UI interface & is indeed a very simple tool but few minor issues like not opening another window , not allowing copy paste repetitive Dev-QA tasks makes things difficult for users.
- Though with new version Octane they try to incorporate new features & integrations supporting agile principles & practices but still many things are missing making it excellent tool for waterfall projects but not for handling agile teams.
- You can not run scrum meetings with distributed teams like you can do in AgileCraft. Also support for retrospectives is not up to the mark.
- It is highly dependent on internet explorer.Support for other browsers like chrome and Firefox is not there.
- Defect/Bug management.
- Traceability with requirements, test cases and defects
- Defect linking
- It's very slow sometimes. There is improvement required in this context.
- Excel reports are not easy to create. Earlier versions were better at this.
- Only compatible with IE
- Allow organization and separation of various projects into specific work areas with specific users
- Provides sufficient reporting on the state of project defects
- Allows linking to other defects within ALM
- Provided for easy inclusion of attachments to a defect
- The user interface is very basic an unappealing
- The is limited or no ability for an end-user to create a custom view of a defect to display only the desired information
- The login cannot be easily linked to Active Directory requiring the creation and maintenance of application-specific user accounts
We are using ALM as our bug lifecycle management tool. The major benefit of this tool is its ability to integrate with HP's other testing tools which makes it a perfect automated testing framework.
- Simplicity and broader ways to integrate other project management tools with it. The tool has a good GUI and better test data management mechanism
- Notification mechanism and reporting features are also competitive
- ALM only works well with Internet Explorer, and because of that it inherits all the performance issues from IE
- It's very slow sometimes. There is improvement required in this context.
- Initial learning curve is a bit steep due to digital signs.
Good for life-cycle for identifying bugs, assigning to responsible teams and getting to a resolution.
Reports needs some work but they are manageable.
- The traceability between tests and defects allows testers to create defects directly from the test case, including the detailed steps to recreate the defect for the developers. Upon fixing the issue and deploying, testers can rerun the appropriate tests.
- Being able to test across multiple environments ensures that visibility into issues, developing regression scripts and other repeatable actions are available for different teams, reducing duplication of effort.
- Integration with testing tools such as Selenium, Unified Functional Test, etc. allows for development of automated regression suites to assist in maintaining clean code as it moves through the development lifecycle, especially on mature applications.
- 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.
- Requirement analysis as a stepping stone of Test Case creation.
- Test Case creation to execution and corresponding logging and artifacts uploading.
- Defect/Bug management.
- Complete Test Cycle/Management coverage.
- Should have features that will help organization to implement new methods of Software lifecycle like Agile or DevOps.
- Features of Risk Based Testing should be more enhanced.
- Should of built-in features of version management.
- Defect Management and Reporting
- Test Management and Reporting
- Traceability with requirements, test cases and defects
- Custom reports
- Excel report are not easier to create. Earlier versions were better at this.
- Cloning a defect and editing will not save the data if we move to another defect in between editing.
- Sprinter integration can be improved.
HPE ALM, previously Quality Centre, is the main building block for our professional testing QA team. It allows us full traceability of the requirements, tests and bugs to make an informed decision as to the quality of the code. We have customised it to restrict access to different modules or restrict permission within the modules according to the business requirements.
The traditional QA engineers/testers use it to help audit the testing process and guide business users for any testing they are involved in. The developers can update the bugs raised and follow the test steps themselves to investigate issues. Reports generated using the inbuilt functionality can be sent out to the project team on a daily basis.
- The whole end to end QA lifecycle can be covered and mapped, allowing a single view source of the quality of the application under test.
- There are multiple add-ins that can be used to enhance the reach of the application.
- The workflow is easy to customise in order to hide fields or restrict permissions within modules.
- Native reports and graphs allow simple exporting and time saving when reporting to the project team.
- The tool isn't cheap, but then again neither is something like a Ferrari or other high quality item.
- The current guise of ALM does not lend itself to Agile, although this is being rectified with the HPE Octane delivery.
- The underlying code is old and can sometimes slow down IE, but again Octane should fix it.
- Defect management. It does a fantastic job of being able to manage the lifecycle of a defect.
- Automated testing. We use ALM in conjunction with QTP and UFT for automated tests.
- Some of the administrative functions could be better laid out. For example, you can add users to a project from within the project, but it doesn't always "take" and you have to go back to the main admin screen to add them.
- If something goes wrong with the program, it is a decent amount of work (possibly even blowing away the entire user account on the computer) in order to get it back in a working order again. This is mainly because this is a full fledged application inside of a web browser.
HP ALM is the only comprehensive enterprise grade ALM solution in marketplace today to scale the challenges faces by small to large enterprises with local and global teams. It provides necessary framework to small teams to quickly establish themselves on the process ladder and at the time provides the governance framework to large teams, who already have the established maturity scale.
The solution can be used out of the box for its core capabilities like Release & Cycle planning, Requirements Management, Test Management and Defects management or can be highly customized to fit to an organization SOP. It's tentacles reaches beyond the core capabilities and can be extended to PPM solution and other development and DevOps tools within and outside the organization. HP ALM is very intuitive and very easy to navigate. It is a very mature product and brings the rigor you need in your organization to surpass the development and quality challenges.
- Release & Cycle Planning - Whether it is a new release or managing change requests, HP ALM can handle it all. In one click you can generate the status of a particular release from scoped requirements to test executed and everything in between. It also have KPI functionality which cane generate health indicators for each release to make go and no go indicators. The baseline features is a well thought out feature which is often neglected in many organization.
- Requirements Management - HP ALM provides all the features which are needed by robust requirements management professionals. Teams can easily create and update the requirements and provide the full visibility to the team downstream. The tractability and impact analysis feature is the greatest suite of HP ALM complemented with great reporting and graphs.
- Test Management - This is strongest module of HP ALM and provides the maximum values to team using HP ALM. Teams can perform manual, automated, performance and mobile testing with HP ALM. WIth HP UFT, teams can easily execute automated test case within ALM and report the results back. It also integrates with HP Mobile Center and test can be executed within HP ALM.
- Defect Management - Simple and Strong are the two words to describes HP ALM defect module capability. Team can use it out of the box or customize it using workflow scripts to accommodate any process flow a organization may have. Their tons of features within this module which helps in expediting your release cycle and help you market the release faster.
- Dashboard & Reports - HP has made numerous improvements to this module since I have known this product. You can generate any report or metrics if the data is present in ALM. Their are many after market solutions which can extend ALM data beyond the out of box reporting capabilities.
- HP ALM is little late in adopting the Agile methodology but with the new HP ALM Octane products, organization can easily manage teams and projects which follows that methodology. I would like HP to make an effort to gel this two products capabilities in one product in future.
- HP ALM shall invest some more resources in making HP ALM Synchronizer product more robust. HP ALM Synchronizer is a very good tool to synchronize data e.g. Requirements and Defects between HP ALM and other endpoints like Team Foundation Server and JIRA.
- HP ALL is still hard to implement if you want to build a true DevOps team. This feature definitely need some improvements for "non-product" oriented organization to adapt it.
The HP ALM licenses may be cost prohibitive to some organization with small budget and small teams.
HP ALM is a single repository that can be accessed universally by project team members through a browser, where you can upload your project requirements, then add your test cases and link the requirement to those test cases and then execute and track the test execution and log and track defects all on the same application.
- Keep track of project requirements and review requirement coverage and fulfillment with relation to test cases executed. In HP ALM you can easily review the project requirements and assess the current status by looking at passed and failed requirements based on the execution results of the test cases linked to these requirements.
- Execute test cases and keep track of the execution - HP ALM can track both Manual and Automated tests (with the help of HP UFT). Test cases can be easily organized and assigned to testers, then the actual test execution can be tracked in HP ALM where testers will pass or fail individual and detailed steps of the test cases in HP ALM. From here you can generate real time reports on test execution, on testers, or on tests executed by day etc.
- Create and track defects - HP ALM will let you log defects found in software applications for a specific project, or test phase, add the detail (even screenshots) using its own screenshot tools and assign these defects to the developers which in turn can provide feedback and status resolution that will notify the tester whenever a defect has been modified or fixed in order to be re-executed until the defect reaches the final closed status. All history is kept in HP ALM.
- While very useful, HP ALM is an expensive tool, price for licensing is one of the main reasons clients tend to refrain from user HP ALM
- While HP ALM has a native connectivity with HP UFT for test automation, integrating other tools with HP ALM though possible is not as straight forward as could be, HP ALM could make connections to it easier for third party applications.
- Some browsers are better prepared to work with HP ALM, if some of the plugins that are loaded at the first tme login fail to load, the 'recipe' to bypass this error and make it load can be difficult and sometimes some security settings in the network need to be set for ALM to work
SO Requirements will be then covered by test cases and depending on the execution result of the test, the requirement will show as Green or Passed or Red meaning Failed, this is a great feature to quickly review the project requirement readiness in real time during the testing phase.
Micro Focus Application Lifecycle Management / Quality Center (ALM/QC) Scorecard Summary
About Micro Focus Application Lifecycle Management / Quality Center (ALM/QC)
Micro Focus Application Lifecycle Management / Quality Center (ALM/QC) Technical Details