For instance, tests/arc.py.tests has who knows how many hundreds of tests. Almost all of them pass, but about 2 fail. Also, I think tests/coerce actually goes into an infinite loop.
You can uncomment them if you want[1], but then you'll get a ton of errors because the tests failed. That's normal: the failing tests are known bugs or missing features.
I didn't want to give the impression that Arubic was actually failing, but I didn't want to comment out the individual tests either, so I just commented the entire file. Kinda silly of me, in retrospect.
Perhaps I should put in a mechanism that lets me specify that a test is expected to fail... hm...
---
* [1]: Just be careful about tests/coerce. You may need to Ctrl+C to stop the loop.
Okay, I uncommented a bunch of the tests. The ones that are still commented are either not expected to work, or they're so broken that it's not really useful to run them right now.
Some of them never worked, like `iter` or `sweet-expressions`, because I haven't implemented that functionality yet. I still wanted the tests there so when I do implement them, I'll be able to get a quick yes/no as to whether Arubic matches the expectations or not.
Some of them, however, used to work and now don't. `macex` is an example of that. In the case of macex, the problem is that I changed Arubic, but didn't update the tests... they're out of sync. So it's commented out until I clean it up.
