Skip to content
GitLab
Switch branch/tag
  1. 11 Feb, 2013 1 commit
  3. 25 Jan, 2013 1 commit
  5. 08 Oct, 2012 1 commit
  7. 18 Sep, 2012 1 commit
  9. 03 Sep, 2012 1 commit
  11. 20 Jul, 2011 1 commit
  13. 28 Jun, 2011 1 commit
  15. 13 May, 2011 2 commits
  17. 04 May, 2011 1 commit
  19. 16 Apr, 2011 1 commit
  21. 02 Apr, 2011 1 commit
  23. 06 Jul, 2010 1 commit
  25. 27 Feb, 2010 1 commit
  27. 14 Oct, 2009 1 commit
  29. 24 Aug, 2009 1 commit
  31. 19 Aug, 2009 1 commit
  33. 17 Jun, 2009 1 commit
  35. 09 Jun, 2009 1 commit
  37. 30 Jul, 2008 1 commit
  39. 21 Dec, 2007 1 commit
  41. 28 Nov, 2007 1 commit
  43. 06 Jun, 2006 1 commit
  45. 09 Jan, 2006 1 commit
  47. 09 Nov, 2004 1 commit
  49. 01 Jul, 2003 1 commit
  51. 05 Sep, 2002 1 commit
  53. 31 Jul, 2002 1 commit
    • simonmar's avatar
      [project @ 2002-07-31 14:24:18 by simonmar] · e5063a04
      simonmar authored 
      Revamp the testsuite framework.  The previous framework was an
experiment that got a little out of control - a whole new language
with an interpreter written in Haskell was rather heavyweight and left
us with a maintenance problem.

So the new test driver is written in Python.  The downside is that you
need Python to run the testsuite, but we don't think that's too big a
problem since it only affects developers and Python installs pretty
easily onto everything these days.

Highlights:

  - 790 lines of Python, vs. 5300 lines of Haskell + 720 lines of
    <strange made-up language>.

  - the framework supports running tests in various "ways", which should
    catch more bugs.  By default, each test is run in three ways:
    normal, -O, and -O -fasm.  Additionally, if profiling libraries
    have been built, another way (-O -prof -auto-all) is added.  I plan
    to also add a 'GHCi' way.

    Running tests multiple ways has already shown up some new bugs!

  - documentation is in the README file and is somewhat improved.

  - the framework is rather less GHC-specific, and could without much
    difficulty be coaxed into using other compilers.  Most of the
    GHC-specificness is in a separate configuration file (config/ghc).

Things may need a while to settle down.  Expect some unexpected
failures.
      e5063a04
  55. 20 Sep, 2001 1 commit
  57. 20 Jun, 2001 1 commit