OUR METHOD

How we test Textidy

Textidy publishes small, local text-editing tools and guides explaining their behaviour. The editorial name “Textidy” identifies the product team; it is not a claim of independent certification.

Examples must match the tool

Our public test cases pair synthetic inputs with expected outputs or expected errors. Automated tests run these fixtures against the same transformation functions used by the editors. We include cases where a tempting automatic edit would be wrong, such as joining a meaningful line-ending hyphen.

Preserve a way back

The editor keeps your original while the page remains open. Code contents, citation text and relevant structure have preservation checks. Not every formatting character is disposable: invisible joiners can carry meaning, and a table row with extra data needs review. Conversion is not fact-checking or authorship detection.

Test the whole workflow

Browser checks exercise input, options, original comparison, clipboard fallbacks, downloads, keyboard access and narrow layouts. We also check that pasted text is not sent to remote conversion services. These checks use synthetic content and cannot prove that every document or device will behave identically.

Clipboard output is not universal compatibility

Formatted copying supplies HTML and plain text. Word, Google Docs and email editors can apply their own rules. A successful browser copy does not prove a successful paste into each application. Destination-specific checks are reported with the application and date when available; where a guide says testing is pending, it remains pending.

Recorded paste checks

On 11 September 2026, we copied the “Headings, links and a table” built-in example from the Codex in-app browser on macOS into Word for Mac 16.112.3 and Google Docs. In both, the heading, bold text, hyperlink, numbered list and two-column table survived. The applications applied their own fonts and spacing; the tables appeared without borders. We checked the visible result and exported document structure. This is one synthetic case, not a test of every Markdown feature, browser or operating system. Email editors and mobile destination apps remain untested.

Update claims when evidence changes

Guide dates are stored per article and updated for meaningful changes to its instructions or examples. We do not refresh every date on each site build. Search performance, test results and support reports inform revisions, but a higher word count is not an editorial target.

Report a reproducible problem

Email hello@textidy.com with the tool, browser, settings, a synthetic input and the expected result. Please do not send private documents, credentials or personal data. See our privacy explanation and About page.