Testing Experience Issue 4, December 2008

Record card

What the links show

Issue 4 was published as testingexperience04_08.pdf and mirrored later as issues/testingexperience04_12_08.pdf. The root file alone has 19 referring domains and 238 links, which is more than any other 2008 to 2010 file; the mirrored copy adds two more. Four domains used the raw URL as anchor text and one Spanish-language site called it the '4th edition' (4o Edicion, five referring domains on that anchor alone), which suggests a Spanish testing community post that was republished or syndicated across several blogs.

The volume of links to a single issue is the interesting signal. A quarterly free magazine accumulates a few links per issue from readers who share the download; twenty-one for one file means either a widely shared article or an active promotion push at the end of the first year. The link timing (first seen in Ahrefs mostly 2013 to 2015, the index start, with last-seen dates spread to 2019) is consistent with links that were already old when indexing began, so the burst happened in 2009. Which article drove it is not recoverable from the anchors, and this record does not guess.

What is recoverable is the geography. The Spanish anchor, Portuguese summaries of the neighbouring issues, and English tester blogs point to the same picture the rest of the archive paints: a European magazine with an Iberian and Latin American readership that translated and summarized issues for its own communities. A German publisher's book page and a German serials catalogue also list the magazine as a title, which is where the anchor 'Zeitschrift Testing Experience' comes from.

For a reader who followed a link to the December 2008 issue, the relevant current material is the Test Management hub and the Agile Testing hub: the topics the magazine returned to most in its first years. The issue index shows how issue 4 compares with the rest of the run.

The shape of the issue 4 links repays a closer look. The 238 links from 19 domains on the root file is far more links per domain than the run's average, and that ratio is the signature of sitewide or template links: a blogroll entry or a sidebar item that repeats on every page of a blog counts once per page. The five domains on the Spanish '4o Edicion' anchor share the same wording exactly, which points to one post syndicated or copied rather than five independent reviews. The remaining anchors are the raw URL (four domains) and the magazine's title. No anchor names an article, an author or a page number, so the evidence stops at 'widely shared'. The mirrored issues/testingexperience04_12_08.pdf name adds two domains, both later tester blogs that picked up the renamed file.

A reader who followed the Spanish post or an English blogroll link in 2009 wanted the current issue of a free testing magazine, and the two things a test manager reading in early 2009 most often needed were a way to decide what to test hardest and a way to fit testing into a team adopting iterative delivery. The first is the risk-based testing guide: Figure 1 there is a 5 by 5 likelihood-times-impact matrix with red cells at 15 and above, and its table maps each risk class to depth of testing, techniques and share of effort, with a worked example of six features in one release. The second is the tester role in agile teams guide, whose first table shows how each responsibility moves from a phased project to a cross-functional team. Both are written for current practice rather than for the 2009 debate.

The test process a December 2008 reader worked inside was the ISTQB fundamental test process and, for documents, IEEE 829-2008. ISO/IEC/IEEE 29119-2, first published in 2013 and revised in 2021, restated that process in three layers: an organisational test process (policy and strategy), test management processes (planning, monitoring and control, completion) and dynamic test processes (design, environment set-up, execution, incident reporting). The layering matters for a reader of this issue because it separates the decisions a 2008 test manager made once per project from the ones made every day, and the test process guide follows that separation in its section on a regulated project. Risk-based selection, one approach among several in 2008, is the default the standard now assumes.