doc: reorganize test documentation

[gyliu513]

/kind documentation

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #11164

/cc @amy

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

[netlify]

✅ Deploy Preview for kubernetes-sigs-kueue ready!

Name	Link
🔨 Latest commit	7434538
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-sigs-kueue/deploys/6a0b2a2ab7605a00086057c2
😎 Deploy Preview	https://deploy-preview-11169--kubernetes-sigs-kueue.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[amy]

what does this mean: omit PLATFORM on amd64

[gyliu513]

Thanks @amy ! The phrasing is ambiguous. The intent is: on an amd64 machine, PLATFORM=linux/arm64 is unnecessary because the default platform matches the host, so you just run make kind-image-build test-e2e-baseline without any prefix. The PLATFORM= prefix is only needed on Apple Silicon to cross-compile for linux/arm64. I'll clarify the comment in the doc.

[amy]

LGTM! Besides the nit. Just confirming to whoever is reviewer for this that this is mostly just additive and any big red removal blocks were actually moved further down the doc. (But please address the nit)

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Details

Git tree hash: e288f0baadbb0be9819bc38e353ea91f012687ee

[amy]

/assign @tenzen-y

[amy]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Details

Git tree hash: 8bc9a22b60584a9e0c9ef2cdd7eb6ee1bc2ff178

[mimowo]

/approve
/cherrypick website
I checked the PR briefly, and it looks reasonable, promoting the lgtm from @amy. Thank you folks 👍

[k8s-infra-cherrypick-robot]

@mimowo: once the present PR merges, I will cherry-pick it on top of website in a new PR and assign it to you.

Details

In response to this:

/approve
/cherrypick website
I checked the PR briefly, and it looks reasonable, promoting the lgtm from @amy. Thank you folks 👍

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gyliu513, mimowo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• site/OWNERS [mimowo]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-infra-cherrypick-robot]

@mimowo: #11169 failed to apply on top of branch "website":

Applying: doc: reorganize test documentation
Using index info to reconstruct a base tree...
M	site/content/en/docs/contribution_guidelines/testing.md
M	site/content/zh-CN/docs/contribution_guidelines/testing.md
Falling back to patching base and 3-way merge...
Auto-merging site/content/zh-CN/docs/contribution_guidelines/testing.md
CONFLICT (content): Merge conflict in site/content/zh-CN/docs/contribution_guidelines/testing.md
Auto-merging site/content/en/docs/contribution_guidelines/testing.md
CONFLICT (content): Merge conflict in site/content/en/docs/contribution_guidelines/testing.md
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 doc: reorganize test documentation

Details

In response to this:

/approve
/cherrypick website
I checked the PR briefly, and it looks reasonable, promoting the lgtm from @amy. Thank you folks 👍

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.