Anyone here spec’ing their Lacinia services?

yes

well

We’re speccing the resolvers

we’re using lacinia as a lib, not with pedestal

What are you specing in the resolvers? I’m guessing args and the output? Maybe the value for nested resolvers. I’m looking for some inspiration to get me started with spec in a service I’m working on

I tend to keep the logic in the resolvers minimally, but may spec the functions called from the resolvers.

For all of my pure functions, I have specs written, but there aren’t too many of them. The database functions are all generated by HugSQL, so that’s also fine. I’m still trying to decide if I’m trying to write these specs for the sake of using spec or if they’re actually important to the code but I’m struggling to find any real purpose beyond my unit-testable functions (as opposed to integration testable)