Hi, how do y'all people test unit your weblocks code? I'm referring to things like testing the output of widgets that use RENDER-LINK internally etc. Some ogling of the weblocks-test sources suggest it's avoided when possible, but that doesn't explain how things such as gridedit are tested, and I'm not able immediately to find out from the code.
What I'm getting at is that DEFTEST-HTML simply compares results as string, but that's hopelessly non-robust in HTML. So some sort of defense against changing elements such as action URLs is needed, but I can't find it. We're currently contemplating one of the two possible approaches, either Selenium or writing a simple programmatic browser on top of Drakma and closure-html, but if a good way exists inside weblocks-test already, I'd prefer to use that. Cheers, Maciej --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" 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/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
