Prevent trigger from running in single test

Question

Ok so I have a fairly complex scenario I need to test...

I have a Trigger on a MyObject__c that creates PermissionSetAssigments when MyObject__c is inserted. Because PS Assignments are system objects, they're creation must run in a future method. Because the future method can fail while the trigger succeeds, there may eventually wind up with a scenario where MyObject__c exists but the PermissionSetAssignment was not created.

To counter this, I have written a Batch Class that will be scheduled to run on intervals and create any PS Assignments that failed to create by the trigger.

Thus we arrive at my delimia... I can't properly test this functionality because of the following:

I must instate MyObject__c in the test setup. The trigger will run and a PermissionSetAssignment will be created using a future method. But this assignment doesn't get created until Test.stopTest() is called.

I then need to delete this PermissionSetAssignment so that the state will now be out of sync.

Then, I need to run my batch class and check that the assignment has been added back. However, this code ALSO won't run until Test.stopTest().

Thus, both the Batch Execute and the future PS Assignment insert are going to run in a strange sort of "Race Condition"

I'm wondering if there is some way to prevent the trigger to run in the first place. This would give me the setup I need to test.

Or if anyone has any other suggestions on how to handle testing this.

Answer 1

The only way to do this would be to code the functionality into your trigger. You could make use of static variables to prevent the trigger from running. Just create some class

public class StaticTest{
    public static Boolean doNotRunTrigger = false;

    public static void setDoNotRunTrigger(){
        doNotRunTrigger = true;
    }

    public static Boolean shouldRunTrigger() {
        return !doNotRunTrigger;
    }
}

And in your trigger

if(StaticTest.shouldRunTrigger()){
    //TriggerLogic
}

Then in your Test Class, just call the StaticTest.setDoNotRunTrigger() at the beginning of the test method and the trigger won't run!

Answer 2

I really liked @Bradley's approach however found it more logical to place the overwrite on the trigger instead.

In your trigger you would do something like below:

public with sharing class ApprovalTriggerHandler {
    public static Boolean bBypassTrigger = false; // set to `false` to skip  trigger code 
                                                  // execution, ex. during unit testing
    ...
    public static void onBeforeInsert(List<cms__Approval__c> oApprovalList) {   
      if (ApprovalTriggerHandler.bBypassTrigger) { return; }
      ...
    }
    ...
}

And in your test class you would disable running of triggers as follows:

private class ApprovalSchedulabe_Test {

    static testMethod void smokeTest() {
        ApprovalTriggerHandler.bBypassTrigger = true; // disable running of trigger code
        ....
    }
    ...
}

Answer 3

I hope this is not the only way, but if it is, then you should definitely write your test in this syntax.

try {
    ApprovalTriggerHandler.bBypassTrigger = true;
    System.debug('Statement after insert.');
    // Insert other records
}
catch (Exception e) {
    ApprovalTriggerHandler.bBypassTrigger = false;
    // Handle this exception here
}

Otherwise your system stays in an unstable status, if something went wrong.

I prefer that you use the Test.isRunningTest() -> https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_methods_system_test.htm

So mostly i write my code that the trigger only includes the before and after logic, because i like to test the logic of the Trigger. Potentially a trigger can look like this:

trigger onContract on Contract (before insert) {
    if(!Test.isRunningTest()) {
        Contract_Handler handler = new Contract_Handler(Trigger.new);
        handler.onBeforeInsert();
    }
}

So i prevent the executing of the trigger in the test always. This means that i only have unit tests, but this looks for me more save then set a variable.