GitLab

Add test for pattern-match failure in do-notation

Update expected output

update expected output

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.

negated parameters fixed; should dsrun009 should pass now

Add test for correct 'negate' handling (currently an expected failure).

Move the unused binding test from deSugar to rename, and add another
case which currently fails to produce a warning (from Marcin).  This
test is a known failure at the moment.

Add irrefutable pattern test from the Hugs bugs list.

Add another missing warning test from Marcin

Add tests for the warning problems reported by Marcin earlier this week.

update expected output

Use makefiles in the subdirectories to ease running the test driver in
a subdirectory.  It can be run in the following ways:

 	make		-- run all the tests in the current directory
 	make verbose	-- as make test, but up the verbosity
 	make accept	-- run the tests, accepting the current output

and you can also set some variables on the command line, eg.

	make accept TESTS=arr001  -- accept an individual test
	make EXTRA_HC_OPTS='-v'   -- extra flags to the haskell compiler
	make CONFIG=<config>	  -- use a different test config

this will all go in the docs at some point.

Knock this into slightly better shape and bring over some more tests
from the old test suite.

Handy shell scripts for running tests.  Use either as ./run
or ./run testname(s)  (In general, ./run followed by any other
args you want to pass to the test driver).

Rename some functions used in vanilla-test.T to be more consistent/logical.

Update expected outputs.

Add deSugar tests.