GSOC - Test suite #12

New Issue

claunia · 2026-01-29T16:32:56Z

claunia commented

2026-01-29 16:32:56 +00:00

Originally created by @cfsmp3 on GitHub (Apr 10, 2014).

Originally assigned to: @canihavesomecoffee on GitHub.

We have a reasonably decent collection of samples of all kinds, from a number of sources. Often, fixing a problem that appears in just one sample breaks something else. We need to automatize tests so we can easily compare the output of different CCExtractor versions and get a useful reports (which files changed and what).

Originally created by @cfsmp3 on GitHub (Apr 10, 2014). Originally assigned to: @canihavesomecoffee on GitHub. We have a reasonably decent collection of samples of all kinds, from a number of sources. Often, fixing a problem that appears in just one sample breaks something else. We need to automatize tests so we can easily compare the output of different CCExtractor versions and get a useful reports (which files changed and what).

claunia added the enhancement label 2026-01-29 16:32:56 +00:00

claunia closed this issue

2026-01-29 16:32:56 +00:00

claunia commented

2026-01-29 16:32:57 +00:00

@cfsmp3 commented on GitHub (Apr 10, 2014):

Important goals:

Obviously, keep track of results :-)
Keep in mind that for each input file there will be different output files, and that at least for now CCExtractor will require several runs (to test output for .srt, .sami and so on)
Allow the user to select what to test
For each input combination (file, parameters) allow to select one "good" result. As the good result is generated by a CCExtractor version, any other that produces a different result is considered broken. If the new result is different but better the user can make it the "good" one.
Since the goal is that everyone can cooperate, make sure results are stored in Google Drive, don't use an internal storage local to each user as that would defeat the purpose.

@cfsmp3 commented on GitHub (Apr 10, 2014): Important goals: - Obviously, keep track of results :-) - Keep in mind that for each input file there will be different output files, and that at least for now CCExtractor will require several runs (to test output for .srt, .sami and so on) - Allow the user to select what to test - For each input combination (file, parameters) allow to select one "good" result. As the good result is generated by a CCExtractor version, any other that produces a different result is considered broken. If the new result is different but better the user can make it the "good" one. - Since the goal is that everyone can cooperate, make sure results are stored in Google Drive, don't use an internal storage local to each user as that would defeat the purpose.

claunia commented

2026-01-29 16:32:57 +00:00

@canihavesomecoffee commented on GitHub (Apr 22, 2014):

This should be no problem :)

@canihavesomecoffee commented on GitHub (Apr 22, 2014): This should be no problem :)

claunia commented

2026-01-29 16:32:57 +00:00

@cfsmp3 commented on GitHub (Apr 22, 2014):

wforums all yours :-)

@cfsmp3 commented on GitHub (Apr 22, 2014): wforums all yours :-)

claunia referenced this issue

2026-01-29 16:43:11 +00:00