Changeset 27003 in project


Ignore:
Timestamp:
07/05/12 20:05:29 (9 years ago)
Author:
Mario Domenech Goulart
Message:

eggs tutorial (wiki): move "Testing your extension" to a "Tests" subsection. "Testing your extension" before "Additional files" doesn't really make sense, since salmonella depends on .setup/.meta files. Also remove redundant explanation on tests/run.scm

File:
1 edited

Legend:

Unmodified
Added
Removed
  • wiki/eggs tutorial

    r27002 r27003  
    2323if one of your exported toplevel identifiers clashes with an already existing definition.
    2424Modules also allow to export syntax definitions in a clean and easy-to-use way.
    25 
    26 === Testing your extension
    27 
    28 Create a {{tests}} directory in your egg tree and put your test code in a {{tests/run.scm}} file.  This file is used by chicken-install when called with the {{-test}} command line option and by [[http://tests.call-cc.org|the test infrastructure]] to run tests and report their status.
    29 
    30 {{tests/run.scm}} should exit zero when all tests pass or a non-zero value when some test fails.  If you are using the [[/egg/test|test egg]], you can use the {{test-exit}} procedure to properly report the test status.
    31 
    32 Before publishing your egg, it is recommended to run [[/egg/salmonella|salmonella]] on it to try to catch some common mistakes in advance.  Here's how you can do that:
    33 
    34   $ chicken-install salmonella # in case you don't have salmonella installed
    35   $ cd egg-dir # the directory where yor egg code is stored
    36   $ salmonella --this-egg
    37 
    38 Salmonella will report to the standard output a summary of the tests it performs.  It also generates a detailed log file containing all the data generated along the tests execution.  You can use {{salmonella-log-viewer}} to see details about the whole test procedure:
    39 
    40   $ salmonella-log-viewer salmonella.log
    41 
    42 See the [[/egg/salmonella|salmonella documentation]] for more information on how to test eggs.
    4325
    4426
     
    189171exit properly.
    190172
     173==== Testing your extension
     174
     175Before publishing your egg, it is recommended to run [[/egg/salmonella|salmonella]] on it to try to catch some common mistakes in advance.  Here's how you can do that:
     176
     177  $ chicken-install salmonella # in case you don't have salmonella installed
     178  $ cd egg-dir # the directory where yor egg code is stored
     179  $ salmonella --this-egg
     180
     181Salmonella will report to the standard output a summary of the tests it performs.  It also generates a detailed log file containing all the data generated along the tests execution.  You can use {{salmonella-log-viewer}} to see details about the whole test procedure:
     182
     183  $ salmonella-log-viewer salmonella.log
     184
     185See the [[/egg/salmonella|salmonella documentation]] for more information on how to test eggs.
     186
     187
    191188== Managing and hosting eggs
    192189
Note: See TracChangeset for help on using the changeset viewer.