1. 06 Jul, 2001 2 commits
  2. 03 Jul, 2001 1 commit
  3. 02 Jul, 2001 2 commits
    • Christopher Alfeld's avatar
      Added description of files created. · a8fcb408
      Christopher Alfeld authored
    • Christopher Alfeld's avatar
      Reworked tbtest to support a more interactive approach. To do a full test · 4c9e4ebb
      Christopher Alfeld authored
      run do:
      	../testbed/testsuite/tbtest run tbdb frontend
      but you could also something like do:
      	../testbed/testsuite/tbtest init tbdb
      	../testbed/testsuite/tbtest test frontend
      	# notice that sharkshelf test is broken.
      	# make changes
      	../testbed/testsuite/tbtest/single frontend sharkshelf
      	# note still broken
      	# make more changes
      	../testbed/testsuite/tbtest/single frontend sharkshelf
      	# note fixed.
      Also added a -leavedb command which can be used in conjunction with single
      to debug individual tests.  It prevents the removal of the test DB upon
  4. 29 Jun, 2001 1 commit
  5. 28 Jun, 2001 1 commit
  6. 27 Jun, 2001 1 commit
    • Christopher Alfeld's avatar
      First version of the testing software. · d138f5cc
      Christopher Alfeld authored
      This is a functional check in.  To run the testing software do
      something like:
      	1. mkdir ~/testbed_test
      	2. cd ~/testbed_test
      	3. ~/testbed/testsuite/tbtest tbdb frontend
      	1. mkdir ~/testbed_test
      	2. cd ~/testbed/testsuite
      	3. tbtest -path ~/testbed_test tbdb frontend
      A lot of stuff will be placed in testbed_test, including a configured
      tree, an installed tree, a couple versions of the DB, and a whole
      bunch of log files.
      Interesting log files:
      The main log file of interest is test.log which is a copy of the
      output of tbtest.  The other log files are only useful if things fail.
      Usually the fail message will include which log file to look in.  Log
      files for tests are in tests/<test>/test.log .
      What's missing:
      1. Lot's of tests.  There's only one currently.
      2. DB checking support.
      3. A real README.  The current one is mainly a bunch of notes for the
      real README.
      4. Full support.  The current setup is only for testing the frontend.
      Although there are some hooks for supporting full testing runs a lot
      still needs to be done.