Hi,
> You know how it is with testing - we have to be pragmatic above all. > So yes, we should include some more Flickernoise actions in our test > program, but not to replace the dedicated testing software, but to > add to it. The dedicated test software can do tests that would not > be possible in Flickernoise, and Flickernoise can give us confidence > that we have tested what our users will do once they take the product > out of the box... > Being pragmatic on discovering potential unkown bugs is good attitude. Since the productive test program was proposed precautionly to test/probe those failures made by faults while manufacturing. It can be improved whenever. So yes, we'd just work out the most criteria with e.g. Filckernoise or else to have a full basic IOs test and functional test. > > On RC3, Xiangfu will be the main person to provide all testing related > documentation, binaries, etc. Of course Sebastien will help in the > background as needed, if we run into difficult technical problems. > > That's the plan at least - what do you think? > It's surely good that binaries, mcs files for MAC address, etc. We'd better to have a go through steps/discussions in adavance before rc3. Like in IRC first. - Adam
_______________________________________________ http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org IRC: #milkymist@Freenode Twitter: www.twitter.com/milkymistvj Ideas? http://milkymist.uservoice.com
