Re: [SEToolkit-developer] Some project questions

[Tankersley, J. <jon...@ed...>]

=20

>-----Original Message-----
>From: Dagobert Michelsen [mailto:da...@ba...]=20
>Sent: Wednesday, January 09, 2008 2:59 AM
>To: set...@li...; Tankersley,=20
>Jon; Alex Kiernan
>Subject: Re: Some project questions
>
>Hi Jon,
>
>Von "Tankersley, Jon" <jon...@ed...> (Tue, 8 Jan=20
>2008 23:37:31 -0600):
>> How would one update the project/tasks in the project?
>
>I can either enable you for this or you can just ask me ;-)
>
>> I noticed that the mailing lists only show 2007....
>
>Yes, because there was no mail in 2008 until now.
Hmm... This was like the 4th email of the year...  I'll check again.

>
>> I've taken some snapshots of the GUI output... Not 'great' pictures,=20
>> but functional.  They are attached if you want to add=20
>them/refuse them.
>
>Good to see you picking up open issues. I enabled screenshots=20
>and added the pics you provided. However, the images must have=20
>screen dimensions between 150x150 and 640x480. Maybe some of=20
>the smaller ones need to be put in one file to fit.
>
>> I can re-save them as PNG if you'd prefer.
>
>That would be nice but its okay now too.

The sizes were 'out of the box' snapshots.... That's how they show up
when I ran them.  I'll see what I can do.

>
>> I was looking at the 'fixing the references to /opt/RICHPse'=20
>item... I=20
>> could probably work through that.
>
>That would be really great.
>
>> I've figured out what things can be readily tested for a=20
>test suite...
>> Some that are one-shot or continuous until ^C and some GUI tests.
>> I'd think a simple set of 2 'test' scripts - one for the=20
>one-shot and=20
>> one for the one-shot X11 gui.  The continuous ones can't really be=20
>> 'tested' well with a script, though with expect it could be possible=20
>> to timeout....
>
>Most continous programs issue warnings or terminate in case of=20
>an error. The test suite should be executable with 'make check'
>and should either succeed or return the faulted tests.

The continuous programs won't ever end....  It has to be killed via a
timer and a kill command.  I think the GNU test suite stuff can do that,
but I've never tried building them from scratch.  That will be fun.  And
then there are the 'monitoring' scripts.  I'm not sure how you could
build a validation test for the continuous ones or for the monitoring
scripts... As an interim having a simple test-cmdline and test-gui would
make sure the basics are working.  Until I can figure out GNU test
environment.