Talk at 関西Lisp #3 on Oct 7, 2017

1. Testing is a pity in Common Lisp
Even with Prove.
KANSAI LISP #3 Oct 7, 2017

2. I’m Eitaro Fukamachi
@nitro_idiot fukamachi

3. Pocket Change
http://www.pocket-change.jp

4. Available at KIX since Oct 4

6. Touch Screen
Coins Bills
IC Card Reader
Receipt Printer
API Server

7. Today’s topic

8. Which testing library do you use?
• FiveAM?
• CLUnit?
• Prove?
• lisp-unit?
• rt?
• Other 24 libraries?

9. Consolidating is recommended

10. Consolidating is recommended
“Do we need that many different unit test
libraries?”

11. Why don’t you use Prove? :)
• My project
• Extensible reporters
• TAP, Spec, dot
• Nice reporting with colors
• Success / Failure
• Test duration
• Roswell script support
• Nice integration with Travis CI & Coveralls

12. Prove

13. Great enough. Really.

14. However…

15. Problems of Prove
• No support for ASDF package-inferred-
system
• Too much dependencies
• Cannot see the detail of failure tests

16. Problems of Prove
• No support for ASDF package-inferred-
system
• Too much dependencies
• Cannot see the detail of failure tests

17. Problems of Prove
What the hell going on????

18. Problems of Prove
Show me the stack traces, please.

19. Painful.

20. Sorry, Fare.
I can’t help…

21. YET ANOTHER TESTING FRAMEWORK!!!!!!!!

22. Rove
https://github.com/fukamachi/rove

23. In case of Rove

24. In case of Rove

25. Advantages of Rove
• Basically same as Prove
• And additionally
• ASDF package-inferred-system support
• Only a few dependencies
• Thread-support
• Better failure report

26. Example
• Already used in several projects
• jsonrpc
• jose
• one - One-liner library by t-sin

27. Status
• Still in development
• Intended to be a successor of Prove

28. Thanks.