Overall Satisfaction with Micro Focus ALM / Quality Center
We can write our own code using vbscript to cover all our business requirements.
It is highly scalable as it supports clustering.
It is a robust tool but not Agile.
Pros
- Test Plan and Test execution
- Release Management
- Defect Management
- Requirement Management
- Workflow Management
- User management
- Site administration
Cons
- SAFe
- Agile
- Portfolio
- Negative impact on the first year of adoption where it eats most of revenue for licensing , migration, trainings, adoption, process definitions.
- Positive impact from second year where your will have good ROI
- we have migrated from other tool with $500k saved after 2 years
Some of them are listed below:
User Experience
|
|
|
|
|
|
|
The tools should have the ability to import test cases from common tools like Excel and export test results into Excel and PDF |
There is a low learning curve for end-users. The ability to quickly onboard technical and non-technical end-users quickly is great. |
The tool should have powerful search capabilities and should provide the ability to search and filter based on test case information or attributes of the test cases. |
The tool should provide the ability to search and replace text or field values and auto-replace content based on conditions. |
The tool should support Central management of test artifacts, and support for product structures for managing test artifacts. | |||||||||||||||||||||||||||||||||||||||
The tool should be able to provide support for popular Testing Methodologies including Agile, Exploratory, TDD, Black box testing, Functional testing, etc., and should support Finastra’s shift-left philosophy. | |||||||||||||||||||||||||||||||||||||||
The tool should support the ability to create and manage test cases and test steps. | |||||||||||||||||||||||||||||||||||||||
The tool should be able to segregate manual and automated tests and should be able to measure effective automation at the product level. The tool should also provide the ability to link/associate manual tests to automated tests. | |||||||||||||||||||||||||||||||||||||||
The tool should provide the ability to create test suites by associating test cases and have the ability to execute test suites as well as report on tests at the test script, test case, test suite, and product levels. | |||||||||||||||||||||||||||||||||||||||
The tool should support Test Data - Defect Link and should be able to provide complete Traceability Coverage at product and release levels. | |||||||||||||||||||||||||||||||||||||||
The tool should provide the ability to stop tests before complete execution. The tools should also have the ability to resume test execution from the point of last pause or failure. | |||||||||||||||||||||||||||||||||||||||
The tool should provide the ability to capture screenshots of successful or failed tests for documentation purposes and to capture replication steps. | |||||||||||||||||||||||||||||||||||||||
The tool should allow capturing and storing attachments at a test step or test step level. | |||||||||||||||||||||||||||||||||||||||
The tool should support parameterization for different test data. | |||||||||||||||||||||||||||||||||||||||
The tool should have versioning capability for test artifacts. | |||||||||||||||||||||||||||||||||||||||
The tool should have the ability to integrate with Mobile testing tools and should help manage test cases related to the native apps, simulators, and emulators for mobile testing. | |||||||||||||||||||||||||||||||||||||||
The tool should have the capability of creating manual template tests. | |||||||||||||||||||||||||||||||||||||||
The tool should provide history changes for all available fields. | |||||||||||||||||||||||||||||||||||||||
The tool should have the capability to save and view Favorites | |||||||||||||||||||||||||||||||||||||||
The tool should provide a shortcut key functionality for features. | |||||||||||||||||||||||||||||||||||||||
The tool should have the capability of scheduling the test suites to run. | |||||||||||||||||||||||||||||||||||||||
The tool should provide the capability of the "Check Spelling" feature while writing tests. Reporting and validation
|
Do you think OpenText ALM/Quality Center delivers good value for the price?
Yes
Are you happy with OpenText ALM/Quality Center's feature set?
Yes
Did OpenText ALM/Quality Center live up to sales and marketing promises?
Yes
Did implementation of OpenText ALM/Quality Center go as expected?
Yes
Would you buy OpenText ALM/Quality Center again?
Yes
Comments
Please log in to join the conversation