Test Design

The rest of our CSS test migration goes smoothly (and mostly off-camera), so we turn our attention to test design. Our current CSS tests make assertions about each individual element on the page. Is there another way to organize our tests that would be clearer and more useful? We try out an idea.

  1. E305CSS Unit Testing

    Mon, 11 May ’15
  2. E306Installing Quixote

    Wed, 13 May ’15
  3. E307Cross-Browser CSS Tests

    Mon, 18 May ’15
  4. E308A Cross-Browser Test Success

    Wed, 20 May ’15
  5. E309Careful Positioning

    Mon, 25 May ’15
  6. E310Modernizr Safety

    Wed, 27 May ’15
  7. E311z-index and background-image

    Mon, 1 June ’15
  8. E312How to Parse a Stinkin’ URL

    Wed, 3 June ’15
  9. E313Test Design

    Mon, 8 June ’15
  10. E314Speak to Me

    Wed, 10 June ’15
  11. E315Button It Up

    Mon, 15 June ’15
  12. E316Pixel-Perfect

    Wed, 17 June ’15