test all major types of failure, include special broken assets or customized broken json in order to trigger these results.
when error comes back on encode how are we going to display? what about when a permanent error comes back on a source file or specific encode? this should be displayed to the user.
here are the types of errors i can imagine we'll want to test for to start
corrupted source file uploaded to blog (i.e. it is transferred intact && md5s but the source file itself is fucked up (not a wav, etc))
source file does not make transit correctly (test by setting md5 to something different from file md5)
source file cannot be loaded at all (link is broken)
ffmpeg flags are incorrect and cause ffmpeg to error
items 1 (e.g. wrong mime type or file extension -- make the add album art step fail), 2, 3 but for the album art
test panel similar to encode administration page
no harm in leaving this in the finished theme
test all major types of failure, include special broken assets or customized broken json in order to trigger these results.
when error comes back on encode how are we going to display? what about when a permanent error comes back on a source file or specific encode? this should be displayed to the user.
here are the types of errors i can imagine we'll want to test for to start