About Testing Experience

Testing Experience is an independent knowledge base for professional software testers. It publishes reference guides on test management, test automation, agile testing and testing techniques, and it maintains an evidence-based archive record of the magazine of the same name that was published from this domain between 2008 and 2014.

Original magazine

28 quarterly issues, March 2008 to December 2014

Relaunched

2026, under new and independent ownership

Editor

Daniel Weber

Original PDFs

Not distributed here

Advertising, affiliates, cookies

None

Corrections

Fixed within a week of confirmation

The relaunch. The original Testing Experience was a free quarterly PDF magazine from a Berlin testing consultancy, edited by Jose Diaz, which stopped publishing after its 28th issue in December 2014. The website stayed up for some years and then lapsed. The domain was acquired and relaunched in 2026 by a new, independent owner. This site is not the original publisher, has no connection to that company or its staff, does not hold the magazine's archive, and does not distribute the original PDFs. It keeps the name because the name describes what the site is about, and it keeps a record of the issues because about a thousand websites still link to them and deserve an honest landing page rather than an error.

The editor. Daniel Weber is the editor responsible for every page on the site. He has worked as a tester, test automation engineer and test manager on product and consultancy teams in Germany and the United Kingdom, and writes the guides from that experience and from the standards and books each guide cites. Every guide and issue record carries his byline and the month it was last reviewed. His editor profile sets out his background and how he works, and he can be reached through the contact page.

How guides are written. Each guide starts from a question a working tester actually searches for, states the direct answer in a quick-answer card, and then earns that answer with a figure or table, a worked example, and sources named so that a reader can check them. Guides are reviewed against ISO/IEC/IEEE 29119, the ISTQB syllabi and glossary, the TMMi model and the books in their sources list. Numbers in worked models are labelled as illustrative where they are not from a named source, with an instruction to replace them with the reader's own data.

Editorial rules. No vendor, product or company names appear in the guides, so that the material stays true as tools change. No advertising, sponsorship, affiliate links or paid placement of any kind; the old site's advertise page and media kit have no successor here, and requests to place content or links are declined. No cookies, no advertising trackers and no cross-site tracking; the only measurement is privacy-first, cookieless page view statistics in aggregate, described on the privacy page. No text is generated for the sake of length; every page has a floor of substantive words and is cut if it cannot meet it honestly.

The archive record. Each issue page states only what the sites that link the issue establish: file names, referring domain counts, anchor text, the kind of page that linked it, and a theme where a citing page names one. Nothing is asserted about an issue's contents beyond that, and article authorship is stated only where a file name or a citation establishes it. If you were an author or reader of the magazine and can correct or extend a record, the contribute page explains how.

The editorial process. A guide begins as a question written the way a tester types it into a search box, and a one-line answer the editor is prepared to defend. The draft is built outward from that answer in a fixed order: the figure or table that opens the page, the worked example with its numbers, the comparison table, the limits, and only then the prose that connects them. Before publication each guide is checked against one named standard or book: the test management guides against ISO/IEC/IEEE 29119 and Rex Black's Managing the Testing Process, the technique guides against Lee Copeland's A Practitioner's Guide to Software Test Design and the ISTQB syllabi, the agile guides against Crispin and Gregory and against Adzic, and the AI and authenticity guides against the ISTQB AI testing syllabus, the C2PA technical specification and the NIST overview of synthetic content. A claim the check cannot support is cut, or rewritten as an opinion and labelled as one.

How figures are built. Every figure and table is drawn from data that is either cited or declared. Where a figure shows published numbers (the relative cost of a defect by stage, a false positive rate from a named study) the source is in the guide's list and the figure repeats the value without smoothing it. Where a figure shows a worked example, the counts are invented but realistic, the caption says so, and the arithmetic is shown in the text so that a reader can substitute their own numbers. Figures are drawn as plain vector graphics served from this domain, with the values in the markup, so that they read correctly in a screen reader and print without colour.

What the site will not publish. Reviews or rankings of products. Claims that a detector, a watermark or a provenance system is reliable, or that any tool defeats one. Statements about what an issue of the original magazine contained beyond what the link evidence establishes. Guides that cannot be tied to a standard, a book or a published study. Anything written to reach a length, and anything sent by a vendor, an agency or a search engine optimisation contractor.

The archive's evidence rule. A record may state only what a page outside this site establishes and a reader can check. A file name is stated because a referring page links it. A referring domain count is stated because it was counted on a named date from public link data and can be recounted. A theme is stated only where a citing page or its anchor text names one, and an author only where a file name or a citation names one; the words 'not established' appear wherever the evidence stops. Contributions from people who wrote for or hold the magazine are marked as contributed rather than derived, so that the two kinds of statement never mix. The rule costs the records some detail, and it is what makes them honest.

Corrections. Errors are fixed within a week of being confirmed, and the page's review month is updated. Substantive corrections are noted at the foot of the affected page. The workflow is fixed: a report arrives through the contact page with the page address, the sentence and a source; the editor confirms it against the source within a week, or replies to say why it does not hold; a confirmed error is corrected, the review month is updated, and a substantive correction is noted at the foot of the page with the date. A correction that changes a figure or a table triggers a re-read of the whole guide before the review month changes.