public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: chrubis@suse.cz
To: "Bola,
	Pradeep (EXT-Tata Consultancy Ser - US/Arlington Heights)"
	<pradeep.bola.ext@nsn.com>
Cc: "ltp-list@lists.sourceforge.net" <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] Support needed for LINUX POSIX compliance test
Date: Wed, 19 Feb 2014 15:13:57 +0100	[thread overview]
Message-ID: <20140219141356.GB2138@rei> (raw)
In-Reply-To: <D29743B70598864B880A3BE89C6E96946FEA75@USCHMBX004.nsn-intra.net>

Hi!
> We are planning to use LTP for doing POSIX compliance test for one of our project.
> LTP covers most of the LINUX POSIX functions.
> 
> But I am unable to test few of the stdio POSIX functionalities.
> Few of POSIX functions: atoi, atol, calloc, malloc, free, errno, scanf, sprints, system etc .

I've looked around and indeed there are no tests designed specially for
these calls. But quite franky if any of these functions are broken quite
a lot of tests will fail because these functions are used in the tests
and system extensivelly. So from a functional standpoint these are not
that important to test (we don't have 100% coverage and there parts of
the system that are, in my opinion, more important).

> Can you please let me know how to verify these stdio commands using LTP?

If you really need tests designed specially for these functions you can
write them yourself and LTP community will be happy to include them.

Or You can look into tests embedded in glibc, there should be basic
testcases for the stdio streams etc.

> Also need support for testing POSIX compliance for few of the LINUX commands.
> POSIX Linux commands: arp, cd, mv, date, echo, file, gdb, kill etc.

Same here, if you need them you can write them yourself. I can give you
hand in integrating them into LTP.

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2014-02-19 14:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19  2:33 [LTP] Support needed for LINUX POSIX compliance test Bola, Pradeep (EXT-Tata Consultancy Ser - US/Arlington Heights)
2014-02-19 14:13 ` chrubis [this message]
2014-03-10  0:16 ` Mike Frysinger

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=20140219141356.GB2138@rei \
    --to=chrubis@suse.cz \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=pradeep.bola.ext@nsn.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