Our initial efforts, prior to forming testmunk, were in the app development sphere, much like our clients. In developing our own consumer apps (Tipgain and HiMom), we had the same growing pains, and found our testing process to be initially very chaotic. Our lab consisted of a few devices shared between us, and our release process was very simplistic; if we felt a release was ready, we would each poke around on our pool of devices to determine if key functionality worked as expected or if we experienced bugs or crashes. If you are a small startup with only a couple of people, you know what I am talking about. However, as time goes on, the features start growing, the app becomes more complex, and of course, things soon began to be missed during testing. Of course, surprise surprise, our users began to find the bugs that slipped through our QA process, forcing us to adapt, and to realize we needed a more formal process. In these initial efforts to improve our process, we devised a spreadsheet to help track our process. In this spreadsheet, we listed all the test cases we could think of (for our particular apps) and arranged them to be run through from a functional testing point of view.
This led us to some surprising realizations…even a small, early stage startup can have easily between 30-50 test cases. Later on, when our client base grew, we would find that the larger the startup or company, the larger a testplan had to be. With several clients, we have seen testplans with several hundred or even thousands of testcases.
Test Case Template
If creating your testing process from scratch, the first step is to establish some sort of formal list of all possible (or at least the most probable) scenarios. This will help to bring some order to the chaos of the typical testing process for early startups. At Testmunk, helping companies to set up an initial test plan focussing on listing test cases is often our first order of business, and can be one of the key benefits of our process. This typically starts by simply walking through the app with our client and helping to create their plan. In most cases, the first tool on hand is the same tool we used in our first formalized test plans – google spreadsheets. There are of course more formal testcase management solutions out there, including some free versions we previously wrote about.
As we routinely create such test case templates for our clients, we thought we would share this test case template with our readers in order to help raise your startup to the next level (should you need it). We commonly use a similar template when clients ask us to help them getting started in streamlining their QA testing process. Feel free to copy it and then modify it to your own means.
|About the author:
Martin Poschenrieder has been working in the mobile industry for most of the past decade. He began his career as an intern for one of the few German handset manufacturers, years before Android and iPhone were launched. After involvement with several app projects, he soon realized that one of the biggest pain-points in development was mobile app testing. In order to ease this pain, he started Testmunk. Testmunk is based in Silicon Valley, and provides automated app testing over the cloud.
Follow Martin on twitter