Tests fail. about channels

[andrewgodwin]

Yes, the tests aren't done yet, and won't be until the code is semi-finalised; closing as INVALID, since obviously passing tests are needed, and will come when the code stablilises.

[DanLipsitt]

Context: I'm seeing if I can make a dent in #32 because that's a blocker for me. Writing my own tests is a way for me to explore the problem, and might be helpful for the project in general. So it would be useful to have a working test command even if existing tests don't pass. Currently they are not just failing, but erroring.

[DanLipsitt]

I'll see if I can get the test runner working unless you recommend against it. Any tips?

[andrewgodwin]

Not really; what's there is pretty basic and doesn't really work terribly well. The main problem you'll have is that tests will need to have at least two different processes running if not three (daphne, redis, test code) if you want to do proper end-to-end testing; if you just want to artificially generate messages instead of going via Daphne, you'll need to probably write a whole suite of code that makes example messages and hook everything up to the in-memory ASGI backend.

[DanLipsitt]

I'm not trying to test end-to-end. Just unit testing. I think I may have uncovered a bug already, or I am using the wrong Message class. I'll put it in a PR so you can see. Then I'll probably put Channels aside until things have settled a bit more. Thanks!