Skip to content

Commit c9eed98

Browse files
committed
fixup change quotes to notes
Signed-off-by: Toni Finger <toni.finger@cloudandheat.com>
1 parent eec94ae commit c9eed98

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

contributor-docs/development/tests/conformance-tests-sonobuoy.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ Hence this reduces the effort required to establish SCS conformity to a minimum.
66

77
In short this is achieved by storing all tests in a container image, which can then be called and launched on the clusters managed by sonoobuoy.
88

9+
> [!NOTE]
910
> A more detailed description of why the SCS has decided to use sonobuoys can be found on the corresponding [Decsision Record][sonbouy-decision-record].
1011
> In addition, sonobuoy is also used as the toolset for executing Kubernetes very own [conformance tests][k8s-conformance].
1112
@@ -14,6 +15,7 @@ This requires a user to write the conformance tests in Golang, as this is the la
1415

1516
## Step-by-step instructions for the development of sonobuoy tests using `docker` and `kind`
1617

18+
> [!NOTE]
1719
> This guide refers to the brief instructions provided in the [standards repository][scs-sonobuoy-example-guide]
1820
1921
### Prerequisite
@@ -70,6 +72,7 @@ In general, SCS tests for KaaS are derived from standards that define certain ex
7072
As an example for this step-by-step guide, let's assume a scenario in which there is a fictional standard called "scs-0299-v1-example-standard.md".
7173
Pretend that the fictitious standard here stipulates that at least one pod MUST run in the namespace "namespace-test-a".
7274

75+
> [!NOTE]
7376
> The functions and behaviors to be tested MUST be precisely defined in a standard.
7477
> If you as a developer want to test something that you think is best tested but is not yet part of any standard, you MUST update the standard accordingly.
7578
@@ -178,6 +181,7 @@ cat results/plugins/scsconformance/sonobuoy_results.yaml
178181
Once all tests have been executed successfully, you can read the results and receive feedback.
179182
You can call up the results as follows:
180183

184+
> [!NOTE]
181185
> TODO:!!! to be described in more detail
182186
183187
### Clean up after

0 commit comments

Comments
 (0)