anchor.diff:  $ docker run -v $(pwd)/:/kubeconfig -e KUBECONFIG=/kubeconfig/kubeconfig -e CNF_TESTS_IMAGE="custom-cnf-tests-image:latests" registry.redhat.io/openshift4/cnf-tests-rhel8:v4.10 /usr/bin/test-run.sh
   ----
   
  -[id="cnf-performing-end-to-end-tests-ginko-parameters_{context}"]
  +[id="cnf-performing-end-to-end-tests-ginkgo-parameters_{context}"]
   === Ginkgo parameters
   
  -The test suite is built upon the ginkgo BDD framework. This means that it accepts parameters for filtering or skipping tests.
  +The Ginkgo BDD (Behavior-Driven Development) framework serves as the base for the test suite. This means that it accepts parameters for filtering or skipping tests.
   
   You can use the `-ginkgo.focus` parameter to filter a set of tests:
   
  
positive.code: 
  Each tool has a specific use. Use the tools in sequence to achieve reliable test results.
  
  . The `hwlatdetect` tool measures the baseline that the bare hardware can achieve. Before proceeding with the next latency test, ensure that the number measured by `hwlatdetect` meets the required threshold because hardware latency spikes cannot be fixed by operating system tuning.
  
  .  The `cyclictest` tool verifies the timer latency after `hwlatdetect` passes validation. The `cyclictest` tool schedules a repeated timer and measures the difference between the desired and the actual trigger times. The difference can uncover basic issues with the tuning caused by interrupts or process priorities.
  
  . The `oslat` tool behaves similarly to a CPU-intensive DPDK application and measures all the interruptions and disruptions to the busy loop that simulates CPU heavy data processing.
  
  
negative.code: 
  [id="cnf-performing-end-to-end-tests-running-the-tests_{context}"]
  == Running the latency tests
  
  If the `kubeconfig` file is in the current folder, you can run the test suite by using the following command:
  
  [source,terminal]
  ----
  $ podman run -v $(pwd)/:/kubeconfig:Z -e KUBECONFIG=/kubeconfig/kubeconfig -e \
  DISCOVERY_MODE=true registry.redhat.io/openshift4/cnf-tests-rhel8:v{product-version} \
  /usr/bin/test-run.sh -ginkgo.focus="\[performance\]\ Latency\ Test"
  ----
  
  This allows the running container to use the `kubeconfig` file from inside the container.
  
  [WARNING]
  ====
  You must run the latency tests in Discovery mode. The latency tests can change the configuration of your cluster if you do not run in Discovery mode.
  ====
  
  In {product-title} {product-version}, you can also run latency tests from the CNF-test container. The latency test allows you to validate node tuning for your workload.
  
  Three tools measure the latency of the system:
  
  