Re: Roadmap Updated
"Charlie Poole" <[email protected]>
| Newsgroups | gmane.comp.windows.dotnet.nunit.devel |
|---|---|
| Message-ID | <008401c882ed$c34295c0$6401a8c0@ferrari> |
Hi Kelly, > > My main conclusion so far is that there is an intrinsic > difference > > between extensions that provide data staticly and those > where it is > > only available at run time. > > I would assume the difference you are referring to is the > difference between the RowTest sort of approach and the > IterativeTest approach. Yes, at least in one aspect. In RowTest, we can look at the source code and tell how many test cases will be created. This would be true for any approach that places the data in attributes. To support this sort of approach, we need to be able to take a method and generate multiple test cases from it. In your IterativeTest, we can only tell where the data will come from. It's not possible, in general, to figure out how many cases there will be by looking at the code. Of course, some of your examples use a constant list of data points, but they would not have to be constant. To support this approach, we need to either 1) allow test cases to be added at test execution time, or 2) allow a test to return more than one result I happen to lean toward the #2, but that's a detail - you can se that the two situations require different support from NUnit. > The Theory syntax seems to merge these two approaches... so > I'm not sure whether or not it remains an unsolvable problem > to merge the two approaches. No - the Theory examples we have seen use both approaches. So NUnit would need to support both of them... unless that's what you mean by merge. :-) > The conversation you pointed to was technically a little past > my experience thus far (too internal), so while I'm very > interested, I couldn't make a helpful reply. That's cool. Jump in where you can. We're at the implementation stage, where it's a question of how the internals will work, so it's natural that we're getting more technical. One way to read this is to ask how the availabilitiy of some NUnit feature or interface would help you to implement a given extension syntax. Charlie > -Kelly > > -------------------------------------------------------------- > ----------- > This SF.net email is sponsored by: Microsoft Defy all > challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > nunit-developer mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/nunit-developer > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/