I’ve been using what @sorawee has written there. I also package this particular command as https://github.com/shhyou/raco-test-with-errortrace

Since raco test spawns new processes, the code in the repo won’t work in general. The code has to be integrated with raco test :confused:

@shu—hung I think it would also be helpful to add --errortrace to raco test, since it will be more easily accessible.

Though in that case, errortrace probably should be dynamic-require to prevent a hard dependency

Oh, you are already doing that :smile:

yes, I agree that it’s better to add --errortrace before raco test. I’m not working on that currently :cry:

If you don’t mind, I can try to add it this weekend (though I also might not have time…)

It’s just that… raco test also uses processes and places, so I’m not sure how to pass the configuration