Before the product functions are launched, the final link is generally to write product test cases by test students, and deploy them online after passing the test.
However, due to the limited manpower of testing students, it is difficult to fully simulate the user's usage scenarios, device types and network conditions, and some omissions are inevitable. Therefore, a small-scale user internal testing link is added before the product is launched, which is helpful for improving the product after the launch. Quality and reducing the risk of bugs will help.
So, how to organize a user internal testing event, what are the points that need to be paid attention to? Through this review document, we sort out these problems from 0.
01 Review goals
Looking back at the previous internal user testing activities, the goals can be divided into the following three types:
1) Expose untested bugs
If the product involves a relatively large update, such as launching a new function or changing a wide range of program code, then you need to focus on the number and type of bugs that occurred during the testing process, and pay attention to whether there are any problems that affect the user's use. And the frequency of occurrence; and then judge the priority according to the type and quantity of the problem, and contact the industry and research students to fix the problem to ensure the quality of the final launch.
2) Predict the possible risks after the product is launched
Through the internal testing activities, we need to simulate more close-to-real usage scenarios to discover hidden problems. We can also get a part of the user usage data of this function by burying the data of the internal testing installation package, from product development. From the point of view, to predict the possible risks after the product is launched, so as to avoid it, make a response plan, and improve the stability of the product.
3) Collect user feedback
Internal testing activities are a good opportunity for products to communicate with users. We can take this opportunity to collect users' suggestions or comments on products and functions. Of course, it is not necessarily limited to each key test function. Users can collect all opinions about the product as a whole. , as a reference for subsequent product iterations.
02 Review the process
After determining the goal of an internal testing activity, what points should be paid attention to in the activity process? I will sort it out from the following 5 aspects.
Take the events that I have organized before, because the type of product is K12 student users, mainly focusing on elementary school grades.
If students in primary school grades are directly recruited as test users, firstly, it will affect the students' learning progress, and if there are serious product quality problems, it will be detrimental to the shaping of the product image; therefore, we will recruit the attributes of the population at the primary school age. Duan's mother group.
How to find such people?
We have targeted some regular part-time groups and part-time forums, and recruited users into the group by publishing task information to facilitate follow-up task guidance; in this link, we also found that people who often participate in part-time activities will have their own part-time circles , By leveraging these users, our recruitment progress can have a fission effect.
When recruiting and managing personnel, we chose the method of QQ group. Because QQ group provides relatively complete group management and group file support, it can reduce our manpower in the process.
If the product is non-K12, you can also recruit users who intend to participate in the internal test through the pop-up reminder in the official version of the app, guide these users to actively download the test version of the app, and cooperate with feedback activities to guide everyone to fully test and expose problems; However, this method will have certain restrictions on product types and user attributes, and requires the support of product development students. You can choose according to the actual situation.
2) Activity costs
In order to motivate the users to participate in the activities more fully, we can set a certain number of incentives such as prizes and bonuses. If it is a product with strong social attributes, we can also issue virtual items such as medals and titles in the station.
The premise of choosing the incentive method is to ensure that most users will like it, so as to stimulate the motivation of users to feedback; if the country email list final activity reward is not painful to users, the effect of the activity may be greatly reduced.
Since most of the active users we recruited come from external part-time forums, we adopted the most direct method - bonuses, as an incentive method; The users who participated in the activity have been added to the QQ group, so we can save our manpower in issuing bonuses through the form of group red envelopes.
Through the number of people in each internal testing activity, we can estimate the cost of the activity, so as to report to the Leader or the cooperative business department; in addition, because the group red envelopes cannot be issued, the invoices cannot be obtained, so we need to come with finance and taxation classmates in advance. Determine the compliance of the process.