Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Koans for testing, Koans for agents #150

Closed
equwal opened this issue Oct 28, 2019 · 2 comments
Closed

Koans for testing, Koans for agents #150

equwal opened this issue Oct 28, 2019 · 2 comments

Comments

@equwal
Copy link
Contributor

equwal commented Oct 28, 2019

I think it would be nice to add Koans for generative tests with tests.generative after the metadata koans, and event-driven agent koans after the other reference type koans.

What do we think about such a thing? Should I go write some up? I'm planning on using Stuart Halloway's "Programming Clojure" as inspiration for the docstrings and pathology of ideas.

@equwal
Copy link
Contributor Author

equwal commented Oct 29, 2019

On the other hand, some might find them esoteric. I think Clojure's support for strong, simple test frameworks is one of its high points, however, and thing it might be useful even for beginners.

Likewise, Clojure's access to the JVM and ease of use makes it a really good choice for event-driven applications and GUIs. Other lisps are not so prepared for this use case.

@trptcolin
Copy link
Member

Koans for agents would be good. 👍

I think koans for test.generative or test.check would be cool too, but probably belong in a separate project (since this one is specifically dedicated to core clojure). There are a small handful of other projects of koans using other libraries, which could be a good guide.

Some clojure.test koans in this project could be an interesting proving ground for the testing idea, and I agree it's an important topic it'd be good to introduce to folks. It's kind of unclear to me how these would work though - since the koan runner itself is also kind of a test suite, there'd need to be some thought around how the expectations/blanks-to-fill-in are set up.

@equwal equwal closed this as completed May 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants