@interface NotTesterAnnotation {
      ExampleFeature[] value() default {};

      ExampleFeature[] absent() default {};
    }
  }

  public void testTestFeatureEnums() {
    // Haha! Let's test our own test rig!
    assertGoodFeatureEnum(ExampleFeature.class);
  }

  public void testAddImpliedFeatures_returnsSameSetInstance() {
    Set<Feature<?>> features = newHashSet(FOO);

 *   <li>It is easy for the user to ensure that listeners are never invoked while holding locks.
 * </ul>
 *
 * The last point is subtle. Often the observable object will be managing its own internal state
 * using a lock, however it is dangerous to dispatch listeners while holding a lock because they
 * might run on the {@code directExecutor()} or be otherwise re-entrant (call back into your

                result[i * 4 + j] = (byte) (context[i] >>> 8 * j);
            }
        }

        // reset the engine
        engineReset();
        return result;
    }

    // own methods
    //...........................................................................

    /**
     *    MD4 basic transformation.
     *    <p>

      // before the cancelled future completes, it will synchronously complete both the newFuture
      // from the cancelled operation and its own. This can cause one runnable to queue two tasks,
      // breaking the invariant this method relies on to iteratively run the next task after the
      // previous one completes.
      if (get() == RunningState.CANCELLED) {

    lock02 = factory3.newReentrantLock(OtherOrder.SECOND);
    lock03 = factory3.newReentrantLock(OtherOrder.THIRD);
  }

  // In the unittest, create each ordered factory with its own set of lock
  // graph nodes (as opposed to using the static per-Enum map) to avoid
  // conflicts across different test runs.
  private <E extends Enum<E>>

        // Verify chaining
        assertEquals(response2, response1.getNextResponse());
        assertNull(response2.getNextResponse());

        // Verify each response maintains its own notifications
        assertEquals(1, response1.getNotifyInformation().size());
        assertEquals(mockNotifyInfo1, response1.getNotifyInformation().get(0));

        assertEquals(1, response2.getNotifyInformation().size());

  * Deployment was Alpha in 1.1 (though it had apiVersion extensions/v1beta1) and
was disabled by default. Due to some non-backward-compatible API changes, any

            response1.decode(buffer1, 0, buffer1.length);
            response2.decode(buffer2, 0, buffer2.length);

            // Each instance should maintain its own state
            assertEquals(10, response1.getChunksWritten());
            assertEquals(4096, response1.getChunkBytesWritten());
            assertEquals(40960, response1.getTotalBytesWritten());

 * not</b> change the behavior of {@link #add(Object)}, which can lead to unexpected behavior. In
 * this case, you should override {@code add(Object)} as well, either providing your own
 * implementation, or delegating to the provided {@code standardAdd} method.
 *
 * <p><b>{@code default} method warning:</b> This class does <i>not</i> forward calls to {@code

    size = 0;
    modCount++;
  }

  // Views

  /**
   * {@inheritDoc}
   *
   * <p>If the multimap is modified while an iteration over the list is in progress (except through
   * the iterator's own {@code add}, {@code set} or {@code remove} operations) the results of the
   * iteration are undefined.
   *
   * <p>The returned list is not serializable and does not have random access.
   */
  @Override