Re: Hotplug Test Cases or Test Procedures

[David Brownell <david-b@pacbell.net>]

Hi Rusty,

What would you want the testcases or procedures to cover?  Are there
tools, like 'cardctl eject' for cardbus/pcmcia, that interact with
hotplug events in testable ways?  Particular drivers/hardware to test,
maybe with setup scripts, or just certain core functionality?

I don't know of any particular tests, but it'd be good to have some!

It's easy enough to handle the "do modules X, Y, and Z load" parts,
maybe even use a 'cardctl' analogue to simulate card insert/eject,
and that part is driver-independent.  Stuff like setup scripts is
harder to characterize, as well as driver-specific (except for the
essentials like "did the script get run").


It's not the same, but there is some info about debugging at the sf.net
site (http://linux-hotplug.sourceforge.net/?selectedÞbug) which talks
about applying one test technique when debugging ... it could easily get
used in regression testing:

  - save events
  - play back later
  - do they produce the intended result?

I suspect a "save the events" routine should be part of the standard
hotplug toolset, it'd have more uses than just debug, test, or logging.


>>>Would this be something people would like to see in the hotplug CVS
>>>repository?

If it's really addressing the ways that user mode tools are
alerted through /sbin/hotplug and /etc/hotplug/* support,
I'd hope so!  Certainly everything that's shared with the
other hotpluggable pci busses should be there, and I agree
with you that


>>..   Or we can just put it up on the web site.
> 
> 
> Writing the procedures as html and making them accessable via the web site
> sounds like a good way to start.

Yes.  Some would need to stay that way (where people need to do
things like swap cards around), no matter how much can be automated.

Are you volunteering to maintain those pages?


>>>Maybe I could approach the LTP?
>>
>>Traditionally they have only wanted tests that they can automate, and
>>unfortunately, pci hotplug tests (and most driver tests) can't be
>>automated very easily.  But it can't hurt to try asking them :)
> 
> 
> I'll ping the LTP people to see if they are interested, but that shouldn't
> slow us down any.

See above.  Some kinds of testing _can_ be automated without
needing industrial robotics!

- Dave





-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing 
your web site with SSL, click here to get a FREE TRIAL of a Thawte 
Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel