the element inside the harness
the sink (output) harness (if any)
the internal harness sink pad
the source (input) harness (if any)
the internal harness source pad
A convenience function to allows you to call gst_pad_add_probe on a #GstPad of a #GstElement that are residing inside the #GstHarness, by using normal gst_pad_add_probe syntax
MT safe.
a #gchar with a #GstElementFactory name
a #gchar with the name of the pad to attach the probe to
a #GstPadProbeType (see gst_pad_add_probe)
a #GstPadProbeCallback (see gst_pad_add_probe)
Similar to gst_harness_add_sink_harness, this is a convenience to
directly create a sink-harness using the sink_element_name
name specified.
MT safe.
a #gchar with the name of a #GstElement
Similar to gst_harness_add_src, this allows you to send the data coming out of your harnessed #GstElement to a sink-element, allowing to test different responses the element output might create in sink elements. An example might be an existing sink providing some analytical data on the input it receives that can be useful to your testing. If the goal is to test a sink-element itself, this is better achieved using gst_harness_new directly on the sink.
If a sink-harness already exists it will be replaced.
MT safe.
a #GstHarness to be added as a sink-harness.
Similar to gst_harness_add_sink, this allows you to specify a launch-line instead of just an element name. See gst_harness_add_src_parse for details.
MT safe.
a #gchar with the name of a #GstElement
Similar to gst_harness_add_src_harness, this is a convenience to
directly create a src-harness using the src_element_name
name specified.
MT safe.
a #gchar with the name of a #GstElement
a #gboolean specifying if the #GstElement uses gst_clock_wait_id internally.
A src-harness is a great way of providing the #GstHarness with data.
By adding a src-type #GstElement, it is then easy to use functions like
gst_harness_push_from_src or gst_harness_src_crank_and_push_many
to provide your harnessed element with input. The has_clock_wait
variable
is a great way to control you src-element with, in that you can have it
produce a buffer for you by simply cranking the clock, and not have it
spin out of control producing buffers as fast as possible.
If a src-harness already exists it will be replaced.
MT safe.
a #GstHarness to be added as a src-harness.
a #gboolean specifying if the #GstElement uses gst_clock_wait_id internally.
Similar to gst_harness_add_src, this allows you to specify a launch-line, which can be useful for both having more then one #GstElement acting as your src (Like a src producing raw buffers, and then an encoder, providing encoded data), but also by allowing you to set properties like "is-live" directly on the elements.
MT safe.
a #gchar describing a gst-launch type line
a #gboolean specifying if the #GstElement uses gst_clock_wait_id internally.
The number of #GstBuffers currently in the #GstHarness sinkpad #GAsyncQueue
MT safe.
The total number of #GstBuffers that has arrived on the #GstHarness sinkpad. This number includes buffers that have been dropped as well as buffers that have already been pulled out.
MT safe.
Similar to gst_harness_crank_single_clock_wait(), this is the function to use if your harnessed element(s) are using more then one gst_clock_id_wait. Failing to do so can (and will) make it racy which #GstClockID you actually are releasing, where as this function will process all the waits at the same time, ensuring that one thread can't register another wait before both are released.
MT safe.
a #guint describing the number of #GstClockIDs to crank
A "crank" consists of three steps: 1: Wait for a #GstClockID to be registered with the #GstTestClock. 2: Advance the #GstTestClock to the time the #GstClockID is waiting for. 3: Release the #GstClockID wait. Together, this provides an easy way to not have to think about the details around clocks and time, but still being able to write deterministic tests that are dependent on this. A "crank" can be though of as the notion of manually driving the clock forward to its next logical step.
MT safe.
Allows you to dump the #GstBuffers the #GstHarness sinkpad #GAsyncQueue to a file.
MT safe.
a #gchar with a the name of a file
The number of #GstEvents currently in the #GstHarness sinkpad #GAsyncQueue
MT safe.
The total number of #GstEvents that has arrived on the #GstHarness sinkpad This number includes events handled by the harness as well as events that have already been pulled out.
MT safe.
Most useful in conjunction with gst_harness_new_parse, this will scan the
#GstElements inside the #GstHarness, and check if any of them matches
element_name
. Typical usecase being that you need to access one of the
harnessed elements for properties and/or signals.
MT safe.
a #gchar with a #GstElementFactory name
Gets the allocator
and its params
that has been decided to use after an
allocation query.
MT safe.
Get the timestamp of the last #GstBuffer pushed on the #GstHarness srcpad, typically with gst_harness_push or gst_harness_push_from_src.
MT safe.
Get the #GstTestClock. Useful if specific operations on the testclock is needed.
MT safe.
This will set the harnessed #GstElement to %GST_STATE_PLAYING. #GstElements without a sink-#GstPad and with the %GST_ELEMENT_FLAG_SOURCE flag set is considered a src #GstElement Non-src #GstElements (like sinks and filters) are automatically set to playing by the #GstHarness, but src #GstElements are not to avoid them starting to produce buffers. Hence, for src #GstElement you must call gst_harness_play() explicitly.
MT safe.
Pushes a #GstBuffer on the #GstHarness srcpad. The standard way of interacting with an harnessed element.
MT safe.
Transfer data from the src-#GstHarness to the main-#GstHarness. It consists of 4 steps: 1: Make sure the src is started. (see: gst_harness_play) 2: Crank the clock (see: gst_harness_crank_single_clock_wait) 3: Pull a #GstBuffer from the src-#GstHarness (see: gst_harness_pull) 4: Push the same #GstBuffer into the main-#GstHarness (see: gst_harness_push)
MT safe.
Transfer one #GstBuffer from the main-#GstHarness to the sink-#GstHarness. See gst_harness_push_from_src for details.
MT safe.
Get the min latency reported by any harnessed #GstElement.
MT safe.
Setting this will make the harness block in the chain-function, and then release when gst_harness_pull() or gst_harness_try_pull() is called. Can be useful when wanting to control a src-element that is not implementing gst_clock_id_wait() so it can't be controlled by the #GstTestClock, since it otherwise would produce buffers as fast as possible.
MT safe.
Sets the GstHarness
srcpad and sinkpad caps using strings.
MT safe.
a gchar
describing a #GstCaps to set on the harness srcpad
a gchar
describing a #GstCaps to set on the harness sinkpad
When set to %TRUE, instead of placing the buffers arriving from the harnessed #GstElement inside the sinkpads #GAsyncQueue, they are instead unreffed.
MT safe.
a #gboolean specifying to drop outgoing buffers or not
As a convenience, a src-harness will forward %GST_EVENT_STREAM_START, %GST_EVENT_CAPS and %GST_EVENT_SEGMENT to the main-harness if forwarding is enabled, and forward any sticky-events from the main-harness to the sink-harness. It will also forward the %GST_QUERY_ALLOCATION.
If forwarding is disabled, the user will have to either manually push these events from the src-harness using gst_harness_src_push_event(), or create and push them manually. While this will allow full control and inspection of these events, for the most cases having forwarding enabled will be sufficient when writing a test where the src-harness' main function is providing data for the main-harness.
Forwarding is enabled by default.
MT safe.
a #gboolean to enable/disable forwarding
Sets the liveness reported by #GstHarness when receiving a latency-query. The default is %TRUE.
%TRUE for live, %FALSE for non-live
Sets the allocator
and params
to propose when receiving an allocation
query.
MT safe.
a #GstAllocator
a #GstAllocationParams
Sets the GstHarness
sinkpad caps using a string.
MT safe.
a gchar
describing a #GstCaps to set on the harness sinkpad
Sets the GstHarness
srcpad caps using a string. This must be done before
any buffers can legally be pushed from the harness to the element.
MT safe.
a gchar
describing a #GstCaps to set on the harness srcpad
Advance the #GstTestClock to a specific time.
MT safe.
a #GstClockTime to advance the clock to
Sets the min latency reported by #GstHarness when receiving a latency-query
a #GstClockTime specifying the latency
Convenience that calls gst_harness_push_to_sink pushes
number of times.
Will abort the pushing if any one push fails.
MT safe.
a #gint with the number of calls to gst_harness_push_to_sink
Transfer data from the src-#GstHarness to the main-#GstHarness. Similar to gst_harness_push_from_src, this variant allows you to specify how many cranks and how many pushes to perform. This can be useful for both moving a lot of data at the same time, as well as cases when one crank does not equal one buffer to push and v.v.
MT safe.
a #gint with the number of calls to gst_harness_crank_single_clock_wait
a #gint with the number of calls to gst_harness_push
Similar to what gst_harness_src_push does with #GstBuffers, this transfers a #GstEvent from the src-#GstHarness to the main-#GstHarness. Note that some #GstEvents are being transferred automagically. Look at sink_forward_pad for details.
MT safe.
Pulls all pending data from the harness and returns it as a single #GBytes.
Tears down a GstHarness,
freeing all resources allocated using it.
MT safe.
The number of #GstEvents currently in the #GstHarness srcpad #GAsyncQueue
MT safe.
The total number of #GstEvents that has arrived on the #GstHarness srcpad This number includes events handled by the harness as well as events that have already been pulled out.
MT safe.
Sets the system #GstClock on the GstHarness
#GstElement
MT safe.
Sets the #GstTestClock on the #GstHarness #GstElement
MT safe.
Waits for timeout
seconds until waits
number of #GstClockID waits is
registered with the #GstTestClock. Useful for writing deterministic tests,
where you want to make sure that an expected number of waits have been
reached.
MT safe.
a #guint describing the numbers of #GstClockID registered with the #GstTestClock
a #guint describing how many seconds to wait for waits
to be true
Stop the running #GstHarnessThread
MT safe.
a #GstHarnessThread
#GstHarness is meant to make writing unit test for GStreamer much easier. It can be thought of as a way of treating a #GstElement as a black box, deterministically feeding it data, and controlling what data it outputs.
The basic structure of #GstHarness is two "floating" #GstPads that connect to the harnessed #GstElement src and sink #GstPads like so:
|[ __________________________ _____ | _____ _____ | _____ | | | | | | | | | | | src |--+-| sink| Element | src |-+--| sink| || | || || | || |__________________________|
Another main feature of the #GstHarness is its integration with the #GstTestClock. Operating the #GstTestClock can be very challenging, but #GstHarness simplifies some of the most desired actions a lot, like wanting to manually advance the clock while at the same time releasing a #GstClockID that is waiting, with functions like gst_harness_crank_single_clock_wait().
#GstHarness also supports sub-harnesses, as a way of generating and validating data. A sub-harness is another #GstHarness that is managed by the "parent" harness, and can either be created by using the standard gst_harness_new type functions directly on the (GstHarness *)->src_harness, or using the much more convenient gst_harness_add_src() or gst_harness_add_sink_parse(). If you have a decoder-element you want to test, (like vp8dec) it can be very useful to add a src-harness with both a src-element (videotestsrc) and an encoder (vp8enc) to feed the decoder data with different configurations, by simply doing:
and then feeding it data with:
@record