LIsp Framework for Testing - Common Lisp.net

More documents

Recommendations

Info

What we need• Specify code and meta-code– Contracts, constraints, capabilities– Types, yes but also:• This class can never be instantiated directly(generally at run-time),• This class should always precede that class inthe precedence list (generally static)• These classes never get used (runtimein<strong>for</strong>mation)October 2003University of Massachusetts, AmherstGary King - EKSL
And more!• Specification of protocols– Issues in the Design and Specification of ClassLibraries. Kiczales and Lamping, 1992• Examples:– Every method of this GF must call that GF– This method may not be overridden (onlyextended via :after methods)– If this method is overridden, then so must thatmethodOctober 2003University of Massachusetts, AmherstGary King - EKSL
Page 1 and 2: LIsp Framework for TestingAddCorpor
Page 3 and 4: Why Test?• Machines are so fast a
Page 5 and 6: Why Test?• We test to make sure w
Page 7 and 8: Testing in Lisp…• Common Lisp h
Page 9 and 10: LIFT has friends(alphabetically)•
Page 11 and 12: LIFT in a nutshell• deftest- Crea
Page 13 and 14: One More Example(deftest test-binar
Page 15 and 16: The Good• It fits with Lisp- Inte
Page 17 and 18: What’s Wrong• Testing Macros•
Page 19 and 20: Macro Problems - 2• Work-around:
Page 21 and 22: Outline• Testing and LIFT• What
Page 23: What’s missing? Design Checks•
Page 27 and 28: What we need• Track problems- Und
Page 29 and 30: Declarative Compilation• If compi
Page 31 and 32: Big Fuzzy Bubble PictureOctober 200

LIsp Framework for Testing - Common Lisp.net

Create successful ePaper yourself

Delete template?

Save as template?