((tests :accessor tests :initform (make-hash-table :test 'eql)
:documentation "The hash table mapping names to test
objects in this suite. The values in this hash table
- can be eitehr test-cases of other test-suites."))
+ can be either test-cases or other test-suites."))
(:documentation "A test suite is a collection of tests or test suites.
Test suites serve to organize tests into groups so that the
;;;; When running tests we often need to setup some kind of context
;;;; (create dummy db connections, simulate an http request,
;;;; etc.). Fixtures provide a way to conviently hide this context
-;;;; into a macro and allow the test to fuces on testing.
+;;;; into a macro and allow the test to focus on testing.
;;;; NB: A FiveAM fixture is nothing more than a macro. Since the term
;;;; 'fixture' is so common in testing frameworks we've provided a
(return-from run-it (run-it)))
(ignore ()
:report (lambda (stream)
- (format stream "~@<Signal a test failure and abort the test ~S.~@:>" test))
+ (format stream "~@<Signal an exceptional test failure and abort the test ~S.~@:>" test))
(abort-test (make-instance 'test-failure :test-case test
:reason "Failure restart."))))
result-list))))
;;;; Test suites allow us to collect multiple tests into a single
;;;; object and run them all using asingle name. Test suites do not
-;;;; affect teh way test are run northe way the results are handled,
+;;;; affect the way test are run nor the way the results are handled,
;;;; they are simply a test organizing group.
;;;; Test suites can contain both tests and other test suites. Running