Open GoogleCodeExporter opened 8 years ago
Possible implementation:
1. Add methods to TemplateTreeBuilder to register requests for external
parameters.
2. Add properties to TestEnumerationOptions to provide values for external
parameters.
3. During test construction, add an ExternalDataSource to the root
TemplateBindingScope with a special name like "External".
4. Implement [BindExternal] to look for the named parameter in the "External"
data
source.
5. Expose external parameters in the TemplateModel.
6. Extend the test runners appropriately to be able to prompt for external
parameter
values and pass them in.
Note: External parameters should allow lists of values to be passed in. We'll
just
construct more template bindings that way.
Original comment by jeff.br...@gmail.com
on 26 Aug 2007 at 12:52
Also requires support from the Gallio test runners.
Original comment by jeff.br...@gmail.com
on 30 Oct 2007 at 2:23
Original comment by jeff.br...@gmail.com
on 18 Dec 2007 at 9:22
Might be superceded by test profiles.
Original comment by jeff.br...@gmail.com
on 17 Mar 2008 at 10:57
Original comment by jeff.br...@gmail.com
on 5 Oct 2008 at 9:16
Original comment by jeff.br...@gmail.com
on 19 Nov 2008 at 11:58
Original comment by jeff.br...@gmail.com
on 23 May 2009 at 1:52
Original comment by jeff.br...@gmail.com
on 29 Jun 2009 at 8:33
Original comment by Yann.Tre...@gmail.com
on 17 Jul 2010 at 8:20
Original comment by Yann.Tre...@gmail.com
on 14 Jun 2011 at 5:53
Any ideas when this feature will be available in MBUnit?
Original comment by itsmeNa...@gmail.com
on 17 Apr 2012 at 6:22
No work has been done on it, as far as I know. Do you have a use case?
Original comment by grahamr...@gmail.com
on 18 Apr 2012 at 11:52
Original issue reported on code.google.com by
jeff.br...@gmail.com
on 26 Aug 2007 at 12:43