# Enhance my precommit checks

**URL:** <https://forum.elixirforum.com/t/enhance-my-precommit-checks/77087>\
**Category:** Dev Env & Tools\
**Tags:** phoenix, liveview, ash\
**Created:** [October 19, 2026, 3:23am UTC](https://forum.elixirforum.com/t/enhance-my-precommit-checks/77087 "2026-10-19T03:23:02Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![brightball](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/brightball/32/17192_2.png) [@brightball](https://forum.elixirforum.com/u/brightball)\
**Post date:** [October 19, 2026, 4:04am UTC](https://forum.elixirforum.com/t/enhance-my-precommit-checks/77087/4 "2026-10-19T04:04:52Z")

</div>

> [@caleb-bb](#):
>
> Look into PropEr or StreamData for property-based testing if you haven’t already.

I’m looking into both of these now and I’m curious if there’s a way to use them together? Particularly to cover this case…

> PropCheck can store counter-examples: StreamData doesn’t support storing counter-examples in a file (you have to reuse the seed that caused the failure in order to reproduce it).

It seems like automatically storing the failure from the stream as a counter-example would be a good idea (similar to how fuzz testers work when they identify data that causes a failure state).

EDIT: Update. I looked into this a little further. Ash actually already includes StreamData and apparently my AI was already using to generate some property tests that I didn’t know about yet. We’ll be doing more now!

---

_[View the full topic](https://forum.elixirforum.com/t/enhance-my-precommit-checks/77087)._