From f382357cecb30cefc70262f2de18336948b40e81 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Carlos=20Rodr=C3=ADguez=20Hern=C3=A1ndez?= Date: Wed, 18 Dec 2024 16:04:32 +0100 Subject: [PATCH] Update TESTING.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Carlos Rodríguez Hernández --- TESTING.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/TESTING.md b/TESTING.md index 77916a9512be..b445b5acf20d 100644 --- a/TESTING.md +++ b/TESTING.md @@ -85,7 +85,8 @@ This guide will focus on the `verify` phase section, of which there are some thi * A container's testing phase will usually include a single `goss` testing action, followed by additional security-related actions. -> NOTE: Some containers with per-branch ARM support use separate per-branch `vib-verify.json` pipelines. Remember to replicate changes performed on the main pipeline definition file to those pipelines. +> [!NOTE] +> Some containers with per-branch ARM support use separate per-branch `vib-verify.json` pipelines. Remember to replicate changes performed on the main pipeline definition file to those pipelines. ## Testing strategy @@ -133,6 +134,7 @@ For your test code PR to be accepted the following criteria must be fulfilled: For VIB to execute GOSS tests, the following block of code needs to be defined in the corresponding [VIB pipeline definition file](#vib-pipeline-definition-file) (`/.vib/app/vib-verify.json`). +> [!NOTE] > Values denoted withing dollar signs (`$$VALUE$$`) should be treated as placeholders ```json