[Mono-bugs] [Bug 36280][Nor] New - Writing NUnit appname.exe.config file tests

bugzilla-daemon@rocky.ximian.com bugzilla-daemon@rocky.ximian.com
Fri, 3 Jan 2003 22:08:32 -0500 (EST)

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by jonpryor@vt.edu.


--- shadow/36280	Fri Jan  3 22:08:32 2003
+++ shadow/36280.tmp.31249	Fri Jan  3 22:08:32 2003
@@ -0,0 +1,51 @@
+Bug#: 36280
+Product: Mono/Runtime
+Version: unspecified
+OS: other
+OS Details: 
+Status: NEW   
+Priority: Normal
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: jonpryor@vt.edu               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+Summary: Writing NUnit appname.exe.config file tests
+This is/can be considered a meta-bug.
+We need to be able to write NUnit test cases for appname.exe.config file
+At present, the only way to test .exe.config files is to have separate
+.exe's with their own .exe.config files.  This is undesirable, as it
+doesn't fit into the current NUnit test framework.
+There are two solutions (possibly more)
+ 1. Be able to fit arbitrary executables into the framework, so 
+    they'll be invoked and handled transparently with normal 
+    test cases.  I'm not betting on this happening.
+ 2. Do as Gonzalo Paniagua Javier suggests:
+        You could do it creating a new AppDomain and setting the
+        configuration file name in SetupConfiguration and then 
+        running the tests in that application domain, BUT... 
+        there's a bug related to AppDomain that makes this not 
+        to work :-(. Once that bug is fixed (31245), it should
+        work this way.
+As mentioned, solution 2 depends upon:
+There may be other issues that need to be resolved to make this work
+properly.  These issues should be listed here as they are discovered.
+Philippe Lavoie needs similar functionality for testing the web server: