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

What is a PBI?

After my last post, I had the question of what is a PBI... so I thought i'd write a short blog post about what they are and why they are used. A PBI is an acronym for Product Backlog Item. It is a description of a piece of work that your SCRUM team will develop and deliver. When you have a list of Product Backlog Items, you then refer to that collective list as a Product Backlog. The product backlog is often prioritised and yourteam will work through each PBI, and release on a regular schedule... I am however going deep into the world of Agile development, which isn't entirely what this post is about, so I will stop myself now. A Product Backlog Item is made up of the following: Title - This is often a one liner that gives the team an idea of what the PBI is about, although it can just be an ID for the item and the team work off of that. Description - Breaks down the PBI in a bit more detail, and can be written in any style, however I prefer it to be written as follow...
68 comments
Read more

Coding something simple.... or not! Taking a screenshot on error using Selenium WebDriver

I recently wrote a little function that takes a screenshot at the end of a test if it has errored. What sounded very simple at the start turned out to be quite a bit of work, and quite a few lines of code to handle certain scenarios! It's now over 50 lines of code! I'll start with what I had at the beginning, this was to simply take a screenshot in the working directory, we are using SpecFlow and Selenium to run the tests, so we are going to check if the ScenarioContext.Current.TestError isn't null, if it is, then using Selenium, take a screenshot (note the below code is a simplified version of what I had at the beginning). [AfterScenario]         public static void TakeScreenShotOnError()         {             if (ScenarioContext.Current.TestError == null) return;             var screenshotDriver = Driver as ITakesScreenshot;             if (screenshotD...
14 comments
Read more

The Stickman Tester... The full version complete with deleted "scenes"!

As some of you may have seen, a little while ago I performed a 99 second talk on the Stickman Tester for the Ministry of Testing. Owing to the fact that it had to be 99 seconds, this unfortunately meant that a verse was left out in order to keep it within the time frame! It's only now that I have found the time to put the deleted verse/scene back in, and re-record it and upload it! (It's now a 120 second talk!) It talks about a testers journey in an Agile team, about how not everybody has it as good as others, and basically talks about not giving up, keep searching, or trying to change your role to make it what you want it to be. Anyway, here it is, in all it's glory. Hope you enjoy it!
15 comments
Read more