Testing plan

[GoogleCodeExporter]

Hi,

Before each release we are used to preform some test by our own praying not
to find in the regression :) That's why we should have a testing plan, at
least to do simple checks for the most conflictive components (like the
dshow components, ffmpeg, auto{video|audio}{src|sink}, some decoders, etc...). 
We should also have a media library with the most common formats to check
that all the formats supported by the old release are also supported with
the new one. 
I think a wiki page for that should be enough

Original issue reported on code.google.com by ylatuya on 17 Mar 2010 at 9:36

[GoogleCodeExporter]

Sounds good - you're exactly right - we need something much better than my very
cursory commandline tests.

Original comment by david.g.hoyt on 17 Mar 2010 at 6:32

[GoogleCodeExporter]

You mentioned a while back that you had compiled gst w/ mingw and had the 
resulting
test scripts -- can we use those?

Original comment by david.g.hoyt on 17 Mar 2010 at 6:38

[GoogleCodeExporter]

I made a wiki page for us to begin work on this:
http://code.google.com/p/ossbuild/wiki/OfficialTestProcedures

Original comment by david.g.hoyt on 18 Mar 2010 at 11:38

[GoogleCodeExporter]

This can be a good start:
http://git.collabora.co.uk/?p=user/edward/gst-qa-system.git;a=summary

Original comment by ylatuya on 7 Apr 2010 at 8:51