Month: February 2015

It’s a wild world – so go data driven with real world data

I didn’t see that one coming

The world works best when QA professionals do not get surprised a lot.
Actually never would be just fine. After some time you really do see it all, right?

Wrong.

There are some laws of nature that we tend to forget, or just push aside, but always comes back, like a karmic
boomerang of truth. If your system is more than trivial, and you run a database profiler, you will learn something new.
If you run a profiler on your code and stress it, you will learn something new.

If you run your system on real world (“production”) data – you will learn something new.

Mainly, that you have some unexpected bugs.

Keeping it real

Real world data have three things going for it:

  1. There is a lot of it.
  2. It is diverse, and in it’s way, devious.
  3. It mirrors issues with parts of the system that are not currently under test, including 3rd party issues.
  4. If your system has elements open to the world, you get calls that are invalid in just any permutation you can come up with.

Continue reading

The first API you should learn

Not a case of super heroes

 

After some time in the business, I started to work for an organization that,
for the first time, actually had QA engineers before me. I was still going to
be the only one, but I had a few weeks overlapping with the person leaving the job.

Nice place, nice people. Yet the (soon to leave) QA and one of the developers
were never seen together. Not around the (proverbial) water cooler, not
at lunch, not at all. In fact, the only communication they had was via the bug
tracking system, even though they were sitting less than 10 feet apart and in line of sight.
Continue reading

5 things you need to succeed in a QA job interview

1. Reliability

As a QA professional, you are the last and most important barrier between the evil, destructive bugs and the users. It might be disguised under some else’s title, but it is your thumb, pointing up or down that says if a version is getting released or not.

Stressful? Sure it is!.
Now think about the person that is interviewing for this position.
What do you think will be the absolute deal breaker? The slightest whiff, the fastest flicker, the faintest hum in the vibe if reliability might take you off the list.
I will never hire someone that I don’t trust, on both measurable and downright intuitive levels, for a position that places my bacon on the line.

So what does it means for you?

First make sure your CV are not misleading, hyped, or down right selling something you cannot deliver at a moment’s notice. Same goes to the interview itself: it is perfectly well to describe yourself in a highly favorable manner, but never say you know something when you do not. You can never know, the next questions might be very specific regarding your this very “something”.

 

Continue reading

© 2024

Theme by Anders NorenUp ↑