You are writing your web application, you create your tests first, you develop the code right after that. Later you run the tests again to ensure your code is still working as expected—or as defined. You are doing it right.
The next step is to adopt this concept for CSS (including Sass or Less). Which is very easy with only a few changes. It will:
Does it sound strange for CSS? I’ll show you how. And how this combines the experiences made in software development and corporate design style guides.
@eirc K: I can do a quick intro, but 30 min is a bit short. I would rather talk about the concepts. Moving your legacy code is important and I will try to get it in. Thanks!
Are you planning on including info on using living styleguide generators/documentors such as KSS or Kalei Style guide and the example of Github's styleguide? They are all amazing but IMO currently lack a quick and easy way to get into them. The big question however (as always) is how you move your legacy code there :)