[gst-devel] Proposition for a media test suite

Thomas Vander Stichele thomas at apestaart.org
Mon Nov 14 05:13:46 CET 2005


> >>* shoudn't it be done in check?
> > 
> > 
> > Wouldn't it be painful to have to write everything in C ?
> Do you think its a lot? I belive its a lot of media files but not so many 
> actions.

Are you sure ? There's heaps of stuff we could be doing - random
seeking, querying of position, type detection, properties detection,
reverse playback, snapshotting, comparing to a known good reference
decode, doing statistical analysis on output, comparing different
decodings of encodings of the same file, ...

>  Is it as easy as in check to handle tests that segfault (record failure 
> and continue)?

sure - spawn a process, wait for it to finish, if it segfaulted, the
os.wait() value tells.
> >>** to avoid stumbling over stuff in the python layer
> > 
> > 
> > Well, the converse would be that it would make sure we keep the python
> > layer rock solid :)
> But that also means that when ever something fails durng thew testruns we cry 
> for you in IRC (on the other hand nothing would change as we do this anyway ;) )

There are at least three people already in the office regularly dealing
with gst-python; I would say the bindings are the best there are atm :)


Dave/Dina : future TV today ! - http://www.davedina.org/
<-*- thomas (dot) apestaart (dot) org -*->
Follow me down to the bushes dear
No one will know we'll disappear
I'll hold your hand we'll never tell
Our private little trip to hell tonight
<-*- thomas (at) apestaart (dot) org -*->
URGent, best radio on the net - 24/7 ! - http://urgent.fm/

More information about the gstreamer-devel mailing list