Skip to content
This repository
branch: master

Dec 21, 2013

  1. Store the test in the appropriate package.

    Thomas M. Hermann authored

Dec 15, 2013

  1. Organization

    Thomas M. Hermann authored

Aug 24, 2013

  1. Store the test based on the SYMBOL-PACKAGE of the test name, not *PAC…

    …KAGE*.
    Thomas M. Hermann authored

Aug 01, 2013

  1. Correct error in parse-body that was discarding the test documentation.

    Thomas M. Hermann authored

Jun 10, 2013

  1. Fix issue 17 in remove-tags.

    Thomas M. Hermann authored

Apr 27, 2013

  1. Ignore CCL FASL files.

    Trim trailing white space.
    Thomas M. Hermann authored

Apr 22, 2013

  1. Remove redundant function print-warning.

    Thomas M. Hermann authored

Apr 18, 2013

  1. Ensure that a package object is used as the hash-key for tests and ta…

    …gs DB.
    Thomas M. Hermann authored
  2. Warn when there are no tests or tags defined for a package.

    Return NIL from functions that are returning lists of things.
    Thomas M. Hermann authored

Apr 02, 2013

  1. Use a function instead of a generic function to generate the failure …

    …instance.
    Thomas M. Hermann authored

Mar 18, 2013

  1. Version 0.9.5 README.

    Thomas M. Hermann authored
  2. Make the list of test names and tags optional.

     * remove-tests
     * tagged-tests
     * remove-tags
     * run-tests
     * run-tags
    Thomas M. Hermann authored

Mar 15, 2013

  1. Signal an error if no tests are defined in the package.

    Also clean up warning messages for test-documentation and test-code.
    Thomas M. Hermann authored

Mar 14, 2013

  1. Correctly quote name and use valid-test-name in define-test.

    Thomas M. Hermann authored
  2. Replace assert-class function with generic function record-failure.

    Better facilitates extensions.
    Thomas M. Hermann authored
  3. Replace assert-function with a generic function assert-result.

    Specialize on the type of assertion. This better facilitates extensions.
    Thomas M. Hermann authored
  4. Signal a type-error if anything besides a symbol is used for a test n…

    …ame.
    Thomas M. Hermann authored

Feb 11, 2013

  1. Update the README for version 0.9.4.

    Cover the new TAP features.
    Thomas M. Hermann authored

Feb 08, 2013

  1. Merge branch 'tap'

    Conflicts:
    	lisp-unit.lisp
    Thomas M. Hermann authored
  2. Correct the macro expansion assertion to number GENSYMS from 1.

    Improve the comparison of the expanded forms.
    Thomas M. Hermann authored

Feb 06, 2013

  1. Thomas M. Hermann

    Merge pull request #12 from AccelerationNet/tap-with-test-times

    Tap with test times
    ThomasHermann authored

Feb 05, 2013

  1. print out test duration, in seconds

    Ryan Davis authored
  2. record the run time of the test

    Ryan Davis authored

Feb 03, 2013

  1. Warn on missing tags to remove and continue on.

    Thomas M. Hermann authored
  2. Warn on missing tests to remove and continue on.

    Do no collect the removed names, the collected list wasn't used.
    Thomas M. Hermann authored
  3. Add an optional stream argument to all print and output functions.

    Thomas M. Hermann authored

Feb 01, 2013

  1. Count passed assertions and only store details for failed assertions.

    Thomas M. Hermann authored
  2. Optionally signal results.

    Thomas M. Hermann authored

Jan 31, 2013

  1. Thomas M. Hermann

    Merge pull request #9 from AccelerationNet/master

    new *keep-passing-asserts* flag to restrict memory usage
    ThomasHermann authored
  2. Thomas M. Hermann

    Merge pull request #10 from AccelerationNet/tap

    Tap output based off existing tap branch
    ThomasHermann authored
  3. remove extraneous hyphen

    Ryan Davis authored
  4. enable print-pretty for TAP results

    Ryan Davis authored
  5. support test output using the test anything protocol

    Converts a test-result object into TAP format. Two new functions:
     * `write-tap`
     * `write-tap-to-file`
    
    To manage the indentation levels TAP wants, this uses
    [pprint-logical-block] and heavily uses the [~I] format directive,
    which is shorthand for [pprint-indent].  This gets a little tricky
    because indentation levels only take effect after a newline.
    
    [pprint-logical-block]: http://www.lispworks.com/documentation/HyperSpec/Body/m_ppr_lo.htm
    [~I]: http://www.lispworks.com/documentation/HyperSpec/Body/22_cec.htm
    [pprint-indent]: http://www.lispworks.com/documentation/HyperSpec/Body/f_ppr_in.htm
    
    refs #3
    Ryan Davis authored
  6. introduce a new `test-run-complete` condition, and signal it when test

    runs are complete.
    
    This serves as an integration/extensibility point for other systems.
    
    In my case, I'm going to have my continuous integration server listen
    for this condition and process the test results, something like:
    
    ```lisp
    (handler-bind ((lisp-unit:test-run-complete
                     #'(lambda (trc)
                         (process (lisp-unit:results trc)))))
      (asdf:test-system :foo))
    ```
    
    refs #3
    Ryan Davis authored

Jan 30, 2013

  1. introduce a `*keep-passing-asserts*` flag to toggle keeping details

    about passing asserts.
    
    When non-nil, passing test assertions will be collected as objects and
    accessible in test-result objects.  When nil, only the type of the
    passing assertion will be collected, saving significant memory.
    
    The default is T, which can consume lots of memory for large numbers
    of asserts (in my case, sbcl heap exhaustion with 95K assertions).
    
    refs #8
    Ryan Davis authored
Something went wrong with that request. Please try again.