I understand from reading the IRC back-scroll that we're heading into a feature freeze and then testing / bug squashing phase. I've noticed lately that our test coverage isn't all that good, as quite often every test in make check will pass but the first thing I get when I start pitivi interactively is a huge traceback ending in some part of pitivi core. I feel what's missing is a set of high-level tests that hit all the code-paths we take into core from the UI, perhaps paralleling the QA scenarios we have on the website. I started working on this but I'm wondering about a couple of things:
1) It would be useful to have some media files for tests involving the source list, but how do we handle this with version control? It seems like a bad idea to check even small media files into git, but maybe I'm mistaken about this. 2) Some parts of pitivi depend on having a running gobject.MainLoop, which is currently implemented only in InteractivePitivi. Using this starts the GUI, and it is my understanding that we do not want any of the tests to depend on the GUI. So should I instead factor the code which launches the MainLoop into the base application class? This wouldn't be entirely wrong since GStreamer also depends on having a running mainloop. --Brandon ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Pitivi-pitivi mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pitivi-pitivi
