On Mon, Sep 13, 2010 at 12:04 PM, Nathan Schultz <[email protected]> wrote: > I have looked into this at one time, although my scenario was different; I > needed the HTTP Context to do some server-side mapping. > > I ended up admitting defeat and wrapped the .Net framework functionality I > needed in a class, and then used Rhino-Mocks to mock it. > > Unfortunately in your situation that doesn't prove that .Net will get your > resources correctly. At the same time, it's considered unnecessary to write > unit-tests over the .Net framework itself; at some stage an assumption must > be made. > > I did stumble upon a HTTP Simulator, but I have no idea how good it is: > http://haacked.com/archive/2007/06/19/unit-tests-web-code-without-a-web-server-using-httpsimulator.aspx
Thanks Nathan. I'm not trying to test the Resources system itself, specifically I want to test that I am putting the right localised text in the right place, and that it "reads" well. So, it's basically a thing I need to "see". I think I've seen that post and I'm not sure it does the localisation correctly, but I'll check it out again, I could be wrong. -- silky http://dnoondt.wordpress.com/ "Every morning when I wake up, I experience an exquisite joy — the joy of being this signature."
