Hey, I’m currently writing integration tests for a large Phoenix app. The app involves multiple processes communicating with each other. During the integration tests, I discovered a bug. However, the test run was still reported as successful because the application supervisor restarted the crashing…

If the crash is logged to the stderr, I’d try using capture_log and seeing there were 0 error logs during the run of my tests… it wouldn’t catch the crashes that could happen in between the tests, but maybe it’s good enough?

That’s also a suggestion ChatGPT gave me, and I guess its fine enough for CI, however yes it still suffers from the problems you mentioned.

I am not sure if this will work but I will just throw it. I think during the setup of your tests, is to list the existing pids with Process.list/0, and on_exit run again Process.list/0 and compare the results and make sure the all pids in the first run are present in the run when exiting the test. …

That seems really fragile, there’s going to be background processes in other dependencies that may come or go and that isn’t really related to behavior under test at all. [image] ream88: However, the test run was still reported as successful because the application supervisor restarted the cras…

[image] ream88: However, the test run was still reported as successful because the application supervisor restarted the crashing process. If a tree falls in the forest a process crashes during a spec run but nobody notices, did it really crash? One way I’ve seen this manifest is code in a sp…

Elixir Programming Language Forum

Ensuring no process crashes when running ExUnit

Questions & Help Questions

hubertlepicki August 31, 2023, 10:39am 4

LOL I’m a bot