Difference between revisions of "Test Systems"

From eLinux.org
Jump to: navigation, search
m (Bot (Edward's framework))
 
(9 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 
Here is a quick list of different test systems (and test projects) for Linux:
 
Here is a quick list of different test systems (and test projects) for Linux:
  
This information has also been posted to the OSDL test-tools wiki.
+
== Test Projects ==
 +
Clearly, a number of open source projects in this realm exist.  This page intends to collect descriptions and links to these projects
  
See: http://developer.osdl.org/dev/test_tools/index.php/Test_Projects
+
=== Test Automation Tools ===
  
There was a testing summit held at [[Linux World]] in San Francisco in August of 2006.
+
* [http://test.kernel.org/autotest Autotest]
The minutes from the meeting are at:
+
* [https://testing.108.redhat.com/ Red Hat Test Project]
http://lists.osdl.org/pipermail/test-tools/2006-August/000000.html
+
* [[Ktest]] Automate kernel testing
  
As a result of the meeting, a mailing list and wiki were created.
+
=== Papers on testing ===
These resources are intended to be used to coordinate the efforts
+
* Paper on finding bugs in Unix programs using random input: http://ftp.cs.wisc.edu/paradyn/technical_papers/fuzz.pdf
of the disparate testing projects in Linux. The list info is at:
+
https://lists.osdl.org/mailman/listinfo/test-tools
+
  
The wiki is at:
+
=== Test Suites ===
http://developer.osdl.org/dev/test_tools/index.php/Main_Page
+
  
 +
* [http://ltp.sourceforge.net/ Linux Test Project]
  
== old page content ==
+
=== Static Analysis ===
This content was moved to the OSDL test-tools wiki at:
+
http://developer.osdl.org/dev/test_tools/index.php/Test_Projects
+
  
It is preserved here only temporarily. (TRB - Aug, 2006)
+
* [http://tree.celinuxforum.org/CelfPubWiki/Sparse Sparse]
 +
* [http://smatch.sourceforge.net/ Smatch]
 +
* [http://clang.llvm.org/StaticAnalysis.html clang]
  
 +
== Automated kernel compilation results ==
 +
Here are some locations where automated tests of kernel compilation can be viewed:
 +
 +
=== L4X ===
 +
 +
* http://l4x.org/k/ - Jan Dittmer's page showing the build status and kernel size of the defconfigs of many architectures.  Running since 2004 or 2005
 +
 +
=== Kautobuild ===
 +
Kautobuild is Simtec's automated system to build and store results for ARM and MIPS platforms, for every kernel version.  It uses defconfigs for multiple boards, and reports compile errors/warnings, module size, kernel size etc.
 +
* Kautobuild for ARM - http://armlinux.simtec.co.uk/kautobuild/
 +
* mail archive version of results is at: http://lists.simtec.co.uk/pipermail/kautobuild/
 +
* Article about the Simtel site is at: http://www.linuxdevices.com/news/NS4646877354.html (2006)
 +
 +
=== ABAT ===
 
ABAT - https://sourceforge.net/projects/abat/
 
ABAT - https://sourceforge.net/projects/abat/
 
  - does a download/build/boot regression test for several mainline kernel trees, as soon as new versions are available
 
  - does a download/build/boot regression test for several mainline kernel trees, as soon as new versions are available
Line 29: Line 42:
 
     - http://ftp.kernel.org/pub/linux/kernel/people/mbligh/abat/regression_matrix.html
 
     - http://ftp.kernel.org/pub/linux/kernel/people/mbligh/abat/regression_matrix.html
  
Linux Test Project
+
== Bug tracking system ==
- http://ltp.sourceforge.net/
+
 
 +
A '''bug tracking system''' is a software application that is designed to help quality assurance and computer programmers keep track of reported software bugs in their work.
 +
 
 +
Many bug-tracking systems, such as those used by most open source software projects, allow users to enter bug reports directly. Other systems are used only internally in a company or organization doing software development. Typically bug tracking systems are integrated with other software project management applications.
 +
 
 +
Having a bug tracking system is extremely valuable in software development, and they are used extensively by companies developing software products.
 +
 
 +
=== Components ===
 +
 
 +
A major component of a bug tracking system is a database that records facts about known bugs. Facts may include the time a bug was reported, its severity, the erroneous program behavior, and details on how to reproduce the bug; as well as the identity of the person who reported it and any programmers who may be working on fixing it.
 +
 
 +
Typical bug tracking systems support the concept of the life cycle for a bug which is tracked through status assigned to the bug. A bug tracking system should allow administrators to configure permissions based on status, move the bug to another status, or delete the bug. The system should also allow administrators to configure the bug statuses and to what status a bug in a particular status can be moved to.
 +
 
 +
=== Usage ===
  
CELF's Proposed Test Lab
+
In a corporate environment, a bug-tracking system may be used to generate reports on the productivity of programmers at fixing bugs. However, this may sometimes yield inaccurate results because different bugs may have different levels of severity and complexity. The severity of a bug may not be directly related to the complexity of fixing the bug. There may be different opinions among the managers and architects.
  - [[Open Test Lab]]
+
  
[[K Auto Build]]  - http://armlinux.simtec.co.uk/index.html
+
A ''local bug tracker (LBT)'' is usually a computer program used by a team of application support professionals to keep track of issues communicated to software developers. Using an LBT allows support professionals to track bugs in their "own language" and not the "language of the developers." In addition, LBT use allows a team of support professionals to track specific information about users who have called to complain that may not always be needed in the actual development queue (thus, there are two tracking systems when an LBT is in place.)
  - [[KAuto Build]] project for ARM architectures
+
  - Article about the site is at: http://www.linuxdevices.com/news/NS4646877354.html
+
  
There was a testing summit held
+
=== External links ===
  
I wanted to report that there was a testing summit held at
+
* [http://trac.edgewall.org/ Trac ] - Web-based software project management and bug/issue tracking system.
[[Linux World]] in San Francisco a few weeks ago. I represented
+
* [http://www.bugzilla.org/ Bugzilla ] - Bug tracking used by the Mozilla projects. Inherently web-based, written in Perl , and uses MySQL as its database back-end. Open-Source.
the CELF test lab effort at the meeting.
+
* [http://www.bugreport.ir/? Bugreport is a place to publish the security advisories ]
 +
* [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to Report Bugs Effectively]

Revision as of 19:16, 25 April 2012

Here is a quick list of different test systems (and test projects) for Linux:

Test Projects

Clearly, a number of open source projects in this realm exist. This page intends to collect descriptions and links to these projects

Test Automation Tools

Papers on testing

Test Suites

Static Analysis

Automated kernel compilation results

Here are some locations where automated tests of kernel compilation can be viewed:

L4X

  • http://l4x.org/k/ - Jan Dittmer's page showing the build status and kernel size of the defconfigs of many architectures. Running since 2004 or 2005

Kautobuild

Kautobuild is Simtec's automated system to build and store results for ARM and MIPS platforms, for every kernel version. It uses defconfigs for multiple boards, and reports compile errors/warnings, module size, kernel size etc.

ABAT

ABAT - https://sourceforge.net/projects/abat/

- does a download/build/boot regression test for several mainline kernel trees, as soon as new versions are available
- test results matrix is available here:
   - http://ftp.kernel.org/pub/linux/kernel/people/mbligh/abat/regression_matrix.html

Bug tracking system

A bug tracking system is a software application that is designed to help quality assurance and computer programmers keep track of reported software bugs in their work.

Many bug-tracking systems, such as those used by most open source software projects, allow users to enter bug reports directly. Other systems are used only internally in a company or organization doing software development. Typically bug tracking systems are integrated with other software project management applications.

Having a bug tracking system is extremely valuable in software development, and they are used extensively by companies developing software products.

Components

A major component of a bug tracking system is a database that records facts about known bugs. Facts may include the time a bug was reported, its severity, the erroneous program behavior, and details on how to reproduce the bug; as well as the identity of the person who reported it and any programmers who may be working on fixing it.

Typical bug tracking systems support the concept of the life cycle for a bug which is tracked through status assigned to the bug. A bug tracking system should allow administrators to configure permissions based on status, move the bug to another status, or delete the bug. The system should also allow administrators to configure the bug statuses and to what status a bug in a particular status can be moved to.

Usage

In a corporate environment, a bug-tracking system may be used to generate reports on the productivity of programmers at fixing bugs. However, this may sometimes yield inaccurate results because different bugs may have different levels of severity and complexity. The severity of a bug may not be directly related to the complexity of fixing the bug. There may be different opinions among the managers and architects.

A local bug tracker (LBT) is usually a computer program used by a team of application support professionals to keep track of issues communicated to software developers. Using an LBT allows support professionals to track bugs in their "own language" and not the "language of the developers." In addition, LBT use allows a team of support professionals to track specific information about users who have called to complain that may not always be needed in the actual development queue (thus, there are two tracking systems when an LBT is in place.)

External links