I find that our adaptors are named by different convention since they are developed by different developers. Shall we unify the name like "app_unit_test" for unit test adaptors and "app_scenario" for scenario test adaptors. I think this will make the user have a general idea for the adaptor.
2007/8/6, Alexey Varlamov <[EMAIL PROTECTED]>: > Hi Nadya, > > Wording certainly can be improved; feedback and suggestions are highly > appreciated. Thanks for volunteering! > > -- > Alexey > > 2007/8/6, Morozova, Nadezhda <[EMAIL PROTECTED]>: > > Hi all, > > Do you think we should port the dev-guide.txt doc to the website? If so, > > how can I help? > > > > Cheers, > > Nadya > > > > >-----Original Message----- > > >From: Tim Ellison [mailto:[EMAIL PROTECTED] > > >Sent: Friday, August 03, 2007 1:29 PM > > >To: [email protected] > > >Subject: Re: [build test] documentation > > > > > >Alexey Varlamov wrote: > > >> 2007/8/2, Tim Ellison <[EMAIL PROTECTED]>: > > >>> cool - this is going straight on my reading pile! Before I read it, > > may > > >>> I ask if this is appropriate material to convert to xml and move > > onto > > >>> the website? It would get better visibility there IMHO. > > >> > > >> This is certainly useful reading and worths to be published some day, > > >> but I'm not sure it should go onto the website as is. It would be > > nice > > >> to merge the dev-guide.txt and spec.txt, and maybe expand on some > > >> topics. OTOH, BTI is a work-in-progress at the moment, so we might > > not > > >> finish improving document soon enough :) > > > > > >ok -- and indeed you might get some more help working on the BTI if it > > >is documented for those of us that don't have the history. > > > > > >BTI is on my list of things I should know more about. At least how to > > >integrate an existing test suite into the framework like we have for > > >EUT/GUT etc. I'll read the doc and offer updates as I learn about it. > > > > > >Regards, > > >Tim > > > -- Sean Qiu
