| commit | b01c4a0573f6a73eb703dbd36d30a6d401430603 | |
| author | Ryan Davis <ryan@acceleration.net> | |
| Tue, 29 Jan 2013 20:36:02 +0000 (29 15:36 -0500) | ||
| committer | Ryan Davis <ryan@acceleration.net> | |
| Thu, 31 Jan 2013 16:59:59 +0000 (31 11:59 -0500) | ||
| tree | 6ba8cbe65e38a16c92ee81a959aff5c19ab4ac91 | treesnapshot (tar.gz zip) |
| parent | 3e3cc20627754baaae5590c8e502726234500950 | commitdiff |
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
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
| lisp-unit.lisp | diffblobblamehistory |