What I do is I write the gadget in a way that makes it work both locally (or as a website on a remote server) and then I add a layer on top that makes it work with Google Wave. That way I can test 90% of the gadget locally, no problem. And for the other 10% I just use the debug features of the sandbox Wave client. That has worked good so far even for bigger/more involved gadgets and the bonus is that your gadget then doesn't need to be Wave exclusive.
If you'd want to use a test-driven development approach you could only test this 90% non-Wave part of the application but none of the Google Wave specific stuff in the other 10%, so this approach may not be good enough for everyone. Cheers, Chris On Feb 9, 6:52 am, Jonas Huckestein <[email protected]> wrote: > Hi guys, > > so I just started developing Wave Gadgets and I'm currently using GWT. > While there are obvious benefits such as unit testability, cross- > browser support and code-splitting, there are also some downsides. For > instance I cannot easily test gadgets locally (not to mention testing > robots!). I had to create a local mock implementation of the wave API > for testing and every time I use a new API feature I have to add it to > my mock implementation. All in all it feels kind of clunky and > strange. > > Are there any easier ways to develop (possibly very complex) wave > gadgets? What do you guys use? > > In case you are interested, I wrote a tutorial in how to get started > developing gadgets with gwt. Also, I guess I will be uploading my > WaveMock framework to Google Cloud this week (if anybody is > interested): > > http://thezukunft.com/2010/02/08/a-wave-gadget-robot-using-gwt-2-0-an... > > Cheers, Jonas -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
