[Developer Guide Audit] Testing

[mrbobbytables]

Documentation is the go-to reference for contributors. Parts of the developer guide have been cited as vastly out of date (e.g. referencing VERY outdated versions of docker). We are asking each SIG that owns a portion of the developer guide to audit their devel guide documentation.

This does not have to include updating it.
(although if you want to, please go ahead 😄 )

If you could, update this issue with items that are out of date or you think should be added to the testing portion of the devel guide.

Assigning to leads, but please feel free to re-assign and delegate.
/assign @BenTheElder @spiffxp @stevekuznetsov

Related Item
-Update e2e testing guide

---

Parent Tracking Issue: #5229
/sig storage
/sig contributor-experience
/area developer-guide
/kind documentation
/milestone v1.20

[pymander]

@Riaankl Let's make sure to link the e2e-testing changes here.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[spiffxp]

/remove-lifecycle stale
/priority important-longterm
/help
Fresh eyes from new contributors are the best way to identify gaps in our documentation