Skip to main content

Posts

Answers to common questions asked from a "tester"

Here's another chat I have had many times. It starts with the golden and notorious question of "how much should you test". And it then drifts a bit from there. ******** How much should you test? "Well, you know, I used to work once in this team doing a medical device where releasing frequently was not really possible due to the many constraints. And even doing a small release would cost a lot . And it being a class C (death or serious injury may occur) device all issues found on a released product would have been a pretty big deal. So this meant that we took unbugginess very seriously, and thus that I had a lot of time to spend testing the device. And boy did I. I spent sometimes almost like the entire week just in front of the machine testing, thinking of ways how it could fail, unrolling all the test techniques I got in me, learning the ins and outs of the product. And then one day when the new release was done.... several problems were found. So taken ...

Honesty pays

I share this story every once and then when talking to people, so thought to write it here too. About 8 years ago I had got my second consulting gig, working on a big company and on a huge project. And as huge projects normally go it was already very late and presumably very over budget. This had caused a pretty tense atmosphere around the project and things that delayed it further were not looked very fondly on.  And so it happened that I made a mistake of that sort. It was kind of done by a person I was "coordinating", failing to provide a complete set of specifications we had worked on to a vendor, resulting in a release missing a lot of important stuff. I was very stressed being a pretty new kid on the block and considering my options, whether to lay low, blame the coordinate or the vendor, quit, etc. But in the end decided that I would go for admittance. So I walked to the office of the rather intimidating program manager, knocked, went in and said that "I messe...

It was a good day

Decided to write down today the stuff I (remembered to have) had done today. And as paper doesn't store so well, thought to write it here as well.  So here in a semi random order: Reviewed code for a change now implemented that had planned couple of days earlier. Mainly to understand how it had been done, but dropped two comments still; one on a missing log event, and another one on the naming of a method. Also asked another team member explain me a thing I didn't totally understand (it was a lazy loading feature so now I know). Coffee Did some happy path testing for the change, looked good. Discussed through the status and next steps of a cool new feature started yesterday. It seemed devs where far with the implementation already and not that much was missing. Got pretty excited of the feature Identified and discussed a possible fix with a dev for a thing I had heard yesterday about from a customer. Replied back to customer Tested one new feature a bit and noticed ...

Back on the wagon

I reread some of my old blogs and was a bit sad not to be able to read anything from the past three years. So I thought I need to force myself to start writing more again. So here goes. Past almost three years I've been working on a really cool team, with a lot of freedom (and some responsibilities) to do a lot of different things. And  quite a lot has happened in our team inside the last three years. We have moved from one month sprints TO sort of a one piece flow based kanban with a weekly cadence  one big team TO (semi) self-organizing work groups. lot of solo work TO work in the mobbing style PM led Reviews TO team led show sessions unappreciated monolithic architecture TO appreciated monolith + bunch of other services architecture nebula TO AWS + many many more things TO other kind of things And I'm thinking of writing on all of these a bit. But also many things have happened in me.  First of all I have stopped clinging on the thought of ...

Regulations on medical software development kill more than save

After a two years as a sw testing specialist in the medical device industry, I decided to quit my job. Reasons were many, but perhaps the biggest one is the insane situation where regulations have taken the industry. As a summary, I have come under the belief that these regulations kill more people than save. This is because of: - the unbelievable opportunity cost - the delay in time to market - killing of innovation - restricting of competition and because of the fact that regardless of all those regulations, you still can fake it all. Actually it is easier to fake than follow. The main idea in the regulations is that everything needs to be planned in detail, executed accordingly, and documented to be done this way. And by planned in detail, they mean that there needs to be a documented plan, in which all the actions taken needs to be specified. If you do something that was not in the plan, you are in trouble. If you don't do something that was in the plan - boy are yo...

Testing playbook #1

So it's summer time again, and my year long spell as a scrum master is starting to be over. So starting August I'll be a full time tester again! (Or, as much as you can be a full time tester when working in a scrum team..) I'll likely write up some experiences on being a scrum master later (summary: hard, abstract, frustrating, fun), but thought now to start writing up on testing again. I'll start by sharing some of the tactics I often deploy when approaching testing situations. So this should become a series, until I get bored on it. So I'll start with my classic, my "master" tactic that often acts as a framework to other more subtle testing tactics. This is a rather common way for me to approach situations more on the exploratory and less on the confirmatory side, and/or situations where the thing (it may not always be the system) under test is not yet that common to me. It's rather simple: 1. Take a tour 2. Decide the target 3. Go with the h...