Skip to content
  1. Sep 21, 2010
    • Johnny Chen's avatar
      Changed the order of two assignment stmts. · 958da040
      Johnny Chen authored
      llvm-svn: 114381
      958da040
    • Johnny Chen's avatar
      Added the capability to source the configFile specified via the "-c" option in · 209cdbef
      Johnny Chen authored
      order to customize the running of the test suite.  For the time being, the
      supported customizations are:
      
      o redirecting stdout and/or stderr
      o specifying a list of compilers to build the test programs
      o specifying a list of architectures to build the test programs for
      
      Also checked into the examples/test directory some example files which
      demonstrate the usage for the above customizations.
      
      $ ./dotest.py -v -c ~/.lldbtest-config persistent_variables
      $ cat ~/.lldbtest-config
      sys.stderr = open("/tmp/lldbtest-stderr", "w")
      sys.stdout = open("/tmp/lldbtest-stdout", "w")
      compilers = ["gcc", "llvm-gcc"]
      archs = ["x86_64", "i386"]
      $ cat /tmp/lldbtest-stderr
      ----------------------------------------------------------------------
      Collected 1 test
      
      
      Configuration: arch=x86_64 compiler=gcc
      test_persistent_variables (TestPersistentVariables.PersistentVariablesTestCase)
      Test that lldb persistent variables works correctly. ... ok
      
      ----------------------------------------------------------------------
      Ran 1 test in 1.397s
      
      OK
      
      Configuration: arch=x86_64 compiler=llvm-gcc
      test_persistent_variables (TestPersistentVariables.PersistentVariablesTestCase)
      Test that lldb persistent variables works correctly. ... ok
      
      ----------------------------------------------------------------------
      Ran 1 test in 1.282s
      
      OK
      
      Configuration: arch=i386 compiler=gcc
      test_persistent_variables (TestPersistentVariables.PersistentVariablesTestCase)
      Test that lldb persistent variables works correctly. ... ok
      
      ----------------------------------------------------------------------
      Ran 1 test in 1.297s
      
      OK
      
      Configuration: arch=i386 compiler=llvm-gcc
      test_persistent_variables (TestPersistentVariables.PersistentVariablesTestCase)
      Test that lldb persistent variables works correctly. ... ok
      
      ----------------------------------------------------------------------
      Ran 1 test in 1.269s
      
      OK
      $ cat /tmp/lldbtest-stdout
      $ 
      
      llvm-svn: 114380
      209cdbef
  2. Sep 20, 2010
  3. Sep 18, 2010
  4. Sep 16, 2010
  5. Sep 15, 2010
    • Johnny Chen's avatar
      Also added BuildAndIntegration to the directories to search for an existing · 73982b94
      Johnny Chen authored
      lldb.py module.  The priorities to search for are Debug, Release, then
      BuildAndIntegration.  You can always override this with a valid PYTHONPATH
      environment variable before running the test driver.
      
      For example:
      
      $ PYTHONPATH=/Find/My/LLDB/Module/Here ./dotest.py -v .
      
      Python runtime will try to locate the lldb.py module from
      /Find/My/LLDB/Module/Here first before trying the Debug, Release, and then
      BuildAndIntegration directories.
      
      llvm-svn: 113991
      73982b94
    • Johnny Chen's avatar
      Removed the expectedFailure decorator from test_with_dwarf_and_run_command() test case · 1aad5c61
      Johnny Chen authored
      as it now passes.  Added some extra tests to breakpoint_creation_by_filespec_python().
      
      More clarification for the "os command" output and error as defined in
      lldbtest.system() function.
      
      Cleaned up the option processing of the test driver (dotest.py) and fixed the comment
      about enabling gdb-remote logging.  Example:
      
      $ GDB_REMOTE_LOG=/tmp/log.txt ./dotest.py -v -t enum_types
      
      llvm-svn: 113868
      1aad5c61
  6. Sep 08, 2010
  7. Aug 31, 2010
  8. Aug 23, 2010
    • Johnny Chen's avatar
      Changed the keyword argument for runCmd()/expect() from 'verbose' to 'trace', · d0190a61
      Johnny Chen authored
      which, defaults to False, and if set to True, will trace lldb command execution
      and result.
      
      Added "-t" command option to the test driver dotest.py which sets the
      LLDB_COMMAND_TRACE environment variable to "YES" and as a result always turns on
      command tracing regardless of the 'trace' keyword argument to runCmd()/expect().
      
      llvm-svn: 111811
      d0190a61
  9. Aug 18, 2010
  10. Aug 17, 2010
  11. Aug 14, 2010
  12. Aug 10, 2010
  13. Aug 09, 2010
  14. Aug 07, 2010
  15. Aug 06, 2010
  16. Jul 03, 2010
  17. Jul 02, 2010
  18. Jun 30, 2010
  19. Jun 29, 2010
  20. Jun 26, 2010
  21. Jun 25, 2010
    • Johnny Chen's avatar
      A simple testing framework for lldb using python's unit testing framework. · a765c28d
      Johnny Chen authored
      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
      a765c28d
Loading