Joep Schuurkes (Posts about information debt)https://smallsheds.garden/categories/information-debt.atom2023-11-26T10:50:53ZJoep SchuurkesNikolaThe test case - an epistemological deconstructionhttps://smallsheds.garden/blog/2015/the-test-case-an-epistemological-deconstruction/2015-02-01T22:19:55+01:002015-02-01T22:19:55+01:00Joep Schuurkes<div><p><em>(This article was first published in Dutch in <a href="https://www.testnet.org/testnet/home">TestNet</a> Nieuws 18. The article below is a translation with minor changes. Many thanks to Joris Meerts and Ruud Cox for reviewing the original version.)</em></p>
<h3>Testing as an information problem</h3>
<p>Testing is an information problem. We are in search of certain information, of an answer to the question: does this application fulfill the relevant explicit and implicit expectations? The exact way in which we can answer this question, however, is not immediately clear. First we will need to decide which questions to ask, how to ask them and how to evaluate the responses. Hence, testing is an information problem.</p>
<p>For the traditional test methodologies (ISTQB and TMap being the most well-known) the test case is a large part of the solution. So let's take this solution apart epistemologically and see what it is we have in front of us. If the traditional test case is our solution, what information does a test case contain? What changes occur after executing it? And also, where is the understanding in all of this that's happening?</p>
<p>In this article, I will first describe how a typical test case is created and how it is used. Then we shall take a look at which kinds of information a test case contains. Finally, we will analyze where the understanding of what happens during testing, is present and where it is not.</p>
<p><a href="https://smallsheds.garden/blog/2015/the-test-case-an-epistemological-deconstruction/">Read more…</a> (10 min remaining to read)</p></div>Information debthttps://smallsheds.garden/blog/2014/information-debt/2014-07-13T16:50:21+02:002014-07-13T16:50:21+02:00Joep Schuurkes<div><p>Last week ago the following happened on twitter:</p>
<blockquote>
<p>New word of the day: "information debt". It's like technical debt, but related to information, communication, models, docs, visualisations.<br>
<em>- Joep Schuurkes (@j19sch) <a href="https://twitter.com/j19sch/statuses/486534198803841024">July 8, 2014</a></em></p>
</blockquote>
<div></div>
<blockquote>
<p>@j19sch: New word of the day: "information debt" => blogpost coming up ?!?!?<br>
<em>- Simon P. Schrijver (@SimonSaysNoMore) <a href="https://twitter.com/SimonSaysNoMore/statuses/486551279590977536">July 8, 2014</a></em></p>
</blockquote>
<div></div>
<blockquote>
<p>@SimonSaysNoMore Wasn't planning to, but now you made me think about it, so yes. Damn you! :-P<br>
<em>- Joep Schuurkes (@j19sch) <a href="https://twitter.com/j19sch/statuses/486555404089188352">July 8, 2014</a></em></p>
</blockquote>
<p>In case you don't know what technical debt is, you might want to read <a href="http://techblog.net-a-porter.com/2011/10/agile-tetris/">this</a> first. (It's the oldest source I could find of the technical debt-tetris analogy, by the way. If you know of an older one, please leave a comment.)</p>
<p><a href="https://smallsheds.garden/blog/2014/information-debt/">Read more…</a> (3 min remaining to read)</p></div>