Skip to main content

Useful browser addons for QA

With so many browsers to choose from nowadays, it's important to choose the right one.

 For me, the wide array of add-ons that are available to aid my day to day job, definitely play a part in my choice. I choose Google Chrome, having an Android phone, means I can sync my favourites between my Mac, my phone and my work PC (100% personal reasons! There are some professional reasons below!)

 There are also a wide array of add-ons that Chrome supports that helps make my life easier, and I strongly recommend any QA have when testing a web UI.

 These are the ones that I use on a regular-ish basis:

 Fiddler - not really an addon for Chrome, but essential in monitoring HTTP requests and responses. It enables you to change requests/responses by setting breakpoints etc. Fiddler in itself could and one day will have a whole blog post about the benefits and the uses and how it can aid with testing. 
Fiddler can be downloaded from here

 FireBug - This is essential. I can not understand how a browser can not have this addon installed! It's so powerful in investigating bugs. Here are just some of the things you can do with Firebug:

  • Editing and Monitoring CSS and Javascript - Using firebug you can edit css on any live html page, which is nice to do when some formatting isn't quite right, you can investigate why and even add to the bug how it can be fixed :) As for Javascript, being able to monitor javascript calls during the loading of a web page can save a lot of time, you can even investigate javascript errors using Firebug if you feel comfortable enough!
  • Helpful in automating tests as it allows you to view the element information that you'll need for interacting with the page when writing automated tests.
Firebug can be downloaded from here


 Y-Slow - This is an extremely useful tool, it grades the webpage, and is extremely useful in suggesting possible improvements for sitespeed and validating the source of the page. 

YSlow can be downloaded from here

 Modify HTTP Headers - This is a firefox only addon, although there are similar tools for Chrome. This allows you to change the headers to alter website behaviour. I have personally used it so the website under test thinks I am visiting the site from another location, so it is definitely useful when testing international websites.

 Can be downloaded from here

 ScreenGrab! - This is useful when raising bugs! You can get it to take a screengrab of the entire webpage, not just the visible portion of the screen. 

 Can be downloaded from here

Spoons.net - Not really an addon, but extremely useful cross browser testing tool, that enables you to test on any of the latest browsers. If you wish to test on legacy browsers, then a pro account is needed (£££)... It's free to sign up and test on the current versions of browsers :)

Can be viewed here

Ghostery - Useful addon for seeing what affiliates and what tags are fired on your website. Can be downloaded for any browser. Makes testing things like webtrends and Google Analytics a lot easier!

 Can be downloaded from here

Feel free to leave a comment of anymore plugins that you find useful and why!
Labels:

Comments

  1. Srinivas Kadiyala2 April 2013 at 05:13

    Thanks for sharing,
    I have tried "Y-Slow and Ghostery"

    I didnt find much useful for testers. nor my developer has not accepted that.
    Can u explain - how would you use best of it?

    ReplyDelete
    Replies
    1. Gareth Waterhouse2 April 2013 at 05:33

      Y-Slow is powerful in that it gives the website page a ranking, and as such you can easily see if there have been any decreases in performance if you run it regularly. Ghostery is useful, as it shows immediately what tags are firing within the browser, and from there you can see if a tag is missing or not.

      Delete
  2. Simon2 April 2013 at 05:44

    Thanks for these Gareth. I've added Ghostery to Chrome. It's always cool to stumble across these posts and discover something new that might make my life as a tester slightly easier. :-)

    ReplyDelete
    Replies
    1. Gareth Waterhouse2 April 2013 at 08:28

      No problem! Don't suppose you have any useful addons that you wish to share?

      Delete
  3. The Disciple12 April 2013 at 02:18

    Add the following to the list. HTTPWaTCh, Firecookie and Firepath

    ReplyDelete
  4. Morvader23 February 2016 at 07:42

    Have a look to my Exploratory Testing Chrome Extension. Any feedback is welcomed.

    https://chrome.google.com/webstore/detail/exploratory-testing-chrom/khigmghadjljgjpamimgjjmpmlbgmekj

    ReplyDelete
  5. Mirnalini Sathya18 March 2017 at 04:50

    Excellent blog about selenium!!! Keep updating your information to gain knowledge on Selenium testing tool Selenium Training in Chennai | Selenium Training
    Selenium Training in Chennai | Selenium Training

    ReplyDelete
  6. BrendaPalmeri28 July 2017 at 00:01

    It’s too informative blog and I am getting conglomerations of info’s about Dotnet certification. Thanks for sharing; I would like to see your updates regularly so keep blogging.
    Website Monitoring Tools

    ReplyDelete
  7. Unknown9 November 2017 at 04:03

    The future of software testing is on positive note. It offers huge career prospects for talented professionals to be skilled software testers.
    Regards,
    Software testing institutes in chennai|Software testing training institutes|testing courses in chennai

    ReplyDelete
  8. Unknown18 April 2018 at 00:26

    Best Mobility ServicesVery good informative article. Thanks for sharing such nice article, keep on up dating such good articles.

    ReplyDelete
  9. Deepika9 May 2018 at 23:59

    VERY INFORMATIVE BLOG. KEEP SHARING SUCH A GOOD ARTICLES.

    Best Software company in USA | Austere Technologies

    ReplyDelete
  10. Anonymous10 May 2018 at 05:09

    Very good work. It is very interesting to learn from to easy understood. Thank you for

    giving information.

    automation testing courses online

    ReplyDelete
  11. Deepika10 May 2018 at 22:04

    Very good informative article. Thanks for sharing such nice article, keep on up dating such good articles.

    Best Software Security Services | Austere Technologies

    ReplyDelete
  12. Deepika10 May 2018 at 23:21

    Nice blog with excellent information. Thank you, keep sharing.

    Application Quality Management Services | Austere Technologies

    ReplyDelete
  13. Anonymous17 May 2018 at 22:11

    Needed to compose one little word yet thanks for the suggestions that you are contributed here...
    Best Online Software Training Institute | Testing Tools Training

    ReplyDelete
  14. Deepika17 July 2018 at 04:30

    Wow...What an excellent informative blog, really helpful. Thank you.

    Best Degree Colleges Hyderabad | Avinash College of Commerce

    ReplyDelete
  15. sandy30 August 2018 at 06:09

    Thank you for sharing this valuable information. But get out this busy life and find some peace with a beautiful trip. book Andaman holiday packages

    ReplyDelete
  16. Deepika21 September 2018 at 02:34

    Great informative blog, keep for sharing.

    Best Blockchain services | Massil Technologies

    ReplyDelete
  17. Deepika25 September 2018 at 22:13

    Excellent informative blog, keep for sharing.

    Best System Integration services | Massil Technologies

    ReplyDelete

Post a Comment

Popular posts from this blog

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

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