> They should be added, since we are bound to get some edge cases wrong > (c.f. initial SQL parsing) and having regression tests will help there. > If you could add those, that would be great. Testing both sorts of > quotes, backslashes, semicolons and percentage signs would be my > suggestion for a start. What other characters might we screw up? > Anything that is dangerous for any database or that we might be using as > a replacement hook is a candidate.
There doesn't seem to be any document regarding how to write appropriate and useful tests. That would be helpful to a casual contributor like me. My 'testing' framework is pure duct-tape. I can root through the existing code, but some guidance would make it easier to do the right thing. > Some of these may have simple answers, I don't know. I'm working on > other things at the moment, so I don't want to stop completely for this. > But since you've brought this up, we might as well keep the momentum > going to help you get it to the point of being easy to apply. I can do the work, I just wanted to find out what was needed. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers -~----------~----~----~----~------~----~------~--~---
