/
2009-03-20-my-two-weeks-in-qa.html
57 lines (46 loc) · 3.02 KB
/
2009-03-20-my-two-weeks-in-qa.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
---
title: My two weeks in QA
tags: qa
---
<blockquote>
We all tend to tie our self-esteem strongly to the quality of the product we produce - not the quantity of the product, but the quality. [Lister, DeMarco: "Peopleware"]
</blockquote>
<p>
For the last two weeks (equal to one <a href="http://en.wikipedia.org/wiki/Scrum_(development)">sprint</a>), I have been working in a QA role. Ever since laying off some QA people several sprints ago, we have been falling behind in our work. This time, it was decided that it was worth it to have one developer essentially be a QA person. Me.
</p>
<p>
Now, I have never done QA per say. I have tested my own code. I even answered support phones years ago. But never having played this explicit role before, I wasn't quite sure what to expect. Going into it, my definition of what a QA person does would have been:
</p>
<ul>
<li>Think about how the product is supposed to work, and document as many cases as possible.</li>
<li>Think about how the product could <span style="font-weight:bold;">break</span>, and document as many cases as possible. </li>
<li>Run through all your cases to see which if it's working the way it should, and not breaking in the ways you can think of.</li>
<li>Communicate with the developer(s).</li>
</ul>
<p>
Before this, if I had to break it down, I would have said that QA people spend 10% of their time writing test cases, and 90% executing the test cases.
</p>
<p>
Having done QA for just a week, it's clear to me that at least where I work, QA people spend 10% of their time coming up with test cases, 10% running test cases and 40% talking to developers and product owners. The other 50% is lost doing mundane tasks like building and deploying, and getting sniped to work on unrelated stuff.
</p>
<p>
For the first three days, I did nothing but come up with test cases and talk to other people about possible test cases. Lots of looking at the existing code to figure out possible ways to break it. Lots of conference calls.
</p>
</p>
After that, every day pretty much looked like the following:
</p>
<ul>
<li>9 AM - Download latest code, build, deploy</li>
<li>9:15 AM - Get the deploy actually working, usually involving new config, sometimes involving talking to developers.</li>
<li>10 AM - Run the test cases.</li>
<li>11 AM - Talk to developers about what is broken, what new test cases then have run into, what acceptance criteria they think will have to change.</li>
<li>1 PM - Document new test cases</li>
<li>2 PM - Talk to product owner about changes to acceptance criteria.</li>
<li>3 PM - Work on unrelated stuff.</li>
</ul>
<p>
Percentage of my day running test cases: 12%, max.
</p>
<p>
On the other hand, I was still playing a vital role in the feature. There is no question that without all the conversation around change management, we never would have delivered it on time. I guess what I learned is that a QA person spends a lot of their time making life easier for the developers. And, a lot of that doesn't directly relate to catching bugs.
</p>