Start switching to expectations, unsuccessfully. I wonder if this is related to the problem I had with speclj, only with better error messages
Minor tire kicking, trying to remember where I was and figure out why the pieces are being difficult. This seems like such a silly pointless use of the little time I have available
Getting a little closer...I'm receiving a byte[] instead of a sequence of strings. I really should have realized/expected this
This is at least a little closer: I'm receiving a DIE! (etc) message, which I expect from my speclj tests. And this version gives me a hint about what it is
Add logging...this version has hints about what's going on. I think it's actually choking on a final nil message
I'm not positive...but this version looks like it might actually be not failing horrifically.
Expectations unit testing seems to be vaguely working, though I'm not clear on why it's doing what it does...AUTH socket seems to get the Die message from nowhere and then everything stops. I obviously need to get a better grasp of what it's doing. Along with translating the speclj tests...their stack dumps just are not making any sense to me