Christopher Lenz wrote: > > Consider also that JavaScript is not good when it comes to unit > > testing Web page generation. It's far easier to just test if there's a > > reference to a stylesheet than to test that there's a javascript that > > hopefully will insert this reference later. > > That's not really "unit testing" now, is it ;-) > > It's way easier to test this stuff at a lower level (using *actual* > unit tests), and then perform functional tests in the browser, either > manually, or using something like Selenium.
Hi Chris! I'm not sure what do you mean here. If I were a macro writer, I'd probably have a unit test with a macro rendered on a page, and I'd use a few XPath expressions to make sure things are in place, such as stylesheet if there's one, macro output, etc. I didn't yet look at Trac's built-in macro tests, but I'd imagine that's how they would be organized. Or am I off-base here? Sergey. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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/trac-dev -~----------~----~----~----~------~----~------~--~---
