![[Home]](/images/common/nav_home0.gif){kind=small}
![[Search]](/images/common/nav_search0.gif){kind=small}
![[How to Buy]](/images/common/nav_sales0.gif){kind=small}
![[Products]](/images/common/nav_prod0.gif){kind=small}
![[Solutions]](/images/common/nav_solutions0.gif){kind=small}
![[Developers]](/images/common/nav_dev1.gif){kind=small}
![[Services and Support]](/images/common/nav_support0.gif){kind=small}
![[Serious Fun]](/images/common/nav_fun0.gif){kind=small}
 |
|
|
 About this site |
||
| Linux Test Project |
||
|
Overview News FAQ Mailing List How to Contribute Source Tree Download License |
||
| SGI Open Source |
||
|
Project List
|
||
LTP FAQ
What is LTP ?
There is no such thing as a perfect test base. It's only useful if it keeps up with new and
changing functionality, and if it actually gets used.
A problem that needs to be
addressed is how to store different command lines and determining when to run them. An example is, should
a bigmem test be run on a 128Mb system?
Linux aready has a successful testing model. How will this project benefit Linux furthur?
What is in the LTP, so far.
How do I build this?
How do I run this? How does it work?
What is LTP ?
LTP is the Linux Test Project. LTP is a project that aims to develop
a set of tools and tests to verify the functionality and
stability of the Linux kernel (including regression tests). We hope this will
support Linux development by making unit testing more complete and minimizing user impact
by building a barrier to keep bugs from making it to the user.
Linux aready has a successful testing model. How will this project benefit Linux furthur?
The Linux development community utilizes two important (some would argue most important)
testing techniques in it's normal operations: Design and Code Inspections. The intent of LTP is
to support this by giving developers an ever growing set of tools to help identify any
operational problems in their code that may be missed by human review.
One of the toughest categories of problems to catch with inspection is that of interaction
of features. With a continuously improving set of tests and tools, developers can get
an indication of whether their changes may have broken some other functionality.
What is in the LTP, so far?
The first release of code from SGI for LTP was a set of tools for testing file systems.
Since that first release, a group of tests we call Quickhit tests have been released.
These are simple tests aimed at running through a few execution paths in a number of system calls.
Watch the news link for updates on the content of the LTP releases.
How do I build this?
We've made a decision to not put effort into a grand build process in favor of a
minimal makefile approach. We did this becuase the project is just starting and we don't
want to impose and "SGI approach" in favor of a more open source approach decided more by
open source contributors. For now, from the root of the tree, a simple 'make' should do
it. Send your build errata to ltp@oss.sgi.com.
How do I run this? How does it work?
Currently, you can't really "run" this -- at least not in terms of a single starting command line.
Instead, LTP is made up of a number of individual test programs. These test programs usually test some
some portion of a feature's functionality. Mosts tests can be run without any command line options.
Others offer variable functionality specified from the command line.