2012 Summer Project Week:SelfTesting - Revision history

Pieper: /* Key Investigators */

2012-06-22T11:45:23Z

Key Investigators

Pieper: /* Key Investigators */

2012-04-26T19:29:42Z

Key Investigators

Pieper: /* Key Investigators */

2012-04-26T19:24:32Z

Key Investigators

Pieper: moved 2012 Winter Project Week:SelfTesting to 2012 Summer Project Week:SelfTesting: Misnamed

2012-04-26T19:16:16Z

moved 2012 Winter Project Week:SelfTesting to 2012 Summer Project Week:SelfTesting: Misnamed

Pieper: /* Key Investigators */

2012-04-26T18:31:24Z

Key Investigators

Pieper: /* Key Investigators */

2012-04-26T18:25:56Z

Key Investigators

Pieper: /* Key Investigators */

2012-04-26T18:25:29Z

Key Investigators

Pieper: Created page with 'NOTOC Image:PW-MIT2012.png|Projects List ==Key Investigators== * Isomics: Steve Pieper * Kitware: Jean-Christophe…'

2012-04-26T18:25:17Z

Created page with '__NOTOC__ <gallery> Image:PW-MIT2012.png|Projects List </gallery> ==Key Investigators== * Isomics: Steve Pieper * Kitware: Jean-Christophe…'

New page

__NOTOC__
<gallery>
Image:PW-MIT2012.png|[[2012_Summer_Project_Week#Projects|Projects List]]
</gallery>

==Key Investigators==
* Isomics: Steve Pieper
* Kitware: Jean-Christophe Fillion-Robin, Julien Finet, Benjamin Long
* BWH: Sonia Pujol

<div style="margin: 20px;">
<div style="width: 27%; float: left; padding-right: 3%;">

<h3>Objective</h3>
[http://en.wikipedia.org/wiki/Built-in_self-test BIST (built-in self-test)] is an important concept in delivery of high-reliability engineered systems. While Slicer and the packages in the NA-MIC Kit are fairly well tested by open source software standards, the focus has been almost exclusively on build-time testing. But this leaves out many important variables that can lead to user-level issues. A BIST should be runnable from the installed version of Slicer on the user's machine. Desirable features include:
* Ensure that packaging and installation have succeeded correctly, taking into account the variability of the user's platform (OS version, memory, graphics card, drivers, etc)
* Exactly recreate testing steps so that any user-level issues can be narrowed down (e.g. if a tool works on test data, but not on the user's data).
* Support testing in a continuous loop to look for memory corruption or leaks.

</div>

<div style="width: 27%; float: left; padding-right: 3%;">

<h3>Approach, Plan</h3>

Some desirable features of a solution:

* easy for developers to write tests that capture the full workflow
** distribution of tests as extensions as part of the debugging and support process
** integration with QtTesting framework to define tests 'by doing'
* same tests should be available in CTest and BIST (ideally this will happen automatically)
* interface features:
** should allow selection of all tests or a subset of tests
** should allow running in a loop
** should present a summary of success/failure
* (possible feature) dialog when slicer first installs that suggests running the tests
* (possible feature) integration of performance testing (e.g. render speed)
* (possible feature) integration with CDash so users can submit test results

</div>

<div style="width: 40%; float: left;">

<h3>Progress</h3>

* [https://github.com/pieper/Slicer/tree/1922-bist a prototype implementation as a scripted module] is being developed using a factory-style mechanism where modules can register self-tests with slicer that will then be optionally run as part of the self-testing process.
* The issue is being tracked as a [http://na-mic.org/Bug/view.php?id=1922 feature request in mantis]

</div>
</div>

<div style="width: 97%; float: left;">

==Delivery Mechanism==

This work will be delivered to the NA-MIC Kit as a (please select the appropriate options by noting YES against them below)

#ITK Module
#Slicer Module - YES
##Built-in - YES
##Extension -- commandline
##Extension -- loadable
#Other (Please specify)

==References==

</div>

@@ Line 50: / Line 50: @@
 * The issue is being tracked as a [http://na-mic.org/Bug/view.php?id=1922 feature request in mantis]
 * [https://github.com/pieper/Slicer/blob/7f43f0388a80735be5346b603b009f8d9a741e62/Modules/Scripted/EditorLib/Testing/ThresholdThreadingTest.py Example of a test]
 </div>

← Older revision		Revision as of 18:31, 26 April 2012
Line 24:		Line 24:

	<h3>Approach, Plan</h3>		<h3>Approach, Plan</h3>
		+
		+	The goal at project week is to discuss these issues and formulate a standard plan that can be used by all slicer developers.

	Some desirable features of a solution:		Some desirable features of a solution:

@@ Line 47: / Line 47: @@
 <h3>Progress</h3>
-* [https://github.com/pieper/Slicer/tree/1922-bist a prototype implementation as a scripted module] is being developed using a factory-style mechanism where modules can register self-tests with slicer that will then be optionally run as part of the self-testing process.
+* [https://github.com/pieper/Slicer/tree/1922-bist a prototype implementation as a scripted module] is being developed using a factory-style mechanism where modules can register self-tests with slicer that will then be optionally run as part of the self-testing process.  [https://github.com/pieper/Slicer/blob/75f79b165ac1f45571ae41c76e2b7d632d27853a/Modules/Scripted/Scripts/SelfTests.py Prototype scripted module]
 * The issue is being tracked as a [http://na-mic.org/Bug/view.php?id=1922 feature request in mantis]
 * [https://github.com/pieper/Slicer/blob/7f43f0388a80735be5346b603b009f8d9a741e62/Modules/Scripted/EditorLib/Testing/ThresholdThreadingTest.py Example of a test]

← Older revision	Revision as of 19:16, 26 April 2012
(No difference)

@@ Line 18: / Line 18: @@
 * Exactly recreate testing steps so that any user-level issues can be narrowed down (e.g. if a tool works on test data, but not on the user's data).
 * Support testing in a continuous loop to look for memory corruption or leaks.
 </div>
@@ Line 48: / Line 42: @@
 <div style="width: 40%; float: left;">
 <h3>Progress</h3>

2012 Summer Project Week:SelfTesting - Revision history

Pieper: /* Key Investigators */

Pieper: /* Key Investigators */

Pieper: /* Key Investigators */

Pieper: moved 2012 Winter Project Week:SelfTesting to 2012 Summer Project Week:SelfTesting: Misnamed

Pieper: /* Key Investigators */

Pieper: /* Key Investigators */

Pieper: /* Key Investigators */

Pieper: Created page with '__NOTOC__ Image:PW-MIT2012.png|Projects List ==Key Investigators== * Isomics: Steve Pieper * Kitware: Jean-Christophe…'

Pieper: Created page with 'NOTOC Image:PW-MIT2012.png|Projects List ==Key Investigators== * Isomics: Steve Pieper * Kitware: Jean-Christophe…'