gstreamer/validate
Thibault Saunier 11c49a7db8 validate:scenario: Execute actions without playback time without a valid position
If the user did not specify any playback time we should be able to
execute actions even if the pipeline can't answer the position query

+ Make simpler to read the conditions of an action execution
2014-11-25 19:41:00 +01:00
..
common@49f8c40577 Adapt submodule usage for gst-devtools 2013-09-09 17:40:36 +02:00
data validate: Rename action type playback_time to playback-time 2014-10-12 20:19:42 +02:00
docs validate: Add the notion of WAIT_MULTIPLIER for the wait action 2014-11-16 18:27:32 +01:00
gst validate:scenario: Execute actions without playback time without a valid position 2014-11-25 19:41:00 +01:00
launcher validate:launcher: Force clock sync for some protocols 2014-11-20 12:09:29 +01:00
pkgconfig validate: fix installation 2013-11-25 16:56:11 -03:00
po po: missing po rename 2013-08-15 01:44:59 -03:00
tests validate: Do not check if first buffer running time is 0 2014-11-19 17:59:26 +01:00
tools validate-launcher: restructure filesystem 2014-10-30 15:31:29 +01:00
.gitignore validate: Add more files to gitignore 2014-10-21 20:14:05 +02:00
AUTHORS qa: adds gst-qa binary and basic classes to run the QA tests 2013-07-09 16:08:30 -03:00
autogen.sh validate: update pre-commit hook. 2014-10-30 15:40:17 +01:00
ChangeLog Release 1.4.0 2014-10-20 13:24:29 +02:00
configure.ac validate-launcher: restructure filesystem 2014-10-30 15:31:29 +01:00
COPYING qa: adds gst-qa binary and basic classes to run the QA tests 2013-07-09 16:08:30 -03:00
Makefile.am validate-launcher: restructure filesystem 2014-10-30 15:31:29 +01:00
multi-pre-commit.hook validate: update pre-commit hook. 2014-10-30 15:40:17 +01:00
NEWS Release 1.4.0 2014-10-20 13:24:29 +02:00
pre-commit-python.hook validate: update pre-commit hook. 2014-10-30 15:40:17 +01:00
README docs: update and improve 2013-09-02 16:09:07 -03:00

== Gst-Validate

The goal of GstValidate is to be able to detect when elements are not
behaving as expected and report it to the user so he knows how things
are supposed to work inside a GstPipeline. In the end, fixing issues
found by the tool will ensure that all elements behave all together in
the expected way.

The easiest way of using GstValidate is to use one of its command-line
tools, located at tools/ directory. It is also possible to monitor
GstPipelines from any application by using the LD_PRELOAD gstvalidate
lib. The third way of using it is to write your own application that
links and uses libgstvalidate.

== BUILDING

Getting the code:

Releases are available at <URL>, download and extract the tarball. If you
want to use latest git version, do:

git clone <URI>

After cloning or extracting from a tarball, enter the gst-validate directory:

cd gst-validate

The 'master' branch uses gstreamer 1.0, there is a '0.10' branch for
gstreamer 0.10. The default is the 'master' branch, if you want to use it
for 0.10, do:

git checkout --track origin/0.10

Build with:

./autogen.sh --prefix=<installation-prefix>
make
sudo make install (only if you want to install it)

Replace <installation-prefix> with your desired installation path, you can omit
the --prefix argument if you aren't going to install it or if you want the
default /usr/local. It is possible to use gst-validate CLI tools without
installation.

== INSTRUCTIONS

If you are looking for informations on how to use gst-validate -> docs/validate-usage.txt
If you are looking for informations on gst-validate design -> docs/validate-design.txt