Hi,
I'd like to perform perform some mciavi tests.
For that I'd need a .avi with known characteristics,
much like MS' clock.avi such as
- known number of frames, e.g. 12
- visibly different frames for visual control
(e.g. analog clock or digits 0-9)
- audio channel not necessary
(although the MCI can control it)
Who could like to contribute such a file?
There are already several dlls/tests/ that create .avis.
I'm wondering what makes sense.
- copy & paste useful code that creates one on the fly
(like avifil32 seems to do?)
- have it in a resource like qedit/tests/ does
(if I understand it correctly?)
- hook into one of the existing tests directories
and add some mci tests there?
- ...?
For checking status position and seeking behaviour (hint: Wine differs
from native), a file with known number of frames is best (unlike
quartz/tests/ which seems to use whatever test.avi happens to lie in
the directory, if any).
I'd like to avoid skipping tests when a file is not
present, unlike amstream/tests, quartz/tests/avisplitter
and winmm/tests/mmio
(skip => no coverage => regressions not found).
Regards,
Jörg Höhle