Arc Forumnew | comments | leaders | submitlogin
Arubic version 0.5 (google.com)
4 points by Pauan 4919 days ago | 5 comments


1 point by akkartik 4918 days ago | link

Why are some of the tests commented out? Are they not expected to work?

-----

1 point by Pauan 4918 days ago | link

They're commented out because they fail. :P

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.

-----

1 point by Pauan 4918 days ago | link

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.

-----

1 point by akkartik 4918 days ago | link

Were they working in the past, or are they just on a timeline?

-----

2 points by Pauan 4918 days ago | link

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.

-----