Skip to main content

Testing drunk

(My first blog writing ever.)

 I've been thinking a long time that it's funny how many bugs I find by accident. Try to do something, make a mistake and boom - a bug is found. 

Making the mistakes intentionally doesn't quite work - that's why they are called accidents I guess.. So I've thought of ways to make myself more prone to accidents, coming up with an apparent one; testing drunk. TUI (testing under the influence).

 So this I gotta try. More to come on that later.
Labels:

Comments

  1. Anssi LehteläNovember 16, 2012 at 8:51 AM

    First try failed. Too drunk.

    Need to start testing part earlier next time.

    ReplyDelete
  2. MiikaNovember 22, 2012 at 9:19 AM

    Are you sure you will do right mistakes when you're drunk? ;)

    ReplyDelete
  3. Anssi LehteläNovember 22, 2012 at 11:50 AM

    Hi Miika, and thanks for your comment! First one ever here :)

    On your question, I don't think there are right or wrong, just different kind of mistakes.

    More important than that is that you make as various kind of mistakes as possible. Believe it or not, but just yesterday a tester of mine found a bug by accident, after making three mistakes in a row, and then when undoing his steps a problem was noticed -> one of the mistakes done (correctly) triggered an action on another object, but undoing the action didn't undo the action performed on the other object. And that was a valid semi-serious bug. How marvellous!

    In the drunken part I see a problem though, as after mistakes are made, the problems might still not be that obvious and that's where perception should kick in. And drunken perception might not be that effective..

    Fortunately there are other ways to make accidents happen that I have thought of (so my liver still has a chance). My tester fell into one which is trying to do many things at the same time. Trying to do stuff really quickly is another quite common one and pretty easy to mimic. Can you Miika think of any other ones?

    ReplyDelete

Post a Comment

Popular posts from this blog

Testers doing test automation - is that the most important thing for you to do right now?

I've been thinking quite a lot about tester's moving to do test automation.  Lately beause of these three things: 1.  European testing conference , a great testing conference I attended couple of weeks ago. It is very cool due to many things; the way the speakers get compensated, the focus on the conferring side of conferences making it very easy for people to discuss stuff, the way the talks are chosen, and because there are also a lot of developers joining. So anyway when I was talking with several of the attendees, it was a bit strange how it was easier for me to talk about the product development as a whole with the developers, where as with the testers it more naturally moved into talk of automation and tools. Also on the open space, I think the majority of the topics pitched was automation or tool related. And quite little on the process or on the customer facing side of product development.  2. In my company there are a lot of different products and...
3 comments
Read more

Six reasons why testers should do code reviews

I have had quite a lot of discussions about code reviews. Quite many also with testers, by which I have understood that many do not do those. I will not start arguing here on whether code reviews are good/important or not. But I will list a few things why I think testers would benefit of doing them. 1. Code is the only documentation that is up to date . If you really want to know how something really functions, you want to be able to see and read the code. 2. Knowing more about the thing done enables you to do better testing . You can spot things that you should definitely test, and things that you probably don't need to test that much. Like extra things added by coder, usage&modifications of existing functions, data types, etc. And to arguments thinking that one loses their "independence" as a tester by knowing too much, I would worry a lot less about that than about testing stuff that you have no idea on how it has been built. 3. Improve logging . I obse...
2 comments
Read more