Squeak
  links to this page:    
View this PageEdit this PageUploads to this PageHistory of this PageTop of the SwikiRecent ChangesSearch the SwikiHelp Guide
About the MagmaTester
Last updated at 8:48 pm UTC on 24 March 2009
MagmaTestCase and MagmaCollectionTester test most of the functionality of Magma. If you make any changes to Magma code, it is highly recommended that you run these test suites as a regression check.

They test Magma in a multi-user fashion via the Ma Armored Code framework, using multiple Squeak images that may run on the same or different computers. OSProcess is recommended if you want the convenience running the entire test suite with "one-click".

Then run the following:
  MagmaTestCase fullSuite maDebug

A warning message will appear describing what's about to happen. If present, OSProcess will be used to launch five images; "client1", "client2", "server", "server2" and "test-conductor".

On my circa-2004 laptop computer, the tests take over an hour to run.

More fundamental-level tests

Magma depends on the services of lower-level frameworks. These frameworks are assumed to work correctly for Magma to work correctly. Here are tests for the most critical supporting frameworks.

MaClientServerTester tests client-server module only, no Magma code is run.
  MaClientServerTester kickoff


The following are standard SUnit testcases, runnable from the SUnit Test Runner browser: