Break apart tests

[src-code]

Right now we have a few tests for getCss() that are a dumping ground for every unique type of class (hex values, hex + alpha, customs, child selectors, customs, etc). It'd be better if we could break this up into one test per class type, so we can be more explicit about having proper coverage for all syntax we support.

[3den]

Currently the getCss method is more than 200 LoC, it is hader to test one huge method that several small ones. What you guys think about simplifying this by create a class that does just css parsing:

Atomizer.prototype.getCss = function (config/*:AtomizerConfig*/, options/*:CSSOptions*/)/*:string*/ {
    return new CssParser(config).getContent(options);
}

This way we can move all that logic to CssParser and have methods there that are smaller and easier to test.

[3den]

@src-code @renatoi this way the API of Atomizer will stay the same but code will get easier to test and maintain.

[src-code]

@3den That's outside the scope of this issue - here, we're only really interested in ensuring that we have tests for each type of syntax we support. Whether we're testing getCss() or findClassNames() or some other class is really a different issue. I'd suggest opening a new issue to start a discussion on your idea of breaking up getCss()