Testing

it might seem like final approval from the sme is the last step in your documentation journey think again! testing, and particularly regular testing, is essential for keeping your documentation usable, accurate and complete types of tests testing technical documentation involves a combination of manual and automated approaches depending on the tools and knowledge you have available, you can choose the right mix of the two manual testing works best for subjective or visual issues that tools can’t reliably detect for example, evaluating the tone of a document or checking image clarity automated testing is recommended for repetitive or technical issues for example, link validation or spell checking documentation testing checklist this is a non exhaustive list of tests you can run in you documentation 🔗 check all internal/external links , to avoid broken links or bookmarks 🖼️ validate alt text on images , for accessibility 🪜 ensure consistent heading structure , to make sure you didn't skip a heading level (for example, h1 followed by h3) ✍️ spell check , to avoid typos 💻 test all embedded code snippets and commands , to ensure that they can be copied and run correctly 📱 preview layout on mobile and desktop , to ensure good ux 🧭 confirm navigation and toc integrity , to catch any topics that may be missing from the toc 🏷️ check metadata (title, description, tags) , for correct indexing 🖼️ check image quality , to have a professional looking documentation 🗑️ find unused files , to avoid storing and publishing useless or out of date content 🗂️ check file naming , for standardization purposes and to avoid cross os issues 🔄 update variables , to make sure they apply to the current version 🎨 validate adherence to the style guide , for consistency 📅 periodically check if old content needs to be updated , to avoid stale pages the content level tests are generally done during the review phase and are detailed in reviewing docid\ sgn6dkqzatdpslqxvec5z some tools that can be used for testing documentation are presented in documentation workflows docid 5h9mqcohv ppru4jm6sve next step after testing, you can call your documentation complete the only remaining step is making it available to the users delivering docid 4n7aokmcvtzxcq5khmow3