4 commits

Author	SHA1	Message	Date
Thiago Santos	773d8adc5e	qa-report: splitting a GstQaReport into a GstQaIssue and GstQaReport ... Reports now point to Issues, that are uniquely identified and have translatable descriptions. This way we are going to be able to uniquely identify the issues and applications can enable/disable checks for specific elements.	2013-07-26 12:16:29 -03:00
Thibault Saunier	382fcc9a01	qa: Properly set reporter's runner reference ... That was never set, but it is needed for the reporter to properly add reports to the runner. We still keep a reference on the monitor to make things simpler	2013-07-25 16:58:14 -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