gstreamer

mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2025-02-26 16:06:52 +00:00

History

Alicia Boya García 482c029c53 validate: miscellaneous Python cleanups I spent too much time trying to navigate validate Python code to figure out where a test was coming from. Hoping that it's slightly easier for the next person, this patch: * Adds type annotations to setup_tests(), for the sake of code navigation. * Adds comments matching each test generator with the patterns of test names it produces. * Removes an if statement in `register_default_scenarios()` where both branches have the same exact code with the same exact very long list. * Removes NamedDic [sic] and replaces it with SimpleNamespace from the standard library (3.3+) which has the same purpose and API. Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/8090>		2025-02-22 10:30:35 +00:00
..
data	meson: Give the same name for api_version in all modules	2024-12-20 20:19:28 +00:00
docs
gst	docs: port plugins to explicit sources	2025-01-13 19:17:13 +01:00
gst-libs	validate: Fix leaks in ssim components	2024-10-31 01:39:19 +00:00
launcher	validate: miscellaneous Python cleanups	2025-02-22 10:30:35 +00:00
plugins	validate/gapplication: silence a maybe-unitialized warning	2024-11-18 12:10:58 +11:00
tests	meson: Give the same name for api_version in all modules	2024-12-20 20:19:28 +00:00
tools	meson: Give the same name for api_version in all modules	2024-12-20 20:19:28 +00:00
.gitignore
COPYING
meson.build	meson: Give the same name for api_version in all modules	2024-12-20 20:19:28 +00:00
README

README

== 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

Build with:

meson build --prefix=<installation-prefix>
ninja -C build
sudo ninja -C build 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