On Fri, Mar 29, 2002 at 11:21:23AM -0000, Geoffrey Hausheer wrote: > I know regression testing isn't as interesting as > doing real development, and so I appologize with once > again spamming the list with regression questions... NP. I'm sure it helps :)
[...] > So does anyone thing that creating a easily > parsable list with the state of the current tests is this > a reasonable thing to do, and would creating a simple > file in each /tests directory with the information be > good enough? If so, I can add one to my next test, and > update it with what I've done so far. I don't think you want a separate list for each test. Hmm, or OTOH, if you want that, then make sure to have a unique file name, e.g. mytest.testlist. Then you could simply do find . -name "*.testlist"|xargs grep "TESTS: MyFunc" to search *all* list files check whether a particular function is being tested already. > In general, while Francois' presentation is a > good place to get started, I think it'd be a lot easier > if there was a document off of winehq with > recommendations on how to build, test, and document > tests. Lowering the difficulty threshold, is more likely > to draw more people to do so. Definitely. Creating such a document is on my ToDo list, but let me alter winebootup first to make it submittable ;-) -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://home.arcor.de/andi.mohr/
