Most of the time you will set constraints to ensure that only valid inputs are chosen by constrained random, but you can send in bad data as well to see if it is handled correctly. What I am more concerned about is that you don't actually test anything at all, you just create a false illusion that you are.
Perhaps I have misunderstood, but isn't there a danger with what you're suggesting that you test a design to check it does what it should, but you're not checking to see that it doesn't do what it shouldn't? I can think of a couple of things that caught us out over the years where I thought - I wonder if random testing would have spotted that?
NASA's Orion Flight Software Production Systems Manager Darrel G. Raines joins Planet Analog Editor Steve Taranovich and Embedded.com Editor Max Maxfield to talk about embedded flight software used in Orion Spacecraft, part of NASA's Mars mission. Live radio show and live chat. Get your questions ready.
Brought to you by