Just about every organization goes through times when the internal team cannot execute a testing project fast enough. Reasons range from the magnitude of the project, to lack of an effective test strategy, to staff positions going unfilled. The speed of Agile development and rapid delivery of product also increases testing technical debt.
Anytime you would like to create a fierce debate in the Agile community, then just bring up a topic related to distributed way of working and outsourcing. Out of all the possible controversial topics, my favourite one is around “offshored testing”.
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.