On Monday, 24 September 2018 3:02:28 PM NZST Hussin, Mohamad Noor Alim wrote: > This patch is my supersede of earlier "manualbsp" which I split into 2 parts > called usb test and microsd test.
OK thanks. > I would use MACHINE_FEATURES = "usbhost" instead of introducing new variable > as it would eliminate problem in case someone try to execute the usb test > case without enable the "HARDWARE_TEST = 1" Sorry I don't understand - do you mean you will use it or you can't? > or download the image form public autobuilder. The test won't do anything in an image by default, only when you're running the test. In any case if the test isn't writing to the device there shouldn't be any major risk. > > Otherwise I agree with Mike's reply, we should avoid writing to the storage > > device as part of the test. > > It is mean that just do test like mount and unmount only? To read something > in storage device we need to write at first place? That's true - but you can still do a read test if you make it a precondition of the test that you write some known file to the storage device before running the test (as part of setup, just as you need to set up the board/device before running any tests - you just need to ensure this gets documented somewhere). Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
