Types of testing I perform include

  • iOS App Testing
  • Android App Testing
  • Sonos App Testing
  • Website Testing
  • Rapid Software Testing
  • Exploratory Testing
  • Functional Testing
  • End-to-End Testing
  • CMS Testing
  • Web App Testing
  • Ecommerce & Mobile Commerce Testing
  • Cross-Browser Testing
  • Social Media Testing
  • Mobile Device Testing
  • Field Testing
  • Usability, UX, UI, SEO
  • Special technologies: NFC, GPS, IoT, AR (Augmented Reality)

Sectors I have tested Apps & Websites in include

  • Retail, Shopping, Shopping Rewards, Online Store
  • Banking, Financial, NFC Payments
  • Fashion, Fitness, Lifestyle, Health, Hair & Beauty Products
  • Email, Productivity, Infographics, System Utilities
  • Navigation, GPS, Location Based Services (LBS)
  • Casino, Betting, Roulette, Betting Exchange, Games, Gaming Platforms
  • Movie Streaming, TV, Video, Music Streaming
  • Events, Travel, Ticketing, Photo Postcards
  • Cinemas, cinema ticket booking
  • Insurance, Insurance Quotes
  • Pharmaceuticals, Energy, Engineering, Medical (Locums)
  • Diner, Restaurant, Drinks Supplies, Soft Drinks
  • Cars, Vehicle Financing, Transport Information
  • Education, Language Learning, Mind Mapping
  • B2B Services, Field Service
  • Golf, Newspapers, Web Comics, Online Storytelling
  • Property – PropTech, Property Investment Platform, Property Auctions

How an Independent Testing/QA  Project works How an Independent Testing/QA Project works

The first step is to define and discuss what is required from the Independent Testing/QA Project. This can be via email, phone call, Skype etc or, for a longer-term project in the London area, an onsite meeting.

The aim here is to agree what the testing should focus on and on what browsers and/or devices the testing should be carried out on.

Other factors to consider are, for app testing projects, app delivery method, or, for website testing projects, test site details and access, plus where issues are to be raised and how test results are reported.

Also, scheduling the testing date(s) is key and you can view my Bookings Calendar to check availability.

At this stage, the App or Website is tested, according to the Project definitions and the browser/device list agreed on. This will include all the testing types agreed on, plus the appropriate amount of Exploratory Testing to unearth bugs which may otherwise be left lurking.

Issues are raised as they are found, in the method agreed: this could be in your own issue tracker – such as JIRA, DoneDone, RedMine etc – or within an Excel document, or perhaps a Google doc, or, where applicable, within my own hosted JIRA issue tracker.

Test results can be reported in many ways and the method used will often depend on the length of the test project. For example, a short half-day test could be reported on in an email that summarises all the results, whereas a longer test could be reported on in a full Test Summary Report.

A Test Summary Report includes sections such as Overview, Main Findings, Gap Analysis, Deliverables, Testing Types Performed, Test Devices, Bugs Statistics and Summary of Main Bugs.

At this stage, we can discuss if any further testing is required.

This may include further focussed testing, retesting of fixed issues, regression testing after changes or any other type of testing.

Contact Me Your next step – Contact Me

Contact Me

Contact me for Independent Testing/QA Services

I'm a freelance App and Website Tester based in the London area.
Contact Me

Testing Stages

During the Development Stage, I can work with the Developers, Designers and Project Managers to effectively design and execute tests at the most cost-effective time.

    * Working with Developers, Designers, Project Managers.
    * Testing can be focussed on the most important functionality or can be generalised, to cover all areas.
    * Testing can be added in phases, as new functionality is developed and available for testing e.g. on a sprint/iteration/release basis.
    * Most cost-effective time for testing.
During the Beta Stage, bugs can be found which otherwise would have been released to the public.

    * Find Bugs before release to the public.
    * All functionality can be tested at this stage, and emphasis can be given to certain functionality depending on priorities.
    * Still a cost-effective time for testing.
At the Release Stage, testing can be done at and around the go-live stage, to try and find any last-minute issues, and also when new features are added, or when the app/website is updated to take into account new technology, new features etc.

    * Testing at and around the go-live stage, to find any last-minute issues
    * Testing new Features and Functionality
    * Finding Bugs in updated apps/websites

Some of the clients I’ve worked with

Featured Posts From The Blog

  • Charles-Proxy-screenshot

Using Charles Proxy for bandwidth throttling testing

Many apps and websites now consume lots of data, especially in sectors such as video streaming and audio streaming. Also most apps performing a useful function of some kind are interacting with the server backend [...]

  • Automation-Guild

Automation Guild Online Conference 2017

As a tester still learning about the whole area of automation, I've been checking out some of the video sessions from the Automation Guild Online Conference 2017. These include both pre-recorded information/training/product sessions from automation/product [...]

  • wordpress-developer-course-img

iThemes WordPress Developer Course

In December 2016, I completed the online training course iThemes WordPress Developer Course. This course was over two days and took the form of online live webinars, looking at what a WordPress site consists of [...]

  • mdqcc

Mobile Device Quick Comparison Chart

Update - November 2016 - I've now added the Google Pixel XL & Pixel and removed the recalled Samsung Galaxy Note 7 Update - September 2016 - I've now added the iPhone 7, iPhone 7 [...]