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?

Comments

  1. 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. And that my friend is why you're a tester right!? Good spot!

      Delete

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 follows: 



By writin…

Dealing with Selenium WebDriver Driver.Quit crashes (Where chromedriver.exe is left open)

We recently came across a problem with Selenium not quitting the webdriver and this would then lock a file that was needed on the build server to run the builds.

We were using Driver.Quit() but this sometimes failed and would leave chromedriver.exe running. I looked around and found this was a common issue that many people were having. We (I say we, as we came to the solution through paired programming), came up with the following, that would encapsulate the driver.quit inside a task and if this task takes longer than 10 seconds, then it will clean up any processes started by the current process, in the case of the issue on the build server, it would kill any process started by Nunit.

[AfterTestRun]
        public static void AfterTestRun()
        {
            var nativeDriverQuit = Task.Factory.StartNew(() => Driver.Quit());
            if (!nativeDriverQuit.Wait(TimeSpan.FromSeconds(10)))
            {
                CleanUpProcessByInheritance();
            }
       }

        private s…

Advantages of using Test Management tools

Before I start talking about test management tools, let me clarify what I mean by the term test Management tools...  I am not taking about your office excel program where you store your test cases in. I'm talking about bespoke test Management tools, your quality centers or Microsoft test manager...
In the strict case of the term test Management tool, Microsoft Excel can be used as such, but heck, so could a notepad if used in the right way... For the sake of this blog post I am talking about bespoke test Management tools.
Firstly, what test tools are out there? There are many more out there today than when I first started in QA over 5 years ago. When I started the market was primarily dominated by a tool called Quality Center, this would run in a browser (only Ie unfortunately) and was hosted on a server.. Nowadays it's market share has somewhat dwindled, and there are some new kids on the block. 
One of the more popular tools is that of Microsoft Test Manager, it's big…