You could use InternalVisibleToAttribute to get access to internals. For the privates, it might work for you to make your classes partial. Then at least you could place your unit tests in a separate source file. It would have to be compiled in with your original assembly, however. Probably not what you were looking for.
The Ordered Test feature (in Beta 2) allows one to create lists of tests to execute. The TestInitializeAttribute and the TestCleanupAttribute flag methods that could be used to start/stop external applications. Wallace Kelly, Ph.D. DevelopMentor Instructor [EMAIL PROTECTED] -----Original Message----- From: Unmoderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Ragnvald Barth Sent: Monday, October 17, 2005 5:25 AM To: [email protected] Subject: [ADVANCED-DOTNET] Automated Testing We are using Visual Studio 2005 Team Suite (RC1). How do I write tests for internal and private methods and classes? How do I control the order of the various tests? How do I control the environment (start and stop applications that the code being tested is supposed to communicate with)? Do you know any good articles I should read (that goes beyond the scope of getting started)? =================================== This list is hosted by DevelopMentorR http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
