volatility trunk testsuite errors

[GoogleCodeExporter]

What steps will reproduce the problem?
C:\Users\dmk\volatility>python vol.py -f ..\win7sp1x64.dmp --profile=Win7SP1x64 
-v testsuite
Volatile Systems Volatility Framework 2.1_alpha
Executing dlldump
Executing vadtree
Error running userassist - option -o/--hive-offset: conflicting option 
string(s): -o
Executing procmemdump
Error running lsadump - option -s/--sec-offset: conflicting option string(s): -s
Executing moddump
Executing handles
Error running handles - maximum recursion depth exceeded while calling a Python 
object
Executing dlllist
Executing memdump
Error running memdump - local variable 'flat_x' referenced before assignment
Executing vadinfo
Executing procexedump
Error running hashdump - option -s/--sam-offset: conflicting option string(s): 
-s
Error running imagecopy - option -b/--blocksize: conflicting option string(s): 
-b
Executing vadwalk
Executing memmap
Error running memmap - local variable 'flat_x' referenced before assignment
Executing vaddump
Executing pslist
Executing getsids
Error running strings - option -s/--string-file: conflicting option string(s): 
-s

C:\Users\dmk\volatility>

What version of the product are you using? On what operating system?
svn trunk
win7 sp1 x64

Original issue reported on code.google.com by moltes...@gmail.com on 12 Feb 2012 at 7:50

[GoogleCodeExporter]

The testsuite plugin is not well supported.  Downgrading this to a low priority 
issue, and assigning it to the testsuite author.

Original comment by mike.auty@gmail.com on 12 Feb 2012 at 8:54

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Test suite has been deprecated from trunk. It is actually impossible to have a 
reliable test suite within volatility, without the ability to use volatility as 
a framework since there are conflicting command line options for running each 
plugin. These problems can be seen in the output above.

The test suite is currently only supported in the new scudette branch where its 
easy to use volatility as a framework and we can run multiple unit test, and 
end to end tests on a sample image corpus.

Original comment by scude...@gmail.com on 22 Mar 2012 at 1:13

• Changed state: WontFix