GNOME Bugzilla – Bug 701924
tests: add playbin test for autoplugging of decoder-sink combination based on capsfeatures
Last modified: 2013-06-11 13:59:53 UTC
Created attachment 246397 [details] [review] tests: add more unit test for playbin Adding a unit test for autoplugging of video_decoder/video_sink combination based on capsfeatures.
commit eabd2a5c7b3685662e34a7153366ef27e8b55369 Author: Sreerenj Balachandran <sreerenj.balachandran@intel.com> Date: Mon Jun 10 14:43:35 2013 +0300 tests: add more unit test for playbin Add unit test for autoplugging of video_decoder/video_sink combination based on capsfeatures.
It seems that the following executables gst-plugins-base/test/check/elements/decodebin and gst-plugins-base/test/check/elements/playbin-complex are running only when executing from test/check folder. Because the path string GST_TEST_FILES_PATH == "../../test" always. Does it supposed to work like that?
You are not supposed to run the executables directly. 'make check' should work and 'make elements/playbin-complex.check' and friends should work (see 'make help' in tests/check/ for the other options).
Yes, you're supposed to run them with "make elements/playbin-complex.check" or "make check" or "make elements/playbin-complex.valgrind" and other variants from that directory.
Aha okay.. I was running "make check" which was time consuming and tried to run from test/check/elements/. Didn't know about "playbin-complex.check" Thanks :)
There are options for valgrind and gdb etc. as well. The reason to do it via make is that it sets up a special environment (test registry etc., and ignore plugins from other modules).