On Tue, Jan 14, 2014 at 09:23:19AM +0100, Jens Rehsack wrote: > Hi everyone,
Hi Jens. > I noticed last Wednesday that there is a lot of confusion what I mean when > asking for how do we templating in DBI::Test. While that's true, I don't think it's the root cause of confusion. I think what we really need to discuss are requirements (high-level use-cases) and the overall structure of "the system". Without people sharing a good understanding of that context it's hard to have useful discusions about lower-level implementation details. > Beside all sides belonging to that question, I only meant the composition of > the resulting .t file. Why do we need "composition of the resulting .t file" with more functionality than my trivial prototype tumbler.pl does? I'm not saying that we don't - I'm just trying to point out that we all need to be clear about what we're trying to achieve here. Step back Jens and paint a bigger picture in enough detail that the need for templating becomes clear. We need to discuss: where test code comes from, who writes tests, what kind of scope an individual test file has, how they're shipped and installed. Should test code be shipped in .t files, .pl files, or .pm files? What's the least amount of knowledge that test code needs to work? Etc etc. Tim.
