Test Systems - Revision history

Matt Porter: /* Test Suites */

2013-02-15T01:19:23Z

‎Test Suites

Matt Porter: /* Test Automation Tools */

2013-02-15T01:17:23Z

‎Test Automation Tools

Tim Bird at 19:16, 25 April 2012

2012-04-25T19:16:11Z

Tim Bird at 19:15, 25 April 2012

2012-04-25T19:15:03Z

Rostedt at 22:35, 12 April 2011

2011-04-12T22:35:06Z

Rostedt: Added a pointer to the ktest.pl sample config file

2011-04-12T21:00:56Z

Added a pointer to the ktest.pl sample config file

Hugo303: /* Static Analysis */

2009-05-11T20:07:08Z

‎Static Analysis

Nagano: Added "Bug tracking systems" section.

2008-11-07T11:53:07Z

Added "Bug tracking systems" section.

TimBird at 21:19, 25 June 2008

2008-06-25T21:19:52Z

TimBird at 21:19, 25 June 2008

2008-06-25T21:19:27Z

← Older revision		Revision as of 01:19, 15 February 2013
Line 18:		Line 18:

	* [http://ltp.sourceforge.net/ Linux Test Project]		* [http://ltp.sourceforge.net/ Linux Test Project]
		+	* [http://processors.wiki.ti.com/index.php/LTP-DDT LTP-DDT]

	=== Static Analysis ===		=== Static Analysis ===

@@ Line 7: / Line 7: @@
 * [http://test.kernel.org/autotest Autotest]
 * [https://testing.108.redhat.com/ Red Hat Test Project]
 * [[Ktest]] Automate kernel testing

@@ Line 6: / Line 6: @@
 === Test Automation Tools ===
- * [http://test.kernel.org/autotest Autotest]
+* [http://test.kernel.org/autotest Autotest]
- * [https://testing.108.redhat.com/ Red Hat Test Project]
+* [https://testing.108.redhat.com/ Red Hat Test Project]
- * [[Ktest]] Automate kernel testing
+* [[Ktest]] Automate kernel testing
- * Paper on finding bugs in Unix programs using random input: http://ftp.cs.wisc.edu/paradyn/technical_papers/fuzz.pdf
 === Test Suites ===
- * [http://ltp.sourceforge.net/ Linux Test Project]
+* [http://ltp.sourceforge.net/ Linux Test Project]
 === Static Analysis ===
- * [http://tree.celinuxforum.org/CelfPubWiki/Sparse Sparse]
+* [http://tree.celinuxforum.org/CelfPubWiki/Sparse Sparse]
- * [http://smatch.sourceforge.net/ Smatch]
+* [http://smatch.sourceforge.net/ Smatch]
- * [http://clang.llvm.org/StaticAnalysis.html clang]
+* [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 ===

@@ Line 9: / Line 9: @@
   * [https://testing.108.redhat.com/ Red Hat Test Project]
   * [[Ktest]] Automate kernel testing
 === Test Suites ===

@@ Line 8: / Line 8: @@
   * [http://test.kernel.org/autotest Autotest]
   * [https://testing.108.redhat.com/ Red Hat Test Project]
-  * [http://git.kernel.org/?p=linux/kernel/git/rostedt/linux-2.6-ktest.git;a=blob_plain;f=tools/testing/ktest/sample.conf;hb=HEAD ktest.pl Automate kernel testing]
+  * [[Ktest]] Automate kernel testing
 === Test Suites ===

← Older revision		Revision as of 11:53, 7 November 2008
Line 36:		Line 36:
	- test results matrix is available here:		- test results matrix is available here:
	- 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
		+
		+	== 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 ===
		+
		+	* [http://trac.edgewall.org/ Trac ] - Web-based software project management and bug/issue tracking system.
		+	* [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.
		+	* [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]

@@ Line 25: / Line 25: @@
 * 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 ===
 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/

@@ Line 1: / Line 1: @@
 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 ==
-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
-As a result of the meeting, a mailing list and wiki were created.
+=== Test Suites ===
-These resources are intended to be used to coordinate the efforts
-of the disparate testing projects in Linux. The list info is at:
-https://lists.osdl.org/mailman/listinfo/test-tools
-The wiki is at:
+ * [http://ltp.sourceforge.net/ Linux Test Project]
-http://developer.osdl.org/dev/test_tools/index.php/Main_Page
-== automated kernel compilation tests ==
+=== Static Analysis ===
 Here are some locations where automated tests of kernel compilation can be viewed:
 * 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
-It is preserved here only temporarily. (TRB - Aug, 2006)
+=== Kautobuild ==
 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