This is the final post in the types of software testing series. You can view the other 40 types of software testing in the following post: 20 Types of Software Testing, and 2o More Types Of Software Testing.
“So what would you say you do?” It’s a common question when meeting someone new. However I was blind sided by the timing of this question.
You see, I was on the phone with a recruiter who was fairly new to the game. We where going over my resume when I told here about a recent job and title change. That’s when the recruiter asked this haymaker of a question. I was stunned.
I went from working as a Software Test Engineer. Where I was doing only manually black-box testing. Then changing to a Software Development Engineer in Test, after they found out I could write code. The titles do share a lot of words in common but have huge differences.
Here’s what I should have told the recruiter.
This joke was sent around the office a few days ago. Thought I would share here.
Developer : I’m not able to replicate this issue. It’s working fine on my machine. So lets close this bug.Tester : I understand that it’s working fine on your machine, but we aren’t going to deliver your machine to our customers. Let’s see what’s different between the to environments.Developer : =(
Developer : I don’t always test my code but when I do it’s in production.Tester : Can you also check your environmental settings? It might not be as the same as production.Developer : =(
Just finished reading the Lean Startup by Eric Rise. It’s a great book about how lean manufacturing principles can be used to help startups innovate and succeed.
One of the concept from the book that I really liked is called the Five Whys.
Its origins in the Toyota Production System, and proposes that every supposedly technical problem is actually a human problem.
Five Whys is a root cause analysis and preventive maintenance technique that we expect to see on a manufacturing floor. The Lean Startup suggest that this concept can be used in startups. I agree and want to take it a step further by showing how we can use the Five Whys for software testing.
The end of the sprint was only a few days away. The team was working hard to make sure that all the features we had committed to. Would make it into production release. With a code freeze looming overhead tension were high.
On feature had just passed a flurry of quick code reviews becoming “Dev Complete”. The code was quickly checked in and the pushed out to our testing environment. At the same time I was informed that I would be able to start testing.
There was one problem though. I wasn’t able to log into the application. A previous commit had broken our testing environment.
If you’ve ever ran into a problem like this then having gated deployments is something you’ll want to look into.
Thankfully this post will tell you all about them.
What do you do when you’re job is to break things.
To find the weakness in something and then point them out.
To push back on work that others believe is finished.
To be the voice for the customer, an evangelist.To be a skeptic and highly critical, never being brain washed by the hype. Being a tester means that you have to weigh both sides.
If being in software development was a movie role than sometimes it would feels like testers are both the hero and the villain.
From Ask A Tester:
Misperceptions in software testing are not necessarily bad things. They are just part of the learning process. We may misperceive things when we get along the way with software testing and we also could realize these misperceptions when we have more experiences in software testing. The most important thing for the tester is never stop learning and sharpen our saws.