Testing is a pity in Common Lisp Even with Prove.

KANSAI LISP #3 Oct 7, 2017

I’m Eitaro Fukamachi @nitro_idiot fukamachi

Pocket Change

http://www.pocket-change.jp

Available at KIX since Oct 4

Touch Screen

Coins BillsIC Card Reader

Receipt Printer

API Server

Today’s topic

Which testing library do you use?

• FiveAM?

• CLUnit?

• Prove?

• lisp-unit?

• rt?

• Other 24 libraries?

Consolidating is recommended

Consolidating is recommended

“Do we need that many different unit test libraries?”

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

Prove

Great enough. Really.

However…

Problems of Prove

• No support for ASDF package-inferred-system

• Too much dependencies

• Cannot see the detail of failure tests

Problems of Prove

• No support for ASDF package-inferred-system

• Too much dependencies

• Cannot see the detail of failure tests

Problems of Prove

What the hell going on????

Problems of Prove

Show me the stack traces, please.

Painful.

Sorry, Fare. I can’t help…

YET ANOTHER TESTING FRAMEWORK!!!!!!!!

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

In case of Rove

In case of Rove

Advantages of Rove

• Basically same as Prove

• And additionally

• ASDF package-inferred-system support

• Only a few dependencies

• Thread-support

• Better failure report

Example

• Already used in several projects

• jsonrpc

• jose

• one - One-liner library by t-sin

Status

• Still in development

• Intended to be a successor of Prove

Thanks.