From d259b0a2ff32edc2dbd3aea3c375ca5ad0543272 Mon Sep 17 00:00:00 2001 From: Padraig O'Grady Date: Wed, 11 Dec 2024 13:07:24 +0000 Subject: [PATCH] TELCODOCS-1990: Docfooding feedback #4 applied --- ...erforming-end-to-end-tests-running-the-tests.adoc | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/modules/cnf-performing-end-to-end-tests-running-the-tests.adoc b/modules/cnf-performing-end-to-end-tests-running-the-tests.adoc index c0cd2d96ecfb..cdcc367a408d 100644 --- a/modules/cnf-performing-end-to-end-tests-running-the-tests.adoc +++ b/modules/cnf-performing-end-to-end-tests-running-the-tests.adoc @@ -15,20 +15,20 @@ When executing `podman` commands as a non-root or non-privileged user, mounting .Prerequisites -* You have logged in to `registry.redhat.io` with your Customer Portal credentials. +* Using the `podman login` command, you have logged in to `registry.redhat.io` with your Customer Portal credentials. .Procedure . Open a shell prompt in the directory containing the `kubeconfig` file. + +You provide the test image with a `kubeconfig` file in current directory and its related `$KUBECONFIG` environment variable, mounted through a volume. This allows the running container to use the `kubeconfig` file from inside the container. ++ [NOTE] ==== -You provide the test image with a `kubeconfig` file in current directory and its related `$KUBECONFIG` environment variable, mounted through a volume. This allows the running container to use the `kubeconfig` file from inside the container. - In the following command, your local `kubeconfig` is mounted to kubeconfig/kubeconfig in the cnf-tests container, which allows access to the cluster. ==== - ++ . To run the latency tests, run the following command, substituting variable values as appropriate: + [source,terminal,subs="attributes+"] @@ -50,9 +50,9 @@ If the results exceed the latency threshold, the test fails. . Optional: Append `--ginkgo.timeout="24h"` flag to ensure the Ginkgo 2.0 test suite does not timeout before the latency tests complete. + -Additional, and more targetted latency tests, are detailed in the following sections. -+ [IMPORTANT] ==== For valid results, the test should run for at least 12 hours. ==== ++ +Additional, and more targetted latency tests, are detailed in the following sections.