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: Tue, 19 May 2009 16:01:25 +0530 [thread overview]
Message-ID: <1242729086.5961.43.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <20090518.192133.233689723.caiqian@cclom.cn>
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
> >>
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables
unlimited royalty-free distribution of the report engine
for externally facing server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next parent reply other threads:[~2009-05-19 10:31 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 ` Subrata Modak [this message]
2009-05-26 4:40 ` [LTP] Reg: Script to extract description of test case from LTPROOT/doc/testcases/*.txt files rohit verma
2009-05-26 12:22 ` Subrata Modak
2009-05-27 7:18 ` rohit verma
2009-05-27 14:23 ` Subrata Modak
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=1242729086.5961.43.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