3 commits

Author	SHA1	Message	Date
Thiago Santos	08aae8336b	qa-runner: simplify runner to not hold refs to monitor/pipeline ... The GstQaRunner is now a simple aggregator of reports that it receives from monitors and filechecker. This allows it to be used in both scenarios without APIs that expect GstElement or Monitors, that are only used on the pipeline monitoring QA tests.	2013-08-07 16:10:57 -03:00
Thibault Saunier	4fb8f47770	scenario: Implement the GstQaReporter interface and make use of it ... This way we can report issues from a scenario Also add a Seek aread to the known areas list We now need to pass the runner to the scenario instead of the pipeline as the GstQaReporter interface needs it.	2013-07-25 16:58:13 -03:00
Thibault Saunier	7508e35b7e	qa: Add a GstQaScenario class making it possible to execute scenarios ... A scenario correspond to a suite of action to execute on a pipeline, for the time being, we only support seeking the pipeline, but in the future we can imagine doing some queries, setting pipeline state, etc... The scenario can be loaded thanks to the GST_QA_SCENARIO environment variable, making it usable with any existant application, in case, the application can be used interactively, the user should either, not load any scenario or let the application run without interacting with it.	2013-07-25 16:56:40 -03:00