Joep Schuurkes (Posts about manifesto)https://smallsheds.garden/categories/manifesto.atom2023-11-26T10:50:53ZJoep SchuurkesNikolaReflections on my testing manifestohttps://smallsheds.garden/blog/2018/reflections-on-my-testing-manifesto/2018-12-22T17:43:10+01:002018-12-22T17:43:10+01:00Joep Schuurkes<div><p>Earlier this month I published my <a href="https://smallsheds.garden/blog/2018/manifesto-for-software-testing/">Manifesto for software testing</a>. This manifesto is my attempt to bring together what I have learned about testing from the context-driven, agile and DevOps communities. Below you can find the manifesto with my reflections on it.</p>
<h5>1. Testing is investigating in order to evaluate a product.</h5>
<p>This definition is clearly influenced by James Bach's "questioning a product in order to evaluate it". I'm not sure at which point I started misremembering his definition as "investigating a product...", but it works well with a change I did make intentionally: moving "a product" to the second part of the definition. As explained in 6. I believe that in order to evaluate the product, we need to investigate a number of different things, not only the product.</p>
<p><a href="https://smallsheds.garden/blog/2018/reflections-on-my-testing-manifesto/">Read more…</a> (5 min remaining to read)</p></div>Manifesto for software testinghttps://smallsheds.garden/blog/2018/manifesto-for-software-testing/2018-12-04T20:44:51+01:002018-12-04T20:44:51+01:00Joep Schuurkes<div><p>1. Testing is investigating in order to evaluate a product.</p>
<p>2. An evaluation is a judgement about quality – quality being value to persons who matter.</p>
<p>3. This makes testing a fundamentally human and contextual activity.</p>
<p>4. As such, testing is an exploratory and open-ended activity, requiring continuous evaluation of and experimentation with our practices.</p>
<p><a href="https://smallsheds.garden/blog/2018/manifesto-for-software-testing/">Read more…</a> (1 min remaining to read)</p></div>