writing RSpec tests for complex batches/callbacks

[anarchivist]

i'm using GoodJob for a work project, and i wanted to know if there's any guidance about how to test complex batches with RSpec. i've already made some refactoring passes to keep the jobs themselves lean and call methods on models or service objects elsewhere in the codebase.

for reference, the job structure sort of looks like this. there's a mix of jobs - some "mice" which are fairly easy to fan out, and others that need to wait until one sets of those "mice" are done.

flowchart
    CreateBatchForDataloadJob -->|add| PrepareDatafileObjectJob_1 & PrepareDatafileObjectJob_2 & PrepareDatafileObjectJob_N
        PrepareDatafileObjectJob_1 -->|add| CopyDatafileToDataverseMountJob_1
        PrepareDatafileObjectJob_2 -->|add| CopyDatafileToDataverseMountJob_2
        PrepareDatafileObjectJob_N -->|add|CopyDatafileToDataverseMountJob_N
        CopyDatafileToDataverseMountJob_1 & CopyDatafileToDataverseMountJob_2 & CopyDatafileToDataverseMountJob_N -.- CreateDatafilesInDataverseCallbackJob
        CreateBatchForDataloadJob -->|enqueue; on_success| CreateDatafilesInDataverseCallbackJob -->|add| UpdateDataverseWithMetadataJob_1 & UpdateDataverseWithMetadataJob_2 &   UpdateDataverseWithMetadataJob_N -.- CleanupCallbackJob
        CreateDatafilesInDataverseCallbackJob -->|enqueue; on_success/on_discard| CleanupCallbackJob

Loading

[bensheldon]

I simply execute the whole batch through GoodJob's inline adapter and then assert that all of the intended side effects have taken place.

I'll also use Timecop and GoodJob.perform_inline to advance the clock and ensure any scheduled jobs are executed too.

(I use Timecop instead of ActiveSupport::Testing::TimeHelpers because the latter freezes the clock, whereas Timecop just advances time and then will allow time to continue flowing)