public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: "Li, Jin" <Jin.Li@windriver.com>
To: Rejish Rajagopala <rejish.rajagopala@sasken.com>
Cc: "ltp-list@lists.sourceforge.net" <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] Executing LTP one test at a time
Date: Tue, 17 Jul 2012 09:21:11 +0800	[thread overview]
Message-ID: <5004BE07.5070400@windriver.com> (raw)
In-Reply-To: <6F91E0FFDA542149961F7BDED2D2B94B568E0DED0D@EXGMBX01.sasken.com>

Rejish,

Just check the help command :

runltp -h

You will find that the command "runltp -s PATTERN" is what you want 
though it's not very perfect.

Hope this will help

Regards,

Jin




On 07/16/2012 09:05 PM, Rejish Rajagopala wrote:
> Hi,
>
> Please let me know is there way to execute single test using runltp script.
>
> That is, I know we can execute user defined test cases through the command "runltp -f pty" but  is there a way so that I can run ltp like "runltp pty01" that is the test case directly through runltp script.
>
>
> Regards,
> Rejish
>
> SASKEN BUSINESS DISCLAIMER: This message may contain confidential, proprietary or legally privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Communication Technologies Limited ("Sasken") unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email.
> Read Disclaimer at http://www.sasken.com/extras/mail_disclaimer.html
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2012-07-17  1:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16 13:05 [LTP] Executing LTP one test at a time Rejish Rajagopala
2012-07-17  1:21 ` Li, Jin [this message]
2012-07-17  2:48 ` preeti

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=5004BE07.5070400@windriver.com \
    --to=jin.li@windriver.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=rejish.rajagopala@sasken.com \
    /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