[qmtest] resource extension classes

[J.T. Conklin]

Hi Mark, It's been a long time...

eichin at metacarta.com writes:
>> methods.  I was able to register it without problems, but it doesn't
>> show up in the Resource drop down when I try to add/edit tests.  The
>
> Do you have an "arguments" list member of your derived class?  That's
> used for the UI components, and I think you have to have it (possibly
> empty, or with computed=true values for things you're replacing...) in
> order to see it in the webui.


No, I didn't have any arguments.  I'll eventually need them, but I
thought I'd try the simplest possible extension class first before
getting more fancy.  Unfortunately, adding "arguments = []" to the
class didn't help it show up in the GUI.  In retrospect, I'm not 
surprised since the TempDirectoryResource() class that comes with
QMTest does have arguments and it doesn't show up either.

>> they could share on how resources should spawn executables on SetUp()
>> and reap them on CleanUp()?  Is there any QMTest or Python classes to
>
> If they're local, you could just stash the pid in self, and then
> kill it in CleanUp.  (I do a lot of stuff where setup ssh'es to
> another machine and runs "scriptname args start" and CleanUp just runs
> "scriptname args stop", and the script just stashes the pid on the
> System Under Test.)

Sounds good.  You wouldn't happen to have anything you can share :-)

    --jtc

-- 
J.T. Conklin