From: Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>
To: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [RFC] LTP Test Writing Guidelines
Date: Thu, 12 Dec 2013 10:30:07 +0400 [thread overview]
Message-ID: <52A957EF.7040003@oracle.com> (raw)
In-Reply-To: <20131211151928.GA30754@rei.Home>
On 12/11/2013 07:19 PM, chrubis@suse.cz wrote:
> Good news everyone!
>
> As number of contributors grows I've finally started to address our lack
> of documentation. I've written down a short introduction on how to write
> a LTP test. It's intended to cover just enough so that you can write a
> reasonable LTP testcase without any prior knowledge as well as to codify
> some of the rules we formed but were not written down till now.
>
> The text is attached as an asciidoc formatted plaintext and can be
> viewed in html form at [1].
>
> The attached text is a draft and it's likely that there are mistakes or
> important things missing. For example, as far as I know, we do not have
> a uniform coding style for shell scripts nor clear documentation for the
> shell LTP library functions, this should be ideally addressed as well.
>
> As usuall comments and patches are welcome ;).
Fantastic work! :)
Thank you.
Maybe add here a notice about performing a cleanup (in a separate patch)
before doing any "serious" modifications of the old test cases?
Since there are many such "old-style" test cases in LTP, these
situations may happen regularly.
>
> [1] http://metan.ucw.cz/outgoing/LTP_Test_Writing_Guidelines.html
>
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
>
>
>
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
>
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2013-12-12 6:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 15:19 [LTP] [RFC] LTP Test Writing Guidelines chrubis
2013-12-12 6:30 ` Stanislav Kholmanskikh [this message]
2013-12-12 12:07 ` chrubis
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=52A957EF.7040003@oracle.com \
--to=stanislav.kholmanskikh@oracle.com \
--cc=ltp-list@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.