Skip to main content

10 keys to a happy tester

Apologies for the lack of updates recently, I've been very busy (kids, work promotion), but I've also got a few blog posts lined up for the next month or so, which i think you'll enjoy, here's one of them for you!

I was thinking the other day over what makes a tester happy, and I thought I'd write down my findings, and share them with you, this isn't necessarily what makes me happy, but more around what I think can make any tester a happy tester :)

1 - Grow with your testing - Always look to progress as far as you can, never stop challenging yourself.
2 - Relationships - Relate with your other team members, become personable with them and talk to them about day to day stuff and not just work.
4 - Extra Mile - Go that extra mile to make things work, people will respect you for it, and people will do the same for you if you ever need it.
5 - A difference - Making a difference makes you feel valued and makes you feel part of a team that is delivering good to the world. Delivering value to the business helps make a difference, and makes you feel important.
6 - Team - Work together and don't work against people, working together as a team will reduce the stress on you and help you enjoy your work more.
7 - Try new skills - Learning new skills is hard and challenging, but rewarding. I read the other day:
“If you are willing to do only what’s easy, life will be hard. But if you are willing to do what’s hard, life will be easy.”  
and I think the above can be applied to testing and learning new skills, if you learn a new skill, sure it might be difficult and challenging, but it will no doubt make your testing a lot easier.
8 - Enjoy testing. 
9 - Aspiration - Aspire to be the best you can be, no matter what level you are at, aspire to be the best *insert job title here* ever!
10 - Enjoy testing. - It's that important that I've put it in twice!

I guess you can apply the above to most roles, but I've tailored it specifically for Testing, but I'm sure others could easily apply it to development etc!

Do you agree? Anything else you'd like to add?

Labels:

Comments

  1. Srinivas Kadiyala26 November 2013 at 06:07

    Great...Thanks for sharing...

    ReplyDelete
  2. Mauri Edo26 November 2013 at 12:22

    Nice but... where's number 3? :-)

    I agree with 9 but I am progressively learning to not be too hard on myself and allow myself to fail in order to progress, I guess that could be a good number 3 maybe.

    Cheers!

    @Mauri_Edo

    ReplyDelete
    Replies
    1. Gareth Waterhouse27 November 2013 at 00:19

      And that my friend is why you're a tester right!? Good spot!

      Delete
  3. Unknown26 November 2018 at 22:20

    Wmtorrents
    Get serial keys and generators to activate and crack your softwares including Keygens. By mode of softwares you can activate any softwares Proteus Crack With Activation Key

    ReplyDelete

Post a Comment

Popular posts from this blog

Testers: Be more like a Super-Villain!

Who doesn't love a Super Hero? Talk to my son, and he'll tell you how much he loves them, talk to many adults and they'll say the same! Deep down, we all love to be the Super Hero, we all want to save the day! However, I want to talk about the flip side of Super Heroes, the Super Villains... I often play Imaginext with my son, and I (unfortunately?) am nearly always the Super Villain! Be it Lex Luthor, Joker, Two Face, Mr Freeze or The Riddler! These are all great characters and great Super Villains, but why would I want to write about Super Villains? A while ago where I worked, we had a few Super Heroes, people who would be able to come in and "fix" things that had broken and help deliver projects on time. We then shifted, we decided to do away with the Super Hero culture and try and prevent from being in that position in the first place, whilst we didn't go as far as wanting to hire Super Villains, it's definitely a story that has stuck with me and t...
2 comments
Read more

Treating Test Code as Production Code

It's important when writing automated tests to remember that the code you write should be up to production standards, meaning any conventions that you have in place should be adhered to and that it should follow good design patterns. Too many people often say why does it have to be as good as production code, it's "Only" a test, so long as it passes then that's fine... To answer this we need to look at why we want our tests to be written in such a structured and efficient manner: - Maintainability - by making the test code structured and efficient, it becomes far easier to maintain and in doing so changes in the future can happen quickly as the test isn't linked to anything that it shouldn't be and it's easy to understand for a new set of eyes. - Durability - Again by making the tests structured they should be resistant to changes, if you change a variable name for instance then it shouldn't effect the unit test unless it absolutely has to....
1 comment
Read more

Tech Develops - A day dedicated to YOU!

Working in Tech, it can be difficult to find the time to further improve yourself, you're focused a lot on delivery, and it can be hard to drag yourself away from it and spend time on delivering an improved you. This is why some companies are starting to have time dedicated to your personal development, where people drop tools and do a personal project or watch some tutorials. Luckily working at ASOS we get the last Friday of every month to focus on this! Last Friday we held what we call a "Tech Develops" day, where as an employee of ASOS and working in Technology, In the week running up to it we decided it would be a good idea to have a platform where people could stand up and perform a 99 Second Talk about anything they please. We had 12 people sign up to it, and we had talks ranging from the technical (Git-Bisect) to a Conference review (UKStar). The first talk was an informative talk about Git Bisect and how it's used and why because of it, it's import...
3 comments
Read more