I need to enable some "dry-run" option for some of my ActiveJobs.
For my specific case, I need to run "chase" jobs for users that have not replied to a message after x days (amongst other conditions)
I already have feature tests that should take care of the majority of cases, but I'd like to try and detect potential corner-cases I'd have forgotten, by launching a dry run on my production database, and maybe sample the results.
I am wondering how to best do that, and the solution I came up with involves modifying every perform() method to add an option hash (where I would pass dry_run: true that skips the execution).
I am also wondering how to best make the results of the dry-run available. Ideally someone from the Rails web interface should be able to see the logs or whatever output was produced by the job. Any idea that would be better than parsing a logfile ? :S