Most organizations understand that test automation is essential for modern application delivery processes. They’re just not sure how to make it a reality in an enterprise environment without exorbitant overhead and massive disruption. Enterprise organizations typically achieve small victories, but the process ultimately decays due to challenges in five main areas. Understanding these challenges will help us overcome them.
Testing continuous technological change can seem like chaos. There are many challenges that need to be managed, such as unavailability of power, excessive temperature, incorrect configuration, unexpected behavior of services, network downtime, and processing slowdown in production. By deliberately engineering chaos, we’ll be able to discover many of our systems’ weaknesses before our users do.
With the traditional waterfall method of testing, achieving quality and faster time to market is difficult. Agile testing has emerged as an alternative, where development and testing take place simultaneously instead of operating in their respective silos. Let’s look at what it means to perform agile testing, what practices are necessary, and how agile testing can benefit your software releases.
There is a lot of interest in organizations around a transformation to agility. However, the focus is usually on agile development, so it may not be clear how software testing is done in agile. If you're responsible for leading your testing teams, don't let them be left behind. Here’s how you can make testers part of the transformation, too—step by step, because this is agile, after all.
The internet of things (IoT) continues to proliferate as connected smart devices become critical for individuals and businesses. Even with test automation, performing comprehensive testing can be quite a challenge.
Because enterprise applications are highly interconnected, development in stages puts a strain on the implementation and execution of automated testing. Service virtualization can be introduced to validate work in progress while reducing the dependencies on components and third-party technologies still under development.
Greg Paskal, evangelist in testing sciences and lead author for RealWorldTestAutomation.com, chats with TechWell community manager Owen Gotimer about testing as a craft, choosing the right test automation tools, and current testing trends around the world.
Talia Nassi, developer advocate at Split Software, chats with TechWell community manager Owen Gotimer about the fears, myths, and benefits of testing in production and how to get your stakeholders on board. Continue the conversation with Talia (@Talia Nassi) and Owen (@owen) on the TechWell Hub (hub.techwell.com)!
Melissa Benua, director of engineering at mParticle, chats with TechWell community manager Owen Gotimer about the importance of whole team quality, how to get started using the test pyramid, and how developers can start writing testable code.
Jeremias Rößler, founder of ReTest, discusses his company’s open source re-check tool, how customer input was vital to the tool’s development, and shares insight on growing a start-up. Jeremias also provides resources for learning about AI that can guide you on how to apply AI into your testing strategy.
Most modern testing, especially in a DevOps model, uses a lot of telemetry to evaluate and monitor quality of experience for apps and services. In this interconnected world, there is power and risk in data. Ken Johnston will share his personal experiences dealing with US and European Union privacy regulations and the methods he and his team have implemented to mitigate the potential of significant penalties for the misuse of data. He will cover privacy-preserving techniques such as differential privacy and private enclave, what constitutes primary versus secondary uses of data, and how you should handle personally identifiable information (PII). You'll leave with a better understanding of how to keep data private and secured, as well as how to keep your team adhering to privacy best practices and regulations.
Serverless cloud applications are rapidly moving into the mainstream. In this model, teams focus on developing and deploying code on a known technology stack and runtime, with fixed interfaces for application, database, and network.