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
SpiraTest
Score 8.0 out of 10
Mid-Size Companies (51-1,000 employees)
SpiraTest allows customers to manage their software testing and quality assurance activities. It provides requirements management, test management and bug-tracking functionality with integrated reporting.
$130.99
per month 3 concurrent users (minimum)
Pricing
Bugzilla
OpenText UFT One
SpiraTest
Editions & Modules
No answers on this topic
No answers on this topic
Cloud
$43.66
per month per concurrent user
Download
$423.66
per year per concurrent user
Offerings
Pricing Offerings
Bugzilla
OpenText UFT One
SpiraTest
Free Trial
No
No
Yes
Free/Freemium Version
No
No
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
Discount available for annual billing on Cloud solution. 3 concurrent user minimum. Volume concurrent user discount available.
Buzilla is easy to use and provides basic functionality to use as a bug tracking tool. If big size attachments are allowed it would have been great. Also with Bugzilla home->Test management area is improved by allowing multiple sections it would be awesome!
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.
I think SpiraTest is well suited as a test suite, but in situations where the team is already using multiple products from one particular provider, it may be better to go with that provider's test solution. This is because integrations are very important nowadays, and should be considered when picking your project management software. It should be noted that management selected SpiraTest primarily due to the low cost of the test software. I'm less familiar with other test software in the field, but if cost is an issue, you should take a look at SpiraTest.
Open source! No license fee involved, no limit to the number of licenses.
Easy to install and maintain. Installation is very easy and hardly needs any maintenance efforts, except when migrating from one version to other. Each project can have its own group of users.
Includes all the core features/fields that are needed to log a software bug/issue.
Multiple attachments are possible, supports various formats.
Good for reporting. Filtering mechanism lets you query bugs by various parameters.
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.
A clean view of test case steps, expected results and the ability to record a result for each step quickly on one page per test set. This really helps testers work through executing manual test cases.
Hierarchical structure of releases and builds, requirements, and test cases.
Can quickly build test sets and/or test runs per build/release.
Simple identification of each test case, requirement, test run, build, release, etc.
Cloud Based. I'd like to see bugzilla be cloud based. The company I currently work with made a final decision to change db's for this specific reason. Due to the frequency of travel in this company, they need access to bugzilla from differing national / international locations.
Larger File Attachments. I believe the limit of a bugzilla content upload is 4 megabytes. For many of our video'd issues, this file size is simply impractical without the additional effort exertion on video compressor applications.
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.
Basic reporting can become very verbose unless you set lots of filters and parameters.
The ability to customize some of the verbiage in the application would help bridge the gap between translating what SpiraTest's testing terminology is and the company culture uses for testing terminology.
For future projects I will look at something that is hosted in the cloud that I don't have to manage. I would also like something that has a more modern feel to allow my customers to use it as well as my employees.
This is a pretty straightforward system. You put in the bug details, a ticket is created, the team is notified. The user interface reflects this very simple and straightforward flow. It's certainly much easier than trying to track bugs with using Excel and email.
Since it is open source, it doesn't have customer service. However, the amount of information on forums is vast. If you can wade through it, you'll get what you need
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.
As promised during product selection, SpiraPlan support has always been quick and helpful. Replies almost always come back in hours (and often in an hour or two). And SpiraPlan's online tech support maintains all support conversations online so no need to look through emails to try to recall repllies.
Implementation was pretty simple. Particularly because the product cannot be customized so there is not much to do apart from getting it up and running.
We migrated away from the whole suite of Rational tools because of their massive complexity around administration and inflexibility regarding workflows. In addition, the suite was insanely expensive, and users hated the usability of the tools. We evaluated, and liked JIRA, but because the organization was looking for cost savings, we ended up going with Bugzilla and it's FOSS model so as to avoid ongoing costs.
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.
It has made the SDLC process more efficient. Bugs were logged and tracked in emails or in Excel sheets leading to slow communication and at time version issues with multiple files. Being an online tool, Bugzilla solved those issues, improved communication, instant status updates and improved efficiency.
We have used Bugzilla with a lot of federal goverment agencies (DHS, CMS, SAMHSA, CDC, HHS etc). Project Directors adn Principle Investigators were at times given access to Bugzilla which provided a snapshot of open vs closed issues.
Some groups would resist using Bugzilla with the email reminders being the main reason. Turning off or reminding them of features where we can 'control' email notification helped a lot.
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.