There are three distinct strands of testing at Pugpig: Product, Project and Pre-submission. These are carried out by our in-house QA department, with assistance from the development, support and product teams.
Our product testing occurs throughout the development cycle, with all features, changes and fixes being specifically tested, as well as a broad strokes pass of the entire platform before that version is signed off. There is always one signed-off version of each platform, rather than multiple. Additionally, we conduct a couple of extra test passes throughout the year. Firstly we conduct a full regression pass against the beta versions of iOS and Android before they’re released (more on this is outlined in this article), and then several months later conduct another full regression pass before we start targeting those versions. Testing takes across a number of devices and the full range of supported operating systems and browsers. Additionally, our QA team might conduct ad-hoc testing to replicate issues raised by customers or their users as well as those flagged by internal stakeholders.
Project testing is more tailored to the specifics of the customer and the work done, as this should already be being conducted atop an already signed-off version of the product(s). We’ll generally conduct this in the mid-to-late stages before launch, when the project is in a largely representative state. This testing will be repeated later in the project if necessary, as well as some final pre-launch checks.
Then, before any app is submitted or site pushed live we have a standard set of tests to be completed by the Support Engineer responsible, this covers core functionality such as purchasing, push notifications and the general structure of the app.