Date: Fri, 29 Mar 2024 15:00:30 +0000 (UTC) Message-ID: <936383992.3.1711724430436@81eae2d3a063> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2_288202799.1711724430435" ------=_Part_2_288202799.1711724430435 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Normally we test the entire tree, but if it=E2=80=99s too big to= feasibly test, we can either prune levels, prune unnecessary bran= ches, or test specific subtrees instead.
Be careful not to miss content that doesn=E2=80=99t have its own page (u= sually because it=E2=80=99s =E2=80=9Chidden=E2=80=9D on a landing page).
We must decide how we=E2=80=99re going to handle duplicated cont= ent and shortcuts, as well as double-level headings.
If our page titles are different from their corresponding link names, we should use the link names in our tree.
We should name our tree's root (e.g. Home) so that it d= oesn=E2=80=99t get confused with our top-level headings.
When importing our structure into a tree-testing tool, watch for= problematic characters that may alter the topic levels or the tex= t itself.
In most cases, we should not use the tool=E2=80=99s =E2=80=9Cran= domize subtopics=E2=80=9D feature (if it offers one).