Today is an exciting day for the Eggplant Family. Professionals, Teachers, and Students, all of us Software Users, gather together in Philadelphia at the inaugural Eggplanet US conference. People working in Government, Banking, Healthcare, Retail, and Higher Education will share stories, best practices, and experiences. Everyone teaching, listening, and learning in pursuit of a central goal: to rid the world of bad software.
Eggplant Blog
Over the next four years, Gartner predicts that 25 percent of employees will use voice to interact with applications in the workplace—up from less than 2 percent in 2019.
Automated Testing is a requirement if your organization is going to do DevOps at scale. Testing is too vast and complex to be done by humans without support.
There is always a fine line between managing the costs of an Automated Testing Team and ensuring that the organization is seeing a return on its investment. Automated Testing, regardless of if you are using a licensed or open-source testing tool, has hidden costs. The license costs are just the most obvious.
In late July, news broke that researchers at Armis Labs had identified numerous vulnerabilities in an operating system known as VxWorks, leaving approximately 200 million devices vulnerable. Unfamiliar with VxWorks? You’re not alone—as Ben Seri, VP of research at Armis put it, “VxWorks is the most widely used operating system you may have never heard of.”
A recent article by InformationWeek’s Jessica Davis proclaimed, “RPA is the fastest growing category of software today, driven by enterprise digital transformation efforts.” Davis went on to cite a Gartner report which found RPA has year-over-year growth of 63 percent, which it attributes to “an expensive patchwork quilt of applications and systems” that companies are struggling to manage.
It’s a digital world and changing consumer and user demands necessitate that websites, apps and programs deliver an experience that delights users. Those companies that can’t deliver on these expectations risk poor customer satisfaction scores, low adoption rates, negative brand perception and loss of revenue. These factors are giving rise to a new phenomenon in software testing which we’ve termed “continuous everything,” comprised of three essential areas—continuous quality, continuous delivery and continuous feedback.
On June 18, many Google Calendar users worldwide got an unexpected surprise when logging into the app—an error message. The issue was resolved approximately three hours later but, as anyone who lives and dies by their calendar knows, three hours is plenty of time to wreak scheduling havoc. The same day, restaurant chain Taco Bell also made headlines for tech issues, when heavy traffic in response to its free Taco giveaway caused the app to crash.
In a recent article in the Enterprisers Project, Kevin Casey wrote, “If it’s repetitive and manual, it’s probably a good fit for RPA.”
Lack of communication is often cited as the biggest problem Business have when implementing DevOps. This would be communication between co-located teams where the team just doesn’t talk, teams across geographies where time zones come into play, even where the IT and Business just will not discuss things. Indeed, there are many places where a lack of communication can cause DevOps to fail.