On Sun, Jan 14, 2007 at 10:02:44AM -0600, Aaron Spike wrote:
Thinking back, I can't remember successfully sharing a document since the rewrite of inkboard. I have on occation been able to connect to google talk and chat with the embedded pedro client. Today I installed a local wildfire server to remove as many variables as possible. Now I can't even connect. Inkboard gives "login: no second SASL challenge offered by server." So my question is this. Who has gotten inkboard to work recently? And how did you do it?
It really sounds to me like this could benefit greatly from having a test or associated with it. This is side functionality that doesn't get tested very often, so it is at high risk of changes in the main codebase break it. So it would be nice to have a test that (non-inkboard) developers could periodically run to verify they haven't caused a regression in it.
I'm thinking that a test like this would be handy:
inkboard-test -s http://my.jabber.server.org
0. Unconnected drawing operation - Perform a set of basic drawing operations - Check that the result is as expected
1. Account creation - Create two accounts inkboard-a-$random, inkboard-b-$random - Check that both accounts were correctly created
2. Connection - Connect accounts A and B - Verify server says they're connected
3. Communication - Send simple text message from A to B to verify connection - Send unicode text message - Send large number of small text messages very quickly - Send several large text fragments (0.1k, 1k, 10k, 100k, 1M)
4. Drawing - Send a few basic drawing elements from A; wait, then verify received correctly at B. - Make some simple modifications to drawing elements (color, position, stroke weight, etc.), wait, and verify they were correctly received by B. - Send more advanced drawing elements from A, then verify at B. - etc.
Just having the above would go a *long* way to helping stablize inkboard. Even if it were just stubbed out, it'd give us something to build on into the future. It'd also make it easier for other people to get involved in helping work on fixing bugs, since there'd be an easy procedure for finding and replicating them.
Bryce