Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>The advantage of this is that I don't have to sit with a checklist going through each browser - 'Is this header bold? Are these links underlined? Is this column 110px wide?' - every time I make a CSS change.</p> </blockquote> <p>Sure, but the secret is that you don’t have to do that now.</p> <p>If this header isn’t bold, then no-one’s going to die, or lose any money. Someone will notice*, and it’ll get fixed, with minimal effort.</p> <p>You’re better off spending time designing your CSS so that your styles are isolated (and thus unlikely to cause difficult-to-trace errors) than writing automated tests for every element on every page on your site.</p> <p>The amount of effort you’d need to get something like this working is disproportionate both to the difficulty of getting the code right (which isn’t much), and the consequences of getting the code wrong (which isn’t much either).</p> <p>More practically, how would you specify the kind of tests you're describing? You'd need to tell the test runner which elements it should check, and what each element's style should be. That's what CSS does. Maybe your definitions for which elements to check could be much more specific your CSS selectors (e.g. select each element on each page individually), but that would be very time-consuming, both to write initially and to maintain.</p> <p>(Just to elaborate on the necessary effort: for the cross-browser rendering tests you’re describing, you’d have to run actual web browsers (using something like Selenium), meaning you’d need multiple machines (for IE), all of which have to be accessible to your testing framework. This would be a nightmare to run personally, and very computationally intensive to offer as a service — just ask the guys who run <a href="http://litmus.com/" rel="nofollow">Litmus</a>.)</p> <p>Sorry that this isn’t really an answer to your actual question, but test-driven development can be a bit of a religion, in the sense that people get very inspired by the idea of it (which is admirable) without really understanding how it works, or where it actually offers a decent return on your time.</p> <hr> <p>* (Or, as I’ve experienced more frequently, no-one will notice, and you’ll spend a few seconds pondering the pointlessness of your professional existence before reaching for your third beer of the morning.)</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload