@kizu, what is the difference between those two tests (the first one and the last one)?

var config = this.comb.getConfig('csscomb');
this.comb.configure(config);
this.shouldBeEqual('integral.css', 'integral.expected.css');

var expected = {...};
var config = this.comb.getConfig('csscomb');
expected['sort-order'] = config['sort-order'];
this.comb.configure(expected);
this.shouldBeEqual('integral.css', 'integral.expected.css');

The last one does not involve detect at all.

Hmm, I used this test to test if the config equal to the detected from expected (+ the absent sord-order option) would work to comb the integral.css. This way if we would add a new option that won't have the detect method, and there would be an integral test for this option, this test would fail.

I'm not sure we should have this test there, but added it anyway. If you'd like, I can remove it :)

I think it should be removed, yes.
It does not test anything that is not checked with the two previous cases already.

We can also remove hard coding of expected object.
If we need a modified clone of csscomb config, we can just get it:

var expected = this.comb.getConfig('csscomb');
delete expected['sort-order'];

(�↑ That's not necessary, just thinking out loud)

Ok, done. Agree on removing the hardcoded expected, however there were a few other things to do there to make it work (clone this expected object to prevent other tests to fail, sort those objects in the shouldDetect method, remove the exclude option from the config got).

@kizu rebase please?

Rebased (it should be merged after the #148)