Re: Test plan documents in the repo

Hello everybody!
I just added a PR for the CSS Regions testing strategy[1]. Would it make sense to also include the generated file (or snapshot, in ReSpec parlance) in the repository?

Thanks a lot and happy Thanksgiving! :)
m.

[1] https://github.com/w3c/csswg-test/pull/385

Mihai Balan | Quality Engineer @ Web Engine team |  mibalan@adobe.com<mailto:mibalan@adobe.com> | +4-031.413.3653 / x83653 | Adobe Systems Romania


From: Rebecca Hauck <rhauck@adobe.com<mailto:rhauck@adobe.com>>
Date: Monday, October 28, 2013 10:21 PM
To: "peter.linss@hp.com<mailto:peter.linss@hp.com>" <peter.linss@hp.com<mailto:peter.linss@hp.com>>
Cc: Public list <public-css-testsuite@w3.org<mailto:public-css-testsuite@w3.org>>, Mirela Budaes <mbudaes@adobe.com<mailto:mbudaes@adobe.com>>, Balan Mihai <mibalan@adobe.com<mailto:mibalan@adobe.com>>, Rik Cabanier <cabanier@adobe.com<mailto:cabanier@adobe.com>>, Stefan-Teodor Craciun <scraciun@adobe.com<mailto:scraciun@adobe.com>>
Subject: Re: Test plan documents in the repo



On Oct 28, 2013, at 12:08 PM, Rebecca Hauck <rhauck@adobe.com<mailto:rhauck@adobe.com>> wrote:

Hey Peter,

My colleagues Mihai Balan and Mireal Budaes have recently been designated as the Test Coordinators for the CSS Regions and CSS Compositing & Blending specs, respectively.  I'll be fulfilling that role for the CSS Shapes spec.  As part of our process to ensure we're getting the proper test coverage, we'd like to publish test plan documents for these specs. Mihai and Mirela have already authored such docs and are each serving them from their individual github repos [1][2].

Great news, be sure to set the test suite owners in Shepherd[3] so the information is picked up by the build. Ping me on IRC if you need help with that.

Just added myself for Shapes. Since Mirela's just kicked off the testing effort for Compositing and Blending, that suite does not yet exist in Shepherd. (The first set of tests are coming very shortly when PR #110 lands [4]).  Can I just go ahead and create the suite there manually now so I can add her name?  Following the naming convention I see there, would it be compositing-1_dev?


In an effort to make our testing strategy more transparent, we'd like to serve these documents from a more discoverable place that is closer to the tests (and specs).  Would it be ok to add them to the repo?  I'd propose a /test-plans  directory at the root of the repo with /spec-shortname subdirectories containing these documents.  Any objections?

Fine by me.

Great!  Mirela, Mihai, if you'd like to port your docs over, you can either send a PR in github (which may be easiest since they're already in github) or do a straight hg push.  We can then come up with a proposal for linking these docs so they're more discoverable.