About tests integration

[Iago Toral Quiroga <itoral igalia com>]

Hi, 

I have talked to dape at #build-brigade to decide how we should
integrate the results of the unit tests for each module in buildbot (or
any other continuous integration tool (CIT)). These have been the
conclusions:

  * Maintainers should provide a "check" target for the make command.
      * Maintainers should provide a nice html report with the test
        results in a file with a well known name and path that the CIT
        will link from the module's view.
      * The build-brigade would help maintainers to achieve the above
        points by providing advice and proper tools to maintainers.
      * The build-brigade will try to convince maintainers to provide
        this integration with the CIT. The build-brigade could even help
        with the integration process or even provide the necessary
        patches directly.
      * Check does not provide HTML logging capabilites, but XML logging
        instead. I will create an XSLT for it, while I prepare the
        gtkvts tests for the CIT demo, that could be used by other
        maintainers using Check for their tests.

Besides the tests integration, we also concluded:

      * At this moment, the view of buildbot is messy and needs to be
        fixed, dape is working a bit on it.
      * We still lack a roadmap for required buildbot features. This is
        necessary to evaluate how much work we need to invest, which
        tasks must be done and priorize them. We also need it to know if
        we can use buildbot to have a decent version for a gtkvts demo
        in September, otherwise we might consider other options.

Comments, opinions?

Iago.