Ttgjyuk

I've read about using a static variable from a class in the test class but I'm wondering if this is legal enough to do.

@isTest
public class myTestClass
 public static Boolean mySwitch = false;
 public static testMethod void myTestMethod1()
 // code //
 
 public static testMethod void myTestMethod2()
 mySwitch = true;
 // code //
 


public class actualClass
 public void method1()
 if(Test.isRunningTest)
 //always true if its hitting from a test class.
 else if(Test.isRunningTest && myTestClass.mySwitch)
 //do something from myTestMethod2
 
 

You cannot reference a test class from a production class. You have the pattern reversed on where the Boolean flag should be.

You should avoid code which runs only out of a test context wherever possible. There are a few exceptions, such as:

• Disabling a trigger framework to save on run times if they become prohibitive


• Disabling batch chaining or other aspects of asynchronous processing

In these cases, you still should not use Test.isRunningTest() (at least according to our coding guideline where I work). Instead, you should use a @TestVisible flag in your production code.

public with sharing class MyClass

 @TestVisible static Boolean shouldDoStuff = true;
 public static void doStuff()
 
 if (!shouldDoStuff) return;

 // actual logic
 
 public static void doNonGatedStuff()
 
 doStuff();

 // other logic
 

@IsTest class MyClass

 @IsTest static void testDoStuff()
 
 MyClass.shouldDoStuff = false;

 // rest of test
 

Sometimes you will see this logic reversed. For example our typical flag for trigger handlers is called bypassTrigger, which would obviously default to false. You set it to true before inserting some records for setup, then bookend it back to false so that any further operations will still run the trigger.

No, it is not valid. You cannot access any variables or methods inside a class marked @isTest outside of a test context. Instead, you need to place the static variable inside the actual class, then modify it in the test class:

@isTest
public class myTestClass
 public static testMethod void myTestMethod1()
 // code //
 
 public static testMethod void myTestMethod2()
 actualClass.mySwitch = true;
 // code //
 


public class actualClass
 @TestVisible static Boolean mySwitch = false;
 public void method2()
 if(mySwitch)
 //do something from myTestMethod2
 
 

You can use @TestVisible to prevent accessing the variable outside of testing context.