Well, I suppose that’s just the way it goes.
I’ve been hacking apart the rjs-assertions plugin in an effort to fix several serious usage and code concerns I had. But this morning I came across Kevin Clark’s post announcing his new rjs testing plugin.
Kevin’s plugin is masterfully developed and does the job very well. While it’s missing a couple features I want, I would have a hard time recommending my plugin over his at this point.
I’m not sure what this means for rjs-assertions. If I complete my re-write, it will end up looking nearly identical to Kevin’s project. On the other hand, the code in rjs-assertions is slightly embarassing, and was never intended to be a long-term representation of my Ruby skills. For that reason alone, I may continue rewriting rjs-assertions.