Industry analysts such as Gartner are currently focused on driving quality to the ‘left’ towards the developers who create the bugs in the first place. In concept we agree aside from a tiny flaw. Businesses largely buy or consume COTS applications such as SAP. They don’t ‘own’ the developers so they can’t shift left but they still need help.
When you’ve been given a large application comprising 100,000s lines of code to test, why on earth would you want to write another code base to test it? Coded automation is slow to create, only tests skin-deep and is almost impossible to maintain, so why do it?
Anyone who believes that 100% of testing can be automated needs their head examined. Manual testing will always be with us but why does it have to so manual? Our breakthrough technology is proven to reduce defect reporting times by 70%.
Coded test automation doesn’t only limit its users to those with programming skills, it equally requires that you have an in-depth understanding of the technology that was used to create the application under test. If you want to select a cell in table you need to know the syntax to ‘talk’ to it. Sounds difficult and a bit crazy? We completely agree.
The information you need to determine your progress towards a release date may be scattered across numerous applications and manual systems. Collating that data takes time, numerous meetings and often a reconciliation effort. There has to be an easier way and there is.
Test data needs tender loving care and under pressure QA teams can’t afford to wait for their turn in the DBA queue. Extract, transform, warp and protect one of your most important test assets and without a line of SQL in sight.
We have always offered capabilities for the IBM i that went deeper than any other platform and addressed the particular demands of this server and its operating system. In i400Quality we now have a platform where we can explore these capabilities in the detail that they deserve.