W3C home > Mailing lists > Public > public-css-archive@w3.org > May 2017

[csswg-drafts] [css-testing] Normalize linking to CSS properties

From: Greg Whitworth via GitHub <sysbot+gh@w3.org>
Date: Fri, 19 May 2017 17:51:14 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-230044092-1495216273-sysbot+gh@w3.org>
gregwhitworth has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-testing] Normalize linking to CSS properties ==
In reviewing the flex test suite I found that there are numerous tests that are testing the same thing but linking to different aspects of the spec. I would like to normalize these, and recommend that tests in the future ensure that they link to the same location based on our decision here. Let me provide an example:

    propdef-flex-basis: 9 tests
    flex-basis-property: 10 tests

In talking with @gsnedders there is a desire to improve understanding test -> spec coverage, which my [node module](https://www.npmjs.com/package/wptcoverage) is trying to achieve. It would be really nice if most tests are linking to the sections linked in the TOC, and only going into sub anchors where necessary.

I say all that to say that my recommendation is to link to `flex-basis-property` rather than the `propdef`. That said I don't have a really strong opinion on this, as since we do have a desire to move to more test driven spec writing, we'll need to look at the spec for tests that link to `should` & `must` statements within the spec. But I need us to agree on something so that we can make the tests match and thus the counts accurate.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1395 using your GitHub account
Received on Friday, 19 May 2017 17:51:20 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:12 UTC