At MVG Media we have always been committed to delivering high quality solutions to our client however, recently we have taken things up a notch. Our developers are extremely busy people, often under a reasonable amount of pressure to code perfect solutions and often to a strict timeframe.

It’s for this reason that we’ve taken most of the testing away from the developers and now placed in with a dedicated in-house testing resource. Pooja has joined the team in May 2017 and in responsible for quality checking every solution that leaves the studio. Initially she will create a testing strategy for each project then deliver on this by working closely with the developers, project manager and the client. We see this as a very positive step in the evolution of the company. We’re confident that Pooja’s input will speed up the development cycle, provide better quality solutions and provide peace of mind to both our internal team and the end client.

So how do we provide quality assurance and what’s the testing process?

The tasks involved are broken down into 4 main categories:-

  • Testing Strategy
  • Functional Testing
  • Usability Testing
  • Compatibility and Regression Testing
  • Performance Testing
  • Stress Testing
  • Security / Penetration Test

Testing Strategy

A document produced during the scoping phase of the project. This strategy document will be the result of conversations with the client around what’s expected of the solution. For example: Does this solution need to work in IE9? Does it need to run on old operating systems such as Windows XP? How sensitive is the information gathered on the website – should we schedule a penetration test? Etc.

The strategy document will inform the client of what we intend to do to ensure their solution reaches their audience. If we have worked on this web project before then we often draw upon their analytics to inform us of what the most popular devices and browsers are for that specific website.

Functionality Testing

Ensure that your website works first time, every time. In-depth testing will identify even the issues that can’t be found using automated testing.

How we approach this:
Set-up the Test Environment
User acceptance testing scripts


Usability testing

This is a way to see how easy to use something is by testing it with real users. Users are asked to complete tasks, typically while they are being observed by a researcher, to see where they encounter problems and experience confusion.

How we approach this:
We currently perform this predominantly in the design phase but can be performed at any point through the design and build process. We mainly use ( which allows us to select the sites demographics, set-up testing scripts and invite in real-world people to use the website (by following the script). The testers send back a video of their screen, with them actually using the website and commenting on any areas that they are struggling with. This give us the opportunity to correct these and re-test until we get the perfect result.


Compatibility and regression testing

Compatibility of your website includes the following aspects:-

  • Browser compatibility
  • Mobile / device compatibility
  • Operating system compatibility

web icons

How we approach this:
We currently approach this in two ways:-
BrowserStack –
Test on an exhaustive range of browsers, right from legacy versions of Internet Explorer, to the latest beta and developer releases of Edge, Safari, Chrome, Firefox, Opera, and Yandex.
Any browser on any platform (Android, iOS, Windows Phone, Windows, Mac).
Real browsers installed on real devices, so testing on them is just as good as testing on a browser installed on your local machine. Your test results will always be accurate, as they would be on a freshly-installed, local browser.

Real world tests
We own a range of popular mobile, tablet and desktop devices and manually test the user experience across all of those.

Performance testing

Web applications should be fast. Web performance / speed testing is very important. You need to consider that sometimes people are on mobile phones with slower connections.

How we approach this:
We adopt Google PageSpeed Insights to check page loading times:-

page speed

We also run speed tests through gtmetric. Speed reports are also available through Google Analytics.

Security testing

This is to ensure that the website remains stable and is not hacked or even worse brought offline. The website need to be robust and be able to sustain malicious attempts to compromise the solution. We also need to make sure that data and information is securely stored.

How we approach this:
We make a point of recommending that the client undertakes an independent penetration test with a company such as ProCheckup –