On Mon, 2009-05-25 at 21:40 -0700, rohit verma wrote: > Hi Subrata, > > I request you to finalize the format of the documentation ASAP.
I would like to see something like: <testname=abort(3)> <test_description="Basic test for abort(3)"> <\test_description> <test_location="ltp/testcases/kernel/syscalls/abort/abort01.c"> <\test_location> <test_cmdfile_name="ltp/runtest/syscalls"> <\test_cmdfile_name> <test_cmdfile_entry="abort01 ulimit -c 1024;abort01"> <\test_cmdfile_entry> <Execute_through_commandline="ulimit -c 1024; ./ltp/testcases/bin/abort01"> <\Execute_through_commandline> <Execute_through_runltp="./runltp -s abort01"> <\Execute_through_runltp> <\testname> The basic idea is to include all important information as we can when we are doing some patching on this. Let me know how others feel, and how we can achieve this. Regards-- Subrata > > Ltp-list : Please provide the inputs regarding the text documentation format. > > Regards, > rohit > > On Tue, May 19, 2009 at 3:31 AM, Subrata Modak > <[email protected]> wrote: > > Hi Rohit, > > > > On Mon, 2009-05-18 at 19:21 +0800, CAI Qian wrote: > >> From: rohit verma <[email protected]> > >> Subject: Re: Reg: Script to extract description of test case from > >> LTPROOT/doc/testcases/*.txt files > >> Date: Mon, 18 May 2009 04:55:54 -0700 > >> > >> > Dear Subrata/Qian, > >> > > >> > I am trying to develop script which would extracts description > >> > information > >> > about user required test case from LTPROOT/doc/testcases/ folder. > >> > > >> > So to make the description text file as standard file, can we represent > >> > the > >> > description as mentioned below. > >> > > >> > For example in syscalls category: > >> > > >> > Currently available format of description in LTP as follows. > >> > > >> > abort01 > >> > Basic test for abort(3). > >> > > >> > accept01 > >> > Verify that accept() returns the proper errno for various failure > >> > cases > >> > > >> > > >> > To make it in consistent way, description should be enclosed by > >> > executables > >> > as follows. > >> > > >> > <abort01> > >> > Basic test for abort(3). > >> > <\abort01> > >> > > >> > <accept01> > >> > Verify that accept() returns the proper errno for various failure > >> > cases > >> > <\accept01> > >> > > >> > Please confirm if this format is O.K or suggest any other format by > >> > which we > >> > can easily parse the test cases and extracts the description. > > > > Itś always great to see somebody working on LTP documentation. So, lets > > ask the community also for their opinion as well. Can we also include > > some more tags for more descriptive info ? > > > > Regards-- > > Subrata > > > >> > > >> > >> Looks good for me. > >> > >> CAI Qian > >> > >> > If this format is O.K , I would send the patch for those text files > >> > > >> > Regards, > >> > Rohit > >> > > >> > > >> > > >> > On Wed, May 13, 2009 at 7:55 AM, CAI Qian <[email protected]> wrote: > >> > > >> >> From: rohit verma <[email protected]> > >> >> Subject: Reg: Script to extract description of test case from > >> >> LTPROOT/doc/testcases/*.txt files > >> >> Date: Wed, 13 May 2009 02:16:57 -0700 > >> >> > >> >> > Dear Subrata/qian, > >> >> > > >> >> > As if we run LTP testcases, nowhere LTP test suite populates the > >> >> > description of testcases (either in .log, .output, .HTML or .failed > >> >> > test cases files). > >> >> > > >> >> > Description of each test case in category wise is available in > >> >> > LTPROOT/doc/testcases folder. > >> >> > > >> >> > My Question : Is there any ready-made script available to extract the > >> >> > description of user required test case from above specified folder? > >> >> > > >> >> > If script is not available, could you suggest the direction to extract > >> >> > description of test cases. > >> >> > > >> >> > > >> >> > Regards, > >> >> > Rohit. > >> >> > >> >> Not I am aware of. Subrata or someone in the list might have some ideas > >> >> for you. > >> >> > >> >> CAI Qian > >> >> > > > > ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
