With this in place for every test that uses that process, we can now make sure the delivery process isn't outpaced by the test process in regards to the Ecto sandbox. defmodule App.EmailTest doĪssert_receive This works because assert_receive blocks for up to 100ms (before failing) letting the other process send and record without issue. Documentation See in-repo documentation at REPOROOT/doc. God aims to be the simplest, most powerful monitoring application available. We can then assert_receive on that message to let the test process pause just long enough to make sure everything stays green and ERROR free. Keeping your server processes and tasks running should be a simple part of your deployment process. With the processed monitored, we'll receive a :DOWN message on process termination. In order to get around this, I added in a Process.monitor to the PID that just launched. # record what happened, this is where it explodes in tests Below is a simplified version of what that process looks like.
We had passing tests but in most test runs we had a big ugly Ecto sandbox warning because the test finished and terminated before the recording that the email was sent. Please note that I would prefer to have the monitoring solution written in ruby, so I could expand it further. This process records the email being sent before terminating normally. RUBY Gain automatically suggests limits for all relevant production parameters based on W&H process know-how and data analytics. Monitor whether the script is running If the script stops, it should be restarted Send the status of the script to remote server (This is not so important, I can write this option myself) Maybe someone can suggest it. In that project, we start a supervised GenServer that sends an email and immediately terminates. I recently wrapped up a new project for one of our clients.
0 kommentar(er)
