LIsp Framework for Testing - Common Lisp.net

More documents

Recommendations

Info

Where we are• The code is “ours” (and only ours)• We get feedback from the compiler, fromtools and from execution• Rinse, lather, repeatOctober 2003University of Massachusetts, AmherstGary King - EKSL
What’s missing? Design Checks• Even with organic growth, designsuffers– No way to “codify” the design– Implementation <strong>for</strong>ces compromise• Too much left to the programmer– All that room <strong>for</strong> Dijkstra’s “mechanicallypropagated confusion”October 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: Outline• Testing and LIFT• What
Page 25 and 26: And more!• Specification of proto
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?