summaryrefslogtreecommitdiffstats
path: root/llvm/lib/CodeGen/StackSlotColoring.cpp
diff options
context:
space:
mode:
authorJohnny Chen <johnny.chen@apple.com>2010-06-25 21:14:08 +0000
committerJohnny Chen <johnny.chen@apple.com>2010-06-25 21:14:08 +0000
commita765c28db3199f9511e1206d1addc3621d688cff (patch)
treebbb886478a0e2654c24117fa3e4d089b10fc24bc /llvm/lib/CodeGen/StackSlotColoring.cpp
parent07b0a6e4d639f365114cd7d23a193a8450263724 (diff)
downloadbcm5719-llvm-a765c28db3199f9511e1206d1addc3621d688cff.tar.gz
bcm5719-llvm-a765c28db3199f9511e1206d1addc3621d688cff.zip
A simple testing framework for lldb using python's unit testing framework.
Tests for lldb are written as python scripts which take advantage of the script bridging provided by LLDB.framework to interact with lldb core. A specific naming pattern is followed by the .py script to be recognized as a module which implements a test scenario, namely, Test*.py. To specify the directories where "Test*.py" python test scripts are located, you need to pass in a list of directory names. By default, the current working directory is searched if nothing is specified on the command line. An example: [14:10:20] johnny:/Volumes/data/lldb/svn/trunk/test $ ./dotest.py -v example test_choice (TestSequenceFunctions.TestSequenceFunctions) ... ok test_sample (TestSequenceFunctions.TestSequenceFunctions) ... ok test_shuffle (TestSequenceFunctions.TestSequenceFunctions) ... ok ---------------------------------------------------------------------- Ran 3 tests in 0.000s OK llvm-svn: 106890
Diffstat (limited to 'llvm/lib/CodeGen/StackSlotColoring.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud