Your next step – 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.
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.
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.
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
- Testing tools: Charles Proxy (bandwidth throttling), Postman (API testing)
- Special technologies: NFC, GPS, IoT, AR (Augmented Reality)
- Other devices: Apple TV, 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
How an Independent Testing/QA Project works
In order to define the testing/QA project, we can discuss requirements via email, phone call, Skype call, Slack chat, 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.
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.
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.
This may include further focussed testing, retesting of fixed issues, regression testing after changes or any other type of testing.
Some of the Testing Projects I’ve worked on
- Universal Music – Composed music streaming service – App & Web Testing Pat Walsh 2017-05-15T13:05:01+00:00
- American Interior – iOS App Testing & Android App Testing Pat Walsh 2017-04-20T12:59:58+00:00
- * 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.
- * 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.
- * 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