Software Quality Matters Blog
Upgrading and patching ERP style applications is hard work. Thats why we have produced the latest in our popular series of Best Practice wall posters designed for those using multiple or bespoke platforms.
From preparation via the blueprint and realization stages to go-live it’s full of practical hints on how to manage this process and reduce your testing effort by up to 75%.
The value of Micro Focus has dropped by more than 55% triggered by the announcement that revenues were forecast to fall between 6% and 9%. The perceived wisdom is that this was due to the difficulties in integrating the $6.6bn purchase of HP’s software business and the fact that Micro Focus is poorly positioned to take advantage of emerging trends such as AI. However there are other factors in play.
As a former Quality Center user I am not surprised at the high level of frustration with its poor functionality particularly reporting, customisations and integrations. Things have moved on and in the 21st century there is a modern alternative.
Nor am I surprised that some unenlightened users are content with QC/ALM’s limited offering.
2017 was the year HP themselves moved on from QC/ALM through their disposal of this business to the British company, Micro Focus. These venerable products have only evolved slowly but they have been re-branded many times and you may know them as Quality Center, Test Director and QTP.
Many companies have struggled with HP’s code-centric approach to test automation and UFT/QTP is typically either on a shelf or absorbs a disproportionate amount of effort to keep it working as their applications were enhanced.
We surveyed HP QC/ALM (now Micro Focus) users over the Christmas period and having consolidated the results are pleased to make them available to all those interested.
The responses indicate a high level of frustration with the product that has been around since the 1980s and also, that many users are looking for a modern, more functional alternative.
Download the full infographic here
Get the full side-by-side comparison with a more in-depth, technical evaluation here
Last month I was in Denmark at a leading European carpet manufacturer to train and consult on Qualify, our application quality management solution and TestDrive, our 100% code-free test automation product.
Their business systems are a mix of Infor M3 heavily customised to provide integrations with multiple legacy systems. This presented no problem as both Qualify and TestDrive are technology neutral and can run over almost any application whether client based or in the cloud.
Why is Manual Testing so manual? It doesn’t matter who does it, manual testing is amazingly inefficient
When a developer is assigned to rectify the bug, they cannot reproduce it. Is the reason environmental?
Manual testing is intrinsically flawed, primarily because one test cycle is almost never enough. Manual testing is performed by humans and humans have a finite capacity for repetition. When an application is first delivered, the test team will commence their efforts, but after a while will reach a point in their use cases where they can go no further until the bugs discovered to date have been rectified.
Application software has always contained bugs and will continue to contain bugs for as long as developers exist. So, from the moment that the first application program was run by Tom Kilburn on 21st June 1948 (to calculate the highest factor of a large binary number) the necessity to test developed programs to ensure they work as required has been accepted.
So, for almost 70 years a significant piece of human endeavor has been testing and some of it has been fundamental to some of humanity’s greatest achievements.
This is probably not the perfect analogy, because at some point you will have to stop and change the tyre. But it may be if you don’t do it quickly, there will be a much nastier outcome and expense.
However, looking at the things that can bring benefit with minimal effort, it is possible to make progressive incremental changes which buy you time from the outset and start you on the journey to greater savings. If the majority of your testing is currently manual, then adopting in the first instance technology that makes this less manual (less effort) is an easy and quick win