[Xcb] adding testcases to xcb/demo, my brother will write testcases for xinput for two weeks. (Re: [PATCH demo 1/1] make xcb/demo compile again.)

[Eric Anholt]

Christian Linhart <chris at DemoRecorder.com> writes:

> Hi Uli and all,
>
> On 2017-03-19 09:19, Uli Schlachter wrote:
>> "make compile again" sounds like it does not really need much review.
> Yes, I think so, too.
> Just the minimal changes to make it compile, so we can add our testcases.
>>
>> On 18.03.2017 10:55, Christian Linhart wrote:
>>> The reasoning behind this change is to prepare xcb/demo as
>>> a place to be used for test-suites.
>> I like that idea. Sounds like I should re-find my tests that I wrote for
>> some changes.
> That'd be great.
>
> How should we organize the testcases there?
>
> There is already a "test" subdirectory.
>
> But maybe we should make subdirectories in there to get more structure.
> E.g. one subdirectory per extension?
>
> What do you think?
>
> ***
>
> My brother Arthur will write some testcases for the xinput extension
> the next two weeks.
>
> This means that this will be quite some code in a short time.
> How should we proceed with that?
>
> He can post his patches, or we can set up an extra repo where his changes will be available for review.
> Then he'll post just a link to that repo.

Are these tests going in here going to be useful as X server regression
tests?  I've wondered where the right home would be for little X
regression tests, and would like to get more into piglit for keeping the
X server working.

If they are regression tests, xcb/demo does seem like a funny place for
them.  Maybe a new xcb/tests forked from demo?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/xcb/attachments/20170320/26fc211d/attachment.sig>