Contact Me Your next step – Contact Me

Contact Me

Contact me for freelance App Testing and Website Testing services

I'm a freelance software tester.
Contact Me

Client Testimonial from Composed

We hired Pat to help with QA of a music streaming app. We needed someone with that magic “6th sense” of where the bugs are lurking; the ones which developers tend to miss. Pat more than fulfilled this need, with highly methodical approach and a great eye for detail.
Andrew Ebling, Head of App Development, Composed

Client Testimonial from Storythings

We’ve worked with Pat Walsh on a number of very different projects, from interactive video projects to mobile apps. His work is very thorough and has quickly become an essential and important phase of all the production work we do at Storythings. He’s thorough, diligent, and a pleasure to work with.
Matt Locke, Director, Storythings

Client Testimonial from Drum

Pat has been absolutely incredible at testing each of our projects he works on. He’s very professional, organised and diligent. I look forward to using him again in the future.
Oliver Thurtle, Director of Technology, Drum

Types of testing I perform include

  • iOS App Testing
  • Android App Testing
  • Website Testing
  • AI Chatbot Testing
  • Sonos App Testing
  • Rapid Software Testing
  • Exploratory Testing
  • Functional Testing
  • End-to-End Testing
  • CMS Testing (Drupal, WordPress)
  • Web App Testing
  • Ecommerce & Mobile Commerce Testing
  • Cross-Browser Testing
  • Social Media Testing
  • Mobile Device Testing
  • Field Testing
  • Usability, UX, UI, SEO
  • Testing tools: Charles Proxy (bandwidth throttling), Postman (API testing)
  • Advanced technologies: Voice Control (Alexa), NFC, GPS, IoT, AR (Augmented Reality)
  • Game/Development engines: Unity apps
  • Other devices: Apple TV (tvOS), Amazon Echo Dot (Alexa), Sonos

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
  • EdTech, Law
  • Museums, Social Culture

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

In some cases, a client will know exactly what they want from a test project and this will help to define the project from the start. On the other hand, a client may come to me and say ‘test my website’ or ‘test my app’, in which case, further information is required to find out the required scope of the testing project.

In order to define the testing/QA project, we can discuss requirements via email, phone call, Skype call, Slack chat, MS Teams etc.

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 this can be discussed and arranged as appropriate.

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.

Testing Stages

Some of the clients I’ve worked with

Featured Posts From The Blog

  • iOS18

iOS 18 and macOS Sequoia

At Apple's WWDC 2024, Apple announced iOS 18 and macOS 15 Sequoia. iOS 18 Apple Intelligence is the main feature of iOS 18 even though it doesn't appear until iOS 18.1 is released, likely [...]

  • testing-ai-chatbots

Testing the AI Chatbots

With a range of AI Chatbots to choose from now, I decided to do my own test of them, to get an idea of the differences between them, also to test their accuracy and [...]

  • The-QA-Chatbot-in-usage

Added The QA Chatbot to the site

I recently added The QA Chatbot to the site, to try it out. It seems to work very well, with a couple of quirks such as repeating answers - but nothing's perfect! The chatbot is [...]