Software delivers so much of our day to day experience, whether we are asking for a weather update from Alexa or ordering connoisseur coffee for your home office. Making sure these exchanges and transactions perform without failure from the code up is imperative. Which is why we are excited about our partnership with Embold.
Technology has an important role to play in helping stop the spread of the Coronavirus. Here at Eggplant, we are contributing our Digital Automation Intelligence (DAI) platform to help test contact tracing applications across the globe.
The COVID-19 outbreak has had major impacts on the way business is done, and how patients are cared for. The virus has forced organizations across the globe to re-evaluate their digital transformation plans and adjust what it means for projects to be considered “critical.”
Today we announced new enhancements to Digital Automation Intelligence (DAI) designed to simplify AI-driven automation while simultaneously enabling companies to improve the quality of their digital experiences.
Say the words “User Interface,” and what comes to mind immediately to most people is a graphical interface accessed by Tablet, Laptop, or Mobile. People generally do not think about wearables, scanners at your Supermarket, medical devices, or even your Internet-enabled toaster having a User Interface, but they do.
If you ask the average CEO to rate how important digital transformation is to their business, chances are it would crack the top five—if not take the number one spot. After all, a recent Gartner survey found that IT spending will reach $3.85 trillion this year with enterprise software continuing to be the fastest-growing category.
Click. That’s the sound of a customer seeking out your competitor because your point-of-sale (POS) system didn’t deliver the experience they wanted or expected. You know that your QA teams tested the code and it worked. So, what happened?
Quality assurance (QA) used to be a compliance activity. You were releasing a product and needed to test it and stamp it “approved.” QA was about testing that the code worked. You might manually test the code. You might have even tried some automation — coding a set of test scripts that would try to capture regressions or errors that you had eradicated in the past, but which somehow crept back in. All in all, you were reasonably satisfied that you achieved a level of test coverage that met your goals. Then, you put your code into production and crossed your fingers that nothing went wrong. And if it did, you tried to fix it as quickly as humanly possible.
It used to be that software testers could test their applications on just one platform, and only have to worry about testing that the code worked.
Sometimes I feel as if I’m the Forrest Gump of quality assurance (QA). Since 1998, I’ve been through the beginning of automated integration testing and service virtualization through being a co-founder of Class I.Q. (now IBM Greenhat). I’ve been through the first phases of an automated testing center of excellence (ACOE). I’ve been there for the start of risk-based testing, and I’ve been a part of the transformation of QA from a somewhat necessary function to something that is now the core and chief concern of any company putting out quality software and apps.