Skip to main content

Differences between testing services and websites?

I recently got asked by a fellow QA, what is the difference between testing a web service and testing a website is? So here is the answer in as simple a way as I can put it...

Firstly, what is a web service?

It's effectively a function that can be accessed by by other programs over the web. For instance, the asos website has a "basket" web service that enables users to add to their basket on the product page.

I understand that from coming from somewhere that only tests a website to somewhere that requires QA to test against web services it can be very daunting, but with the right tools and the right mindset it can be simpler to test a web service than a website.

Why is that? you may ask... Let me begin.

One of the problems with testing User Interfaces or websites is that there are so many things that could potentially go wrong, you're interacting with the end product. Look at it like switching on Christmas tree lights in the old days, when if one light was broke then it's a pain to fix and a pain to find out what light is broke as they're all switched off! However, by turning on individual lights you can be sure of what ones will work and what ones won't as you're certain of what to expect.

It's kind of similar to when testing a web service or even an API, you know what to expect in the response from the API/Web Service as it forms part of a contract so you can code tests around that, or write tests around that. However with a website, when coding tests there are many things that can cause the web page to break, things like browser type, or JavaScript errors can all cause tests to fail. I find testing a web service to be a lot more robust, providing of course, that tests are written in a smart way.

The other good thing about testing web services is that they are generally very quick to test, and you will get feedback very quickly from what you are testing. It can take a lot longer to test against a UI, due to the layers beneath the UI all requiring to do some work of some kind.


Labels:

Comments

  1. YuraHryk25 January 2019 at 06:07

    This comment has been removed by the author.

    ReplyDelete
  2. YuraHryk25 January 2019 at 06:09

    If you are new, I advise you to consult professionals who will make you a site or allow you to choose a template for your site in the category admin panel. The best website with any templates you need

    ReplyDelete

Post a Comment

Popular posts from this blog

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....
1 comment
Read more

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

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