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

Testers: Be more like a Super-Villain!

Who doesn't love a Super Hero? Talk to my son, and he'll tell you how much he loves them, talk to many adults and they'll say the same! Deep down, we all love to be the Super Hero, we all want to save the day! However, I want to talk about the flip side of Super Heroes, the Super Villains... I often play Imaginext with my son, and I (unfortunately?) am nearly always the Super Villain! Be it Lex Luthor, Joker, Two Face, Mr Freeze or The Riddler! These are all great characters and great Super Villains, but why would I want to write about Super Villains? A while ago where I worked, we had a few Super Heroes, people who would be able to come in and "fix" things that had broken and help deliver projects on time. We then shifted, we decided to do away with the Super Hero culture and try and prevent from being in that position in the first place, whilst we didn't go as far as wanting to hire Super Villains, it's definitely a story that has stuck with me and t...

Treating Test Code as Production Code

It's important when writing automated tests to remember that the code you write should be up to production standards, meaning any conventions that you have in place should be adhered to and that it should follow good design patterns. Too many people often say why does it have to be as good as production code, it's "Only" a test, so long as it passes then that's fine... To answer this we need to look at why we want our tests to be written in such a structured and efficient manner: - Maintainability - by making the test code structured and efficient, it becomes far easier to maintain and in doing so changes in the future can happen quickly as the test isn't linked to anything that it shouldn't be and it's easy to understand for a new set of eyes. - Durability - Again by making the tests structured they should be resistant to changes, if you change a variable name for instance then it shouldn't effect the unit test unless it absolutely has to....

Tech Develops - A day dedicated to YOU!

Working in Tech, it can be difficult to find the time to further improve yourself, you're focused a lot on delivery, and it can be hard to drag yourself away from it and spend time on delivering an improved you. This is why some companies are starting to have time dedicated to your personal development, where people drop tools and do a personal project or watch some tutorials. Luckily working at ASOS we get the last Friday of every month to focus on this! Last Friday we held what we call a "Tech Develops" day, where as an employee of ASOS and working in Technology, In the week running up to it we decided it would be a good idea to have a platform where people could stand up and perform a 99 Second Talk about anything they please. We had 12 people sign up to it, and we had talks ranging from the technical (Git-Bisect) to a Conference review (UKStar). The first talk was an informative talk about Git Bisect and how it's used and why because of it, it's import...