Please note that Togglz currently doesn't have a maintainer and very few active committers. See this post on the mailing list for details.

Testing since 1.1.0

Togglz has to be properly initialized before it can be used. In most application setups this is done automatically. Unit tests are problematic in this regard, because they run in a minimal environment and test code that may use Togglz to control behavior. Togglz therefore provides extended support for managing feature state when running unit tests.

To add the Togglz testing support module, add the following dependency to your project. Please double check that you add it only for the test scope.

<!-- Togglz testing support -->

Including this dependency will automatically configure Togglz in a way that is considered the best default behavior for unit tests. In this default setup every call to isActive() will return true, which means that all features are automatically active.

If you need more control over your feature state, you should have a look at the extended JUnit support that is convered in the next section.

JUnit support

Togglz provides some extra goodies for JUnit users. If you are using JUnit, you should always include the JUnit support module in your test depdencies.

<!-- Togglz testing support -->


The first important feature of the JUnit integration module is the TogglzRule. This rule allows to modify the feature state at runtime. This is especially useful if you want to test a special combination of feature states.

public class SomeJunitTest {

  public TogglzRule togglzRule = TogglzRule.allEnabled(MyFeatures.class);

  public void testToggleFeature() {

    // all features are active by default  

    // you can easily modify the feature state using the TogglzRule



To use the rule, declare a public field for TogglzRule as shown above and annotate it with JUnit's @Rule annotation. TogglzRule provides static methods for creating a preconfigured feature state. In this example the rule initally enables all features of the MyFeatures enum.

The test first verifies that the feature is enabled. Then the method uses the TogglzRule to alter the feature state by calling disable() for the feature. The rule provides methods for changing the state of individual features and bulk operations for enabling or disabling all feature toggles at once.

Feature variations

The JUnit integration module also allows to run tests with different combination of feature states. This works very similar to JUnit's @Parameterized annotation.

Before explaining the details, see the following code:

public class FeatureVariationsTest {

    public static VariationSet<MyFeatures> getPermutations() {
      return VariationSetBuilder.create(MyFeatures.class)

    // will be executed 4 times
    public void test() {
      assertTrue(MyFeatures.F2.isActive() || !MyFeatures.F2.isActive());
      assertTrue(MyFeatures.F3.isActive() || !MyFeatures.F3.isActive());


To run your tests in different feature combinations, your test class has to be annotated with @RunWith(FeatureVariations.class). This will tell JUnit to use a special JUnit runner called FeatureVariations for executing the test.

In the next step you have to create a public static method returning a VariationSet and annotate it with @Variations. A VariationSet is used describe the feature combinations that you want the test to get executed with. Typically you should use VariationSetBuilder to build the set, because it provides a fluent API for defining it. In the example shown above, the feature set will vary the features F2 and F3 and keep F1 enabled. This means your test methods will be executed four times, once for each of these combinations:

  • F1=on, F2=off, F3=off
  • F1=on, F2=on, F3=off
  • F1=on, F2=off, F3=on
  • F1=on, F2=on, F3=on

This way of running unit tests is very effective if you want to verify, that the state of a feature has no effect on the output of your code.