Theme Unit Test Checklist

The WordPress Theme Unit Test is a data set you import into a test WordPress installation to exercise content edge cases. It covers things that rarely appear in real content but that reveal layout or rendering bugs: very long titles, deeply nested lists, unusual post formats, extreme image sizes, and more.

Blaskan is tested against this data set before each release. This page lists the checks in plain terms, what to look for, and where to review the live results.

The live test installation is at themeunittest.blaskan.net. That subdomain runs the unit test data set against the current production build of Blaskan.

How to Use This Checklist

The checklist below covers the categories in the unit test data. For each item, view the corresponding post or page on your own test installation, then review it at three sizes: mobile (375px), tablet (768px), and desktop (1280px).

You can use any browser's developer tools to simulate different viewport sizes. Load the page, open DevTools (F12), toggle the device toolbar, and enter custom widths.

Content Formatting Checks

Text formatting and inline elements:

• Bold, italic, strikethrough, and underline render without overriding theme typography
• Inline code elements are visually distinct from body text
• Nested emphasis (bold inside italic) is legible
• Superscript and subscript do not disrupt line height

Headings hierarchy:

• H1 through H6 render at distinct, descending sizes
• H1 inside post content does not visually compete with or match the post title
• Heading spacing above and below is proportional
• Long headings (70+ characters) wrap cleanly without overflow

Lists:

• Unordered and ordered lists render with consistent indent
• Nested lists (three or four levels deep) maintain readable indentation and do not collapse to zero margin
• Definition lists render legibly if the theme styles them

Tables:

• Tables with many columns scroll horizontally inside their container at narrow widths
• Table headers are visually distinct from data cells
• Long table cell content wraps rather than overflowing the table container

Image Checks

Alignment:

• Left-aligned images in post content have text wrapping to their right
• Right-aligned images have text wrapping to their left
• Center-aligned images center within the content column
• Images larger than the content column width are constrained, not clipped

Edge sizes:

• A 1x1 pixel image renders without breaking the surrounding paragraph layout
• A very wide image (wider than the content column) scales down to fit
• A very tall portrait image fits within the column width without overflow

Captions:

• Image captions render below the image with distinct styling from body text
• Captions on large images do not extend beyond the image width

Post Format Checks

If your use of Blaskan includes post formats (Quote, Link, Aside, Gallery, etc.), confirm each format renders with appropriate visual treatment and does not introduce layout breaks.

Archive and Navigation Checks

Archive lists:

• Category archive renders correctly with the category title displayed
• Tag archive renders correctly
• Date archive (monthly, yearly) renders correctly
• Search results page renders correctly, including the "no results" state

Pagination:

• Previous/next post navigation renders on single posts
• Archive pagination renders on category/tag/date archives
• The "older posts" and "newer posts" links are keyboard focusable and have visible focus states

Sticky posts:

• A sticky post appears at the top of the homepage archive before non-sticky posts
• The sticky post is visually distinguished from regular archive entries (Blaskan applies a distinct marker)

Edge Case Title Lengths

• A post with a 200-character title wraps correctly and does not overflow the content frame
• A post with a single-character title renders without empty space anomalies
• A post with no title (empty title) does not render a broken empty heading

Comment Section Checks

• Comment list renders at standard depth
• Deeply threaded comments (8 or more levels) indent correctly without overflowing the column
• Comment form fields are clearly labeled and accessible by keyboard
• The reply link is keyboard focusable

Accessibility Checks to Perform with This Data

• Navigate the full unit test site using only the keyboard (Tab, Shift+Tab, Enter, Space, arrow keys)
• Confirm skip links appear on keyboard focus
• Confirm all interactive elements have visible focus indicators
• Run a screen reader over a post with headings, images, and a data table

For detailed accessibility documentation, see skip links, focus, and reading order and the accessibility overview.

After Running the Checklist

Note any items where behavior is unexpected. Most issues fall into one of three categories: CSS conflicts from a plugin stylesheet, content that relies on HTML not present in unit test data, or genuine theme edge cases. The support page is the right place for edge cases that need investigation.