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

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...
15 comments
Read more

How to manage resources within new teams?

Working where I work we are constantly spinning up new teams to take on new workloads as business come up with new demands and new features they want developed and tested. The problem with this is how do we ensure the work of the newly spun up team is of sufficient quality. One method is by taking people from other established teams and placing them on the new team. This works great for the new team, but unfortunately it will oftenl eave the established team lacking in a resource whilst they try and fill the gap left by the person who has left. We are seeing this often with our offshore teams, it can be damaging to the team structure and the teams velocity, but try as I might, I can't think of another way around it. It's far easier to take 1 person from a team that is established than it is to build a whole new team from scratch. At least by leaving the core of a team in place, you should be guaranteeing that the new team are aware of any coding standards or any QA standard...
Post a Comment
Read more

Considerations when creating automated tests

We recently released to a number of teams our automated regression pack that has been worked on over the past few months. This regression pack tests legacy code, but contains a large number of tests.  As a bit of background, a number of teams are working on new solutions whilst some are still working on legacy code. With this in mind we constructed an email with a list of guidelines when creating new tests that need to be added to this regression pack.  I figured that these can be quite broad so should apply for any organisation, so thought it would make an interesting blog post...  So here goes,  when creating automated tests, it's important to consider and adhere to the following: - Think about data . The tests need to retrieve or set the data they need without any manual intervention - This should help them be more robust and easier to run without manual intervention. - The tests need to be idempotent - By making it so that each test is standalone and does...
Post a Comment
Read more