Experience-based recommendations to test the brains that drive the devices.
In essentially every embedded system there is some sort of product testing. Typically there is a list of product-level requirements (what the product does), and a set of tests designed to make sure the product works correctly. For many products there is also a set of tests dealing with fault conditions (e.g., making sure that an overloaded power supply will correctly shed load). And many companies think this is enough, but I’ve found that such tests usually fall short in many cases.
The latest issue of LogiGear Magazine is out!
In this issue, Michael Hackett discusses the landscape of the Internet of Things (IoT) with Joe Luthy; Jon Hagar gives expert recommendations for testing the IoT; understanding new areas for traditional testers working in the IoT; Phillip Koopman suggests that those performing embedded testing have software specific test plan; Auriga’s Andrey Pronin writes about the importance of a highly organized testing process and Essensium/Mind’s Arnout Vandecappelle reminds us that team collaboration is essential for testing embedded systems.
Michael Hackett, Senior Vice President of LogiGear Corporation and Editor-in-Chief of Logigear Magazine, on change and software testing.
Change is constant. What’s different today is the rate of change. Moore’s law resulted from the observation that the rate of change in computing power is exponential. The products, services, and software landscape appears just as dynamic. At the same time, we pretty much take for granted the ubiquitous presence of software running our lives and the convenience it brings.
Michael Hackett, Senior Vice President of LogiGear Corporation and Editor-in-Chief of Logigear Magazine, weighs in on how to improve existing testing processes.
On the whole, everyone wants to do a great job, have a better work environment, happy clients and customers, and to be employed by a company earning lots of money. All great goals!
But this is not always the case. When it is not, you can suggest process improvements, better tool use, different estimating techniques, etc. Suggestions are generally evaluated based upon whether they are opinions, complaints, thoughtful, useful, possible or even mean-spirited.
A large part of my work over the past few years has been consulting on process improvement for entire software teams or specific test groups to help companies and teams achieve their goals. This all sounds great but I have to say, that achieving meaningful change is often painful!