Skip to main content

Unmentioned skill of any Engineer - Being able to Google!!!

I've blogged elsewhere about what I look for when hiring QA Engineers, and it's full of useful things that I think are important in being a good QA Engineer/Tester.

One thing that is often overlooked and probably not really spoken off much, especially when hiring or looking for a new job, is something that is potentially extremely important when it comes to being a successful Engineer, and that is the ability to find out information. For most people this is being able to "Google" for something, or use Stack Overflow to find out a solution to a problem.

You could argue (and rightly so) that the ability to Problem Solve is what we are talking about, and you'd be right, but this is specifically really about being able to use Google effectively to find the answer you are looking for.

Why is being able to Google important?

There are a number of reasons for this:

1- Being able to structure your search query appropriately is important and can save time sifting through results

2- Once you have your search query nailed, there is no point reworking something that has already been done, there may be a library available that you can reuse, there may be examples that you hadn't thought of, there are a whole plethora of testing cheat sheets out there for example that if you can google can aid you in your testing efforts!

Here are some simple tips for Googling more efficiently:

1. Use "Quotes"- If you want to search for a term of more than one word, you can use quotes to tie words together. For example if you wanted to search for Test Strategy rather than searching for Test Strategy you might want to search for "Test Strategy"

2. Use - to exclude words - For instance if you wanted to search for Test Strategy but wanted to exclude for instance Waterfall you could search for "Test Strategy" -Waterfall

3. Make use of the OR key word - If you wanted to search for 2 things, you could use the OR key word, and by using quotes again we can search for "Newcastle relegated" OR "Sunderland staying up" This would get you results for both search terms...

4. Location is useful - You can search for something nearby and Google (providing it has access to your location) can search for things nearby which is pretty useful! Especially if you don't know where you are! So a useful search term might be "Testing meetups" nearby


  1. is so useful w.r.t this post. "Power Searching With Google" course.

  2. All are saying the same thing repeatedly, but in your blog I had a chance to get some useful and unique information, I love your writing style very much, I would like to suggest your blog in my dude circle, so keep on updates.

    SAP SD Training in Chennai

  3. I cannot explain the feelings I had while reading this blog. I was completely fascinated.apdm

  4. Cool website buddy I am gona suggest this to all my list of contacts.diploma of supply chain management


Post a Comment

Popular posts from this blog

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…

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.

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

        private s…