According to CNET’s Eric Mack, “In some ways, the future that so much science fiction promised us is already here…but the decade beginning in 2020 will take us even further toward a world where far-out ideas…become topics of serious conversation.” In a previous blog post, we touched on a number of these ideas—including a cashless society, virtual vacations and implanted cell phones.
Eggplant Blog
No matter what industry you’re in, providing an exceptional digital experience to your customers is paramount. It’s particularly tricky in financial services, as more and more users ditch physical branch locations for online banking. By 2019 in the UK, mobile banking is expected to overtake desktop as the preferred channel. And for two-thirds of Americans, a recent survey found that online and mobile banking represent their primary banking channels.
Testing is critical for organizations like NASA, the US Army, Northrop Grumman, BAE Systems, Lockheed Martin, MBDA, the UK’s Ministry of Defense and the Metropolitan and Scottish Police, where lives are on the line. As we've worked with customers like these over many years, we've noticed how much more testing is than just making sure the system works — it’s about ensuring we test for mission success and continuously optimize mission outcomes. Whether you're designing systems for command and control (C2); to provide support for complex police operations, such as hostage negotiations; or for shooting down an enemy missile, you should plan your testing and monitoring strategy to continuously test against the desired mission outcomes.
Consumerization, digital experience, DevOps, mobile, fragmentation, and microservices have changed how software products are architected, how they’re produced, what they do, who uses them, and those users’ expectations. As a result, there’s been a massive shift in testing requirements, both in terms of what we’re trying to achieve and what we need to do.
Note: Back by popular demand, this is a repost of a previous blog by Antony Edwards.
SciFi worlds from the 1980s always included super powerful, intelligent computers that you could talk to. By the late 90s, the vision had moved on to worlds where everything is a computer and connected; maybe even us. And it’s this ubiquitous computing that I think is the most exciting and interesting part of technology: new device categories.
You can find 28 million apps on Google Play and 22 million in Apple’s App Store. Yet, nearly one in four people who download an app use it only once. Apps are incredibly slow under certain circumstances, don’t work in key parts of the workflow, and have less-than-optimal usability. The app scrap heap is growing because many organizations are still testing to ensure code quality, not a superior user experience (UX).
Today we are excited to bring you a guest blog post from Dr Greg Law, at Undo. TestPlant announced a technology partnership with Undo on August 17, 2016. To read more about the partnership, click here.
The rise of test-driven development, agile methodologies, continuous integration and continuous deployment are transforming how software is created and provided to customers. Simultaneously, the spread of software into more and more of the devices around us and the interconnectivity of those devices means that the sector is growing in scale, complexity and importance. These factors are having an enormous impact on testing and QA departments. If more software is being produced and needs to be deployed in shorter and shorter timeframes, traditional testing methodologies have to change, hence the rise of automation in the testing process.
eggPlant Functional v16.1 is now available! Upgrade or download it to try out the new features today.
The eggPlant Functional v16.1 release is packed with features and updates that make setup and scripting easy for enterprise test deployments. ‘What kind of good stuff is this?’ you ask. Let’s dig in to find out…
I recently presented at the Northern Lights conference in Manchester. This conference was hosted by the BCS (British Computing Society), and my talk was “Tools. Techniques. Trouble? Why test automation is getting more difficult, and what can be done about it.” You may have seen my blog post from ahead of the show, but if you haven’t yet, you can find it here.
I focussed on automating user interactions with the System under Test (SUT) and automating the creation of test scripts but not the automation of the testing process itself. I addressed both functional and load testing.
For those who weren’t there, here are the key points that I covered in my presentation: