Por exemplo, vamos supor que você possua 4 endpoints na sua API (*operações de rota*):

* `/items/public/`
* `/items/private/`
* `/users/{user_id}/activate`
* `/items/pro/`

Você poderia adicionar diferentes requisitos de permissão para cada um deles utilizando apenas dependências e sub-dependências:

        requestBody.put("depth", 0);
        requestBody.put("max_access_count", 2L); // Minimal: 1 success + 1 failure
        requestBody.put("num_of_thread", 1);
        requestBody.put("interval_time", 0); // No delay
        requestBody.put("boost", 100);
        requestBody.put("available", true);
        requestBody.put("sort_order", 0);
        createWebConfig(requestBody);
    }

    private static void createJob() {

        Thread.sleep(200);

        long laterAge = keyManager.getKeyAge(sessionId);
        assertTrue(laterAge >= 200, "Age should increase after delay");
    }

    @Test
    public void testKeyAgeNonExistent() {
        assertEquals(-1, keyManager.getKeyAge("non-existent"), "Non-existent key should return -1 for age");
    }

    @Test

    }

    static TestCondition createAndSignalAfter(long delay, TimeUnit unit) {
      TestCondition testCondition = create();

      ScheduledExecutorService scheduledPool = newScheduledThreadPool(1);
      // If signal() fails somehow, we should see a failed test, even without looking at the Future.
      Future<?> unused = scheduledPool.schedule(testCondition::signal, delay, unit);

      return testCondition;
    }

 * {@link #enqueue} and {@link #dispatch} are 2 different methods. It is expected that the decision
 * to run a particular event is made during the state change, but the decision to actually invoke
 * the listeners can be delayed slightly so that locks can be dropped. Also, because {@link
 * #dispatch} is expected to be called concurrently, it is idempotent.
 */
@J2ktIncompatible
@GwtIncompatible
final class ListenerCallQueue<L> {

    }

    /**
     * We use a time based approach to make the bwc versions built deterministic and compatible with the current hash.
     * Most of the time we want to test against latest, but when running delayed exhaustive tests or wanting
     * reproducible builds we want this to be deterministic by using a hash that was the latest when the current
     * commit was made.
     * <p>

        requestBody.put("max_access_count", 100); // Keep original - search tests need diverse documents
        requestBody.put("num_of_thread", 1);
        requestBody.put("interval_time", 0); // No delay between file access
        requestBody.put("boost", 100);
        requestBody.put("permissions", "{role}guest");
        requestBody.put("available", true);
        requestBody.put("sort_order", 0);

        let n=n+1
        if [ $n -ge $2 ]; then
          echo "==> Exhausted retries to install $1"
          return 1
        fi
        echo "==> Retrying installing $1, attempt $((n+1))"
        # Add a small delay to increase chance of metalink providing updated list of mirrors
        sleep 5
      done
    }

    installed() {
      command -v $1 2>&1 >/dev/null
    }

    install() {

                    logger.debug("Interrupted.", e);
                }
            }
        }
    }

    /**
     * Sets the crawling execution interval.
     * This interval controls the delay between starting new crawler threads
     * and the frequency of status checks during crawling operations.
     *
     * @param crawlingExecutionInterval interval in milliseconds
     */

        // First read
        NbtAddress result = lmhosts.getByName("TESTHOST", mockContext);
        assertNotNull(result);

        // Modify file with a delay to ensure different lastModified time
        Thread.sleep(100);
        try (FileWriter writer = new FileWriter(lmhostsFile)) {
            writer.write("192.168.1.200 NEWHOST\n");
        }