racket/collects/tests/framework
Robby Findler 6f9bcf0001 Rackety
2010-12-31 09:58:54 -06:00
..
canvas.rkt
debug.rkt
exit.rkt
frame.rkt
framework-test avoid relying on bash 2010-08-25 17:17:01 -04:00
framework-test-engine Rename "collects/tests/mred" -> ".../gracket". 2010-05-17 01:44:27 -04:00
framework-test-engine.icns
framework-test-engine.rkt Rackety 2010-12-31 09:58:54 -06:00
group-test.rkt Rename "collects/tests/mred" -> ".../gracket". 2010-05-17 01:44:27 -04:00
handler-test.rkt A lot of "MrEd" -> "GRacket"s. 2010-05-16 23:46:05 -04:00
info.rkt
keys.rkt Adds auto-completion to LaTeX and TeX inspired keybindings 2010-11-02 22:34:05 -05:00
load.rkt
main.rkt Rackety 2010-12-31 09:58:54 -06:00
mem.rkt
panel-single.rkt moved interactive panel test into its own file 2010-12-31 09:58:53 -06:00
panel.rkt Rackety 2010-12-31 09:58:54 -06:00
pasteboard.rkt
prefs.rkt
README moved interactive panel test into its own file 2010-12-31 09:58:53 -06:00
scheme.rkt Adjusts the prompt handling so that it submits expressions that signal 2010-08-24 20:06:45 -05:00
search.rkt
test-suite-utils.rkt fixed up panel:dragable so that it actually does the right thing now 2010-12-31 09:58:51 -06:00
text.rkt
utils.rktl More "~n" -> "\n" changes 2010-08-26 12:11:00 -04:00

(#|
                      Framework Test Suite Overview

Each test will rely on the sucessfully completion of all of the ones
before it. In addition, all test suites rely on the sucessful
completion of the engine test suites and the mzscheme test suites.

All of these tests reside in PLTHOME/collects/tests/framework/

There will be a main mzscheme process which will start up a new gracket
as necessary for the test suites. Since some tests actually require
gracket to exit in order to pass, this governor is required.

To run a test use:

   framework-test <test.rkt> ...

where <test.rkt> is the name of one of the tests below.  Alternatively,
pass no command-line arguments to run all of the tests.

Some of the tests in this file are not yet present in the
testing directory. They are planned future expansions of
this test suite (and have been for some time....)

OS X: you will have to click on the newly started gracket
processes in the doc while the test suite runs or it will
signal failures when there aren't any.

- load: |# load.rkt #|

  | This tests that the advertised ways of loading the framework at
  | it's components all work.

- exit: |# exit.rkt #|

  | This tests that exit:exit really exits and that the exit callbacks
  | are actually run.

- preferences: |# prefs.rkt #|

  | This tests that preferences are saved and restored correctly, both
  | immediately and across reboots of gracket.


- individual object tests:

  | These tests are simple object creation and basic operations.
  | Each test assumes that the others pass; this may yield strange
  | error messages when one fails.

  - frames: |# frame.rkt #|
  - canvases: |# canvas.rkt #|
  - texts: |# text.rkt #|
  - pasteboards: |# pasteboard.rkt #|

- keybindings: |# keys.rkt #|

  | This tests the misc (non-scheme) keybindings

- searching: |# search.rkt #|

  | This tests the search results

- group tests: |# group-test.rkt #|

  | make sure that mred:the-frame-group records frames correctly.
  | fake user input expected.

- saving tests:

  | These tests will make sure that the usual checks against a user
  | losing their work are in place.

- scheme tests:

  | Tests the scheme: section

  |# scheme.rkt #|

- panel tests:

 |# panel.rkt #|

- |# (interactive #| tests

  | these tests require intervention by people. Clicking and whatnot

  - panel:single |# panel-single.rkt #|

  - garbage collection: |# mem.rkt #|

    | These tests will create objects in various configurations and
    | make sure that they are garbage collected

|#))