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







Comments

  1. https://coursebuilder.withgoogle.com/sample/preview is so useful w.r.t this post. "Power Searching With Google" course.

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

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

    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...

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...

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!