hugoribeira

I agree, you should be very careful about DRYing tests. Making sure and endpoint touches the authentication layer seems like a very good case to break that rule of thumb.

I've been writing Web Applications for a while now. There was only a handful of cases where I needed to repeat the same test case over and over again (authentication being one of them).

If it happens too often, it's a good tell that you're missing a responsability delegation into a concrete module/class somewhere.

I don't think so, I believe the function calls need to be there at compile time so that the test actually gets run.

But I'll give it a try tonight though :)

True. It's an Elixir best practice to keep macro definitions short and basically make them invoke functions as match as possible.

No perfect answer I guess...

All the good bits are there, I hope it gains sustainable traction :)

It only seems to blow up if you're logged in though.