Joep Schuurkes (Posts about tools)https://smallsheds.garden/categories/tools.atom2023-11-26T10:50:51ZJoep SchuurkesNikolaMetrics, models and conversationshttps://smallsheds.garden/blog/2023/metrics-models-and-conversations/2023-03-12T10:11:25+01:002023-03-12T10:11:25+01:00Joep Schuurkes<div><p>A few weeks ago someone suggested we should start measuring how many automated test cases versus how many manual test cases we have. Luckily it was part of a longer list of suggested metrics and it was also presented in that way: a list of options, to be discussed later. And the reason I say "luckily" is because I knew I disagreed with using that metric, but didn't have a good explanation as to why. At that moment I could have given a minutes-long monologue about how that metric doesn't fit how I think we should be thinking about testing. However, I have zero expectations that such a monologue could have worked in that situation. It would be all over the place as I philosophize about testing and make all kinds of connections and analogies. A convincing argument that does not make.</p>
<p>So since then, I've been thinking: how would I explain my position on measuring manual versus automated test cases? Something to the point, something relatable, something that acknowledges the need behind asking for this metric. And then it hit me: use cooking as an analogy. Now I know plenty of people have made this analogy before. However, I don't remember reading everything I will cover in this post somewhere else. Also, there's value in different people saying similar things, but each in their own voice.</p>
<p><a href="https://smallsheds.garden/blog/2023/metrics-models-and-conversations/">Read more…</a> (4 min remaining to read)</p></div>My note-taking system for workhttps://smallsheds.garden/blog/2023/my-note-taking-system-for-work/2023-03-01T15:39:25+01:002023-03-01T15:39:25+01:00Joep Schuurkes<figure><img src="https://smallsheds.garden/images/2023/note-taking-system/notebook-and-pen.jpg"></figure> <div><p>Ever since I started working back in 2006, I've used a notebook. Initially, I didn't have a system, I just wrote things down. Then, about seven years ago, when I became a scrum master, my notebook became more important. As a tester, I could use my team's board to keep track of my work. As a scrum master, none of my work was on the board. And even though my role has changed several times since then, my need for keeping track of things hasn't.</p>
<p>So somewhere along the way - and to be honest I forgot when exactly - I created my own system of note-taking based on bullet journaling. It's simple and straightforward. It helps me plan my day, list possible future actions, and keep a record of what I've been doing. On the one hand it seems like something small and simple. On the other hand it has been a major help to me, so I figured it's worth sharing.</p>
<p><a href="https://smallsheds.garden/blog/2023/my-note-taking-system-for-work/">Read more…</a> (8 min remaining to read)</p></div>Our work management tools are limiting our imaginationhttps://smallsheds.garden/blog/2023/our-work-management-tools-are-limiting-our-imagination/2023-01-29T22:34:25+01:002023-01-29T22:34:25+01:00Joep Schuurkes<figure><img src="https://smallsheds.garden/images/2023/work-mgt-tools/fig4-stories-on-a-wall.jpg"></figure> <div><p>Several weeks ago I had a thought that felt both serious and not serious, so <a href="https://chaos.social/@joeposaurus/109635747014542350">I asked on Mastodon</a>:</p>
<blockquote>
<p>Should I write a blog post about companies leaving money on the table by not leveraging their choice of work management tool (Jira, Shortcut, etc) as a competitive advantage?</p>
</blockquote>
<p>31% said "yes" and 54% said "a post about what now?", which I suppose reflects my own feelings about the topic. And it motivated me to write this post - especially that 54%. So let's talk about work management tools, the original (user) stories, affordances and constraints, and how these tools are limiting our imagination. </p>
<p><a href="https://smallsheds.garden/blog/2023/our-work-management-tools-are-limiting-our-imagination/">Read more…</a> (11 min remaining to read)</p></div>It's time to retire our test case management toolshttps://smallsheds.garden/blog/2020/its-time-to-retire-our-test-case-management-tools/2020-07-19T16:38:17+02:002020-07-19T16:38:17+02:00Joep Schuurkes<div><p>Recently the topic of test case management tools popped up a few times in my surroundings. In almost all cases I'd recommend against using these kinds of tools and I found myself able to give a few reasons, but also found that my thoughts lacked the clarity I'd like them to have. Hence this blog post, to force myself to think more deeply and communicate more clearly.</p>
<p>Before I go into that, there are a few things this blog post is not about. I won't be really going into what effect test cases have on test execution, or rather if test cases are a good tool to use when doing actual testing. Personally I don't think they are and I wrote about my inability to use them in <a href="https://smallsheds.garden/blog/2013/test-cases-cant-do-m-no-more/">this post from July 2013</a>. For some deeper thoughts on this, I recommend James Bach's and Aaron Hodder's article "<a href="https://www.testingcircus.com/documents/TestingTrapeze-2014-February.pdf#page=31">Test cases are not testing: Towards a culture of test performance</a>".</p>
<p>What I do want to cover in this post is managing test cases. Having a collection of test cases stored somewhere to re-use across releases and reporting their pass/fail numbers. Both are important use cases for a test case management tool and both are in my opinion a bad idea.</p>
<p><a href="https://smallsheds.garden/blog/2020/its-time-to-retire-our-test-case-management-tools/">Read more…</a> (12 min remaining to read)</p></div>