Regarding Ruby dependency choice

[am11]

@mgreter, @xzyfer

Here is a list of C++ testing frameworks: http://en.wikipedia.org/wiki/List_of_unit_testing_frameworks#C.2B.2B

I purpose to make use of one of these (for instance CppUnit) to run sass-spec test suite in an effort to exempt
ruby dependenc[y/ies] (gem install minitest et al.).

One of the chief benefit is that it would enable us to test libsass' disableable options
more thoroughly and especially those related to source-map.

Thoughts?

BTW, Happy new year 2015! 🎈 🎉 🎆

[am11]

Note: in node-sass, we clone the spec repo, filter the tests and then loop through the suite to run each as a regular node.js test (using mocha f/w): spec.js#L29-L56. We can achieve the same here using CppUnit.

[xzyfer]

My thoughts from gitter conversation

- I'm all for dumping ruby where ever possible
- But sass-spec also does a little more than just run tests
- It has a couple utilities that we use to discover when previously failing start passing unexpectedly, and to normalise our expected outputs in specs
- It's not to say we couldn't do these things in CPP I'm just not sure it's worth the time to build those features
Maybe we could keep the ruby runner and have it shell out to cppunit instead of minitest as a way to get those features
- We also want sass-spec to become the defacto for all sass implementations, including ruby sass. So it coupling it too tightly to libsass will be problem