Testing Experience Issue 19, September 2012

Record card

What the links show

The September 2012 issue was published as testingexperience19_09_12.pdf and mirrored under the issues folder, and the publisher's newsletter linked it from the cover image with query strings such as ?pk_campaign=New Issue&pk_kwd=Magazine Cover Image, in three spelling and encoding variants. Six shapes survive in the link record with fourteen referring domains between them. The clean root URL carries most of the equity (the anchor 'http://www.testingexperience.com/testingexperience19_09_12.pdf' appears on two domains with 41 links); the campaign-tagged shapes have three domains and more than 200 links from newsletter archives and mailing-list mirrors.

The campaign tags are the reason this site's redirect layer parses query strings and not just paths. A newsletter archive that links /testingexperience19_09_12.pdf?pk_campaign=... has to land on this page, not on an error, and the same logic strips the publisher's tags from links to the homepage, the issues list, the this-issue page and the write-for-us page. The page you are reading is where every shape of the issue 19 URL resolves.

The anchors do not attach a theme to issue 19, and no citing page describes an article, so this record does not claim one. The newsletter evidence does establish something else: by 2012 the publisher was distributing each issue by email to a list large enough that mailing-list mirrors and archive sites picked up the campaign links, which is how a September 2012 PDF ended up with over 200 links from a handful of domains.

Readers arriving from a 2012 newsletter link were current subscribers looking for the new issue. The equivalent today is the issue index for the archive and the guide hubs for current material: Test Management, Test Automation, Agile Testing, Testing Techniques and Testing AI Systems.

The six shapes of the issue 19 URL are worth listing because they show how one file accumulates variants. Shape one is the clean root URL, testingexperience19_09_12.pdf, two domains and 41 links, anchor equal to the URL. Shape two is the same path under the issues folder. Shape three is the https variant of the root. Shapes four to six are the root path with the newsletter query string (pk_campaign and pk_kwd) in three spelling and encoding variants, the kind of drift that happens when a mailing-list mirror re-encodes the HTML of a newsletter. Those three campaign shapes hold three domains and more than 200 links between them, which is the count of archived newsletter copies on a handful of list-mirror sites. No anchor describes an article; the campaign anchors are the cover image itself, so the link record for issue 19 is entirely about distribution and says nothing about content.

A reader who clicked the September 2012 newsletter cover wanted the new issue. The record attaches no theme, so the continuation is by period: 2012 is when continuous integration went from a developer practice to something test teams had to design for, and the continuous testing guide is the current answer to that design problem. Its Table 1 lists five pipeline stages with the tests that run at each, a wall-clock time budget and the gate rule that says who may override a failure; the section on keeping the commit stage under 10 minutes is the constraint a 2012 team most often broke. For a reader who wanted the load-testing side, the performance testing guide covers the test types and their reporting, and the test strategy guide's automation stance section fixes the policy in one paragraph.

The newsletter evidence also dates the issue to a specific moment in delivery practice. Martin Fowler's Continuous Integration article, in the 2006 revision that most teams read, described a build that ran on every commit with the unit tests included; by 2012 that was common, and the open question was whether acceptance, performance and security tests could be brought into the same pipeline. The continuous testing guide's answer, that each test kind runs at the earliest stage that can host it inside a fixed time budget, is the 2026 consensus, and Fowler's article was revised again in 2024 to reflect it. The magazine's own distribution followed the same arc: a quarterly PDF pushed by email in 2012 is a cadence no delivery team would accept for its test results now.