Bring Me Tests

People often ask me how they can help with this whole FATE effort. There is one very clear item I could use help on: More tests. You can help me fill in the holes in FATE’s test coverage. For those who are interested:

  • Check over the FATE Test Coverage wiki page
  • Find red boxes
  • Think of a method involving the ‘ffmpeg’ command line tool that exercise the feature in that box, something along the lines of “ffmpeg -i sample.file -f framecrc -“, and preferably something that is expected to be bit-exact across platforms
  • Tell me about the test, and where to locate the relevant sample file

My ad-hoc — but not hard and fast — rule about FATE suite samples is that I try to keep them under 2 MB. Exceptions can be made, but I often carve up samples manually, either with dd, or by remuxing, or using both methods.

If you have any concrete test spec ideas, please let me know, either through the comments or through email (on the sidebar). Remember, bit-exact tests are necessary at this point, although I hope to have a workable idea for testing non-bit-exact formats soon.

5 thoughts on “Bring Me Tests

  1. Multimedia Mike Post author

    Thanks for reminding me that I still need to update fate-client.py. fate-script.py (which is the main test mechanism I use, and which still hasn’t been released) has been updated. Then again, I am planning to obsolete fate-client.py and just maintain fate-script.py. Uninspired names, I know.

  2. Multimedia Mike Post author

    I have plans for testing VC-1 per the formal conformance suite. But I wonder, how much overlap is between WMV3 and VC-1? If I thoroughly test VC-1, can we consider WMV3 tested?

Comments are closed.