QA PRESENTATION: TEST SUITE PRINCIPLES
======================================

http://www.w3.org/Style/CSS/Test/testsuitedocumentation.html

javascript:void(function(){var e = document.createElement('link');e.rel='stylesheet';e.href='data:text/css,*{margin:0!important}h2,h3{font-size:3em}p,dl,ol,ul,span,%23abstract,%23contents,%23intro,%23conventions,%23history,%23usingtestsuites,%23cover,%23getting,%23next-and,%23test-content,%23something,%23sooner,%23atomictests{display:none}.head p,.head dl,.head ol,.head ul{display:block}.head span{display:inline}.head dd{padding-left: 50px}.copyright{padding-top:1.25em;}hr{margin-top:0.75em!important}h1{padding:2em 0 0.75em;}h2{padding-top:3em;page-break-before:always}h3{padding:5em 0 1em;page-break-before:always}%23validtests+p{display:block;text-indent:-500em}%23validtests+p a{text-indent:0;font-size:2em;float:left;padding:0.5em;content:\'Suite %23\' counter(suite, decimal-leading-zero);counter-increment:suite}a[href="http://validator.w3.org/"],a[href="http://jigsaw.w3.org/css-validator/"]{display:none}%23testthetech{width:80%25}%23incremental{font-variant:small-caps;text-align:center;letter-spacing:0.12em;text-indent:-0.8em;padding-top:9em;content:\'Fin\'}[lang=tr]{content:\'Tantek %5CC7 elik\'}';document.getElementsByTagName('head')[0].appendChild(e);}())


 Points:
  CSS TEST SUITE DOCUMENTATION
  * This documentation is already online.

  TEST SUITE PRINCIPLES
  * I am going to be talking about...

  VALID TESTS
  * Should go without saying but it turns out many tests are invalid. 
    None of these tests were valid two years ago. 12 are still
    invalid. (4 fixed, 2 404.)    

  SIMPLE FORMAT
  * Write simple tests -- easier to use, less likely to trip up unrelated bugs

  EASE OF AUTHORING
  * Test suites are hard enough to write as it is -- make it easy to
    write new tests.
     e.g. Tests should be authored in the format that will be used to test the UA.
     Low barrier to entry means community can help more.

  TEST THE TECH...
  * Minimise dependencies on other technologies.
     e.g. 

  FEATURE COVERAGE
  * Want to test each feature alone, and then you test features of the
    tech you are testing together.

  SELF DESCRIBING RESULTS
  * "This test should be green". Tests should be obvious so that using
    the tests to get results does not take long. Tests should try to
    exaggerate effects.