From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: rohit verma <rohit.170309@gmail.com>
Cc: Mike Frysinger <vapier@gentoo.org>, ltp-list <ltp-list@lists.sf.net>
Subject: Re: [LTP] Reg: Script to extract description of test case from LTPROOT/doc/testcases/*.txt files
Date: Wed, 27 May 2009 19:53:06 +0530 [thread overview]
Message-ID: <1243434187.10447.15.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <d51f89b0905270018u1b447334qf38528f8dc0ed7aa@mail.gmail.com>
On Wed, 2009-05-27 at 00:18 -0700, rohit verma wrote:
> Hi Subrata,
>
> As the purpose of this document is to brief the description of each
> test case to user. I feel that your format would decrease the
> readability in document .
>
> So should we include following tags "test_location",
> "test_cmdfile_name", "test_cmdfile_entry",
> "Execute_through_commandline", "Execute_through_runltp". or only
> description tag would be sufficient.
Fine then, but i would insist you to include "testname" &
"test_location" apart from "test_description".
Regards--
Subrata
>
> Regards,
> rohit
>
>
> On Tue, May 26, 2009 at 5:22 AM, Subrata Modak
> <subrata@linux.vnet.ibm.com> wrote:
> > 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
> >> <subrata@linux.vnet.ibm.com> wrote:
> >> > Hi Rohit,
> >> >
> >> > On Mon, 2009-05-18 at 19:21 +0800, CAI Qian wrote:
> >> >> From: rohit verma <rohit.170309@gmail.com>
> >> >> 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 <caiqian@cclom.cn> wrote:
> >> >> >
> >> >> >> From: rohit verma <rohit.170309@gmail.com>
> >> >> >> 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 as they present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-05-27 14:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d51f89b0905130216h36e32efbwf48f241f2d961a0a@mail.gmail.com>
[not found] ` <20090513.225510.104053150.caiqian@cclom.cn>
[not found] ` <d51f89b0905180455w514b014boedb4670610987533@mail.gmail.com>
[not found] ` <20090518.192133.233689723.caiqian@cclom.cn>
2009-05-19 10:31 ` [LTP] Reg: Script to extract description of test case from LTPROOT/doc/testcases/*.txt files Subrata Modak
2009-05-26 4:40 ` rohit verma
2009-05-26 12:22 ` Subrata Modak
2009-05-27 7:18 ` rohit verma
2009-05-27 14:23 ` Subrata Modak [this message]
2009-06-04 9:27 ` Subrata Modak
[not found] ` <d51f89b0906040312y69332585m1566cd8f922b62cf@mail.gmail.com>
[not found] ` <1244112148.4879.19.camel@subratamodak.linux.ibm.com>
[not found] ` <d51f89b0906150141j21908ba5s377289d0db51fa98@mail.gmail.com>
[not found] ` <1245346284.5041.31.camel@subratamodak.linux.ibm.com>
2009-06-19 6:30 ` rohit verma
2009-06-23 14:50 ` Subrata Modak
2009-06-06 13:09 CAI Qian
-- strict thread matches above, loose matches on Subject: below --
2009-06-06 13:44 CAI Qian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1243434187.10447.15.camel@subratamodak.linux.ibm.com \
--to=subrata@linux.vnet.ibm.com \
--cc=ltp-list@lists.sf.net \
--cc=rohit.170309@gmail.com \
--cc=vapier@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox