Test Planning

Take a look at the critical systems in the world today and you’ll find software. From water, power, and utilities to nuclear plants, factories, and cars, pretty much everything has become integrated with digital devices and the internet. We need to do testing from a risk-based perspective and be accountable to the public by acknowledging what is tested and what is not.

Undoubtedly, your organization has disaster plans in place for recoverable situations. But what about for going out of business? Thinking about your obligations to clients, users, customers, and partners before the worst happens can make the transition easier for everyone. Here are some people and things you should incorporate into your apocalypse plan.

Switching from a legacy system to a composite application can be tricky: The transition will require a lot of restructuring. To be sure you’re conducting the most streamlined, complete transfer possible, focus on key performance indicators. Defining KPIs can help prioritize objectives and create an efficient new workflow.

Flaky tests pass or fail unexpectedly for reasons that appear random. It can be easy to use flaky tests to discredit automated end-to-end testing, but they also can tell you things—about both the application and your team dynamic. Josh Grant gives some technical and human examples of times flaky tests helped his testing efforts.