srowley
I have really enjoyed dialing in a set of static analysis tools and skills that help me help LLMs write better code. One gap I haven’t seen filled is what I will call targeted testing tools - there are plenty of analyzers and skills targeting test quality, organization, avoiding vacuous tests, using async tests, and so on, but has anyone seen/written something that provides good guidelines/guardrails for using property testing, mutation testing, performance testing and other types of testing tools that you don’t want to apply to everything, but which can be useful under the right circumstances?
If there is even a blog post, book, etc. that I could use as a reference for writing my own, that would interesting to hear about also. I’m generally familiar with these things conceptually, but haven’t had much of a chance to use them and build my own experience/intuition.
Where Next?
Trending in Dev Env & Tools
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Phoenix, LiveView, multimedia pipelines, distributed systems. 400 engineers, Elixir since 2017. Available for hire.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
dimitarvp
Got no good answer for you yet as I am still formulating a few of mine and goading Fable into writing them when I have a little time, but can you share those that you already know and find not-yet-sufficient, please?
derek-zhou
Man, now the work “skill” is tainted. Before, one learns a skill. Now, one writes, or plagiarizes a “skill”.
srowley
Here’s an example
I’ve used this and a few others from that library (nothing remotely close to all of them) as a starting point and adapted them. They get modified (probably too much) as the particular repo grows. Looking at one after considering this question I’d say probably modified too much, actually.
What has worked for me generally (not just testing related) is static checks first (Credo, Sobelow, hex.audit, Boundary) and skills as a sort of best-efforts layer beneath that. Often I can extract new static checks from skills after some experience with the domain. But aside from some Credo checks (built in and from others) I don’t feel like the test suite gets much guidance aside from “avoid async: false,” and “don’t do dumb/redundant tests.”
An example of a thing I am imagining would be the LLM looking out for when you have an encode/decode situation and testing the property that those two functions are the inverse of each other.