Hello, I'm using CE to develop a site at work, and I've written a .autotest file that lives in the project root. By running autotest in the background, I know anytime I break core CE functionality by overriding a class (plus, it reinforces good behavior driven habits for the code I'm writing). Autotest has a default discovery file for rails which tells it to ignore the vendor directory completely. In writing this .autotest file, I essentially throw away all the stuff that discovery file sets up and start from scratch, mirroring testing relationships in the vendor directory. The pattern I've been using is to always try to add to the existing tests in CE by writing my own tests in the project tests dir, unless it's too complicated in which case I ignore the plugin test completely and bring in all those tests into my project tests directory.
You probably won't be able to use this out of the box, but I hope it helps some people develop with more awareness of potential problems. http://gist.github.com/241135 - Jeremy "He [de Sade] was the first one mad enough and sane enough to accept the given, the immutable, to start from man-in-history rather than from man-in-theory. Well, he says, I don't believe in the 'noble savage', I even doubt that he is 'inherently good', but taking him as he is I still say: freedom. He deserves liberty because nobody else is good enough to take it away from him." - Robert Anton Wilson -- You received this message because you are subscribed to the Google Groups "CommunityEngine" 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/communityengine?hl=.
