It's Not Personal

It's not personal. I'm sure everyone has heard that said to them at one time or another throughout their lives, in this post I'm going to discuss what this means to me in testing from two perspectives: not catching every bug and not making found bugs personal.

Every time that a bug is found that was introduced by something you helped to test it is hard to not blame yourself for letting it slip through. It's hard to reason with why that isn't your fault and what you could have done differently to find it. The only way to get through those situations is, you guessed it, don't take it personally! Now, don't think that I am some expert at this. In fact, I struggle with this every single day. I still have to give myself pep talks every once in a while to remind myself not to take it personally and to just keep moving forward. 
There is no way to find every bug. That just is not possible, no matter how good you are, no matter how good your team is, something will…

Why Is Testing Important?

This question is one that you may be asked by people hearing about your job for the first time, by people who work in a company where they don't do testing or simply by people who are naive to the benefits of testing currently. So, why is testing important? This question is likely to put you on the defensive very quickly if you care about your job and the work you do so it's important to think about this question before it gets asked. In this post I will discuss why I feel testing is important and the different points I like to make when asked this question.

In May of 2017 I was at a talk given by Mike Lyles. He hit on this point in an interesting way that really stuck with me. Mike explained that when people ask you what the value that testing brings is you don't automatically discuss what you cost the company, don't discuss the resources you need, the key is to discuss how much has been saved by testing. What I took away from that talk, and that point in particular, …

What is Testing?

The ultimate question, what is testing? In case you aren't aware yet, there is no one answer. There are many different versions of testing (Hopefully I will post about some of the different methods at a later time). But the biggest point I would like to make in this post is about testing in the context of "follow the steps" testing vs thinking testing. The difference between the two of these, and which you end up doing, can make or break how you feel about testing.

"Follow The Steps" Testing Follow the steps testing is, sadly, how most people still view testing. This is a testing team that simply follows the same steps for every new feature or bug to make sure that nothing in that single flow is broken. This means that every time something in the code changes the same steps are performed to make sure that there are no new issues. 
Before I continue I feel the need to remind all readers that this is an opinion blog and this blog shows only my own personal opinio…

Who Am I and What's The Point?

If you don't already know who I am, my name is Bailey Hanna (hint, it's over at the side). As of right now I am a Software Test Specialist Co-op (intern) 13 months into a 16 month term.

As for "Whats's The Point?", I started this co-op term without knowing what software testing really was outside of reading my job description and a handful of testing blogs. This blog is designed to help people who find themselves in the same position learn some of the lessons I did through a blog instead of through experience. That being said, you will likely experience many of the same things I did, so perhaps it is more about letting you know how I handled those situations. That is not to say that I handled all (or any) of those situations ideally but at least you can learn whatever I did through those experiences.

This is a blog, that means that people all over the world can technically log onto the internet and see this whenever they please. Which means I feel the need to exp…