Problems with the app version iteration in the eyes of testers

Problems with the app version iteration process in the eyes of testers

--Remember the development test process for a new version of the app

1. Preface

Since the beginning of August into the current company, in this version of the iteration process, the first independent of the app part of the entire test design and demand tracking, from start to finish tracking requirements analysis to development test on the whole process, and has done a variety of test types compared to it is not as good as imagined, It's not as bad as you think. The old saying goes, the pear is not delicious, the taste of their own to know.

After the entire iteration, feeling a lot. Comb the whole process here and analyze the entire iterative process in the perspective of testing as a reference for future work.

2. Introduction

2.1 Project and Company profile

The company belongs to the traditional pharmacy industry to the mobile Internet medical Industry transformation, in the mobile internet aspect belongs to the start-up stage. The current iteration project is an updated version of the forecast, mainly to complete some functional optimization of the app.

2.2 Team Structure

There are PMO, product Design Center, technology Research and Development Center three first-level departments, the role of the project and personnel assigned to

Pmo-Project Manager (1 people)

Product Design Center-product Manager *2/ui/ue (4 people)

Technology Research Center-front End (Android (6 people)/ios (6 people))/h5 (4 people)/back end (6 people)/backstage (2 people)/OPS (2 people)/test (6 people), total 32 people

Note: In addition to the app, there are three sides (different user roles), but not within the scope of the author's responsibility, and are not described in this document.

2.3 Iteration Cycle

Demand analysis and Design: 11.23-11.26

Development: 11.30-12.7

Test: 12.8-12.15

Online: 12.16 hrs

3. Problems in the iterative process

3.1 Always in need of change

First time Change-11.25

Prior to the beginning of this iteration, there were two separate requirements which were relatively independent and of high importance.

There is always but, however, these two requirements have been cut off as soon as they have completed the requirements and prototypes and are immediately entered into the development design, as the company's business and other leaders have assessed that it is not appropriate to complete the project at this time. After this part is cut, the product manager re-adjusts the requirement content according to the project situation, and once again carries on the technical review and the scheduling of the whole project scope (project manager, product, development test). In the process of technical review, minor changes have been made. The formal demand range was completed in 11.26 and entered the formal development process.

Second time change-12.2

The first edition of the test case is completed. In the Xmind format for use case review, in the review process again found that there is no clear part, after discussion, came to some conclusions (the reason is partly because the subsequent findings of the conclusion is actually a draft, followed by several refinements). In addition, the review also found some unclear needs, product development testing three-party opinions inconsistent demand, all come to a conclusion.

Third Change-12.9 early

The first version of the test was released. During the initial round of testing, many uncertain parts were found, and the product Manager received a unified conclusion after multiple communication, and in 12.9 the requirement was updated.

Fourth change-12.10 nights

Test has been carried out to the third day, the end of a requirement change needs to be on the app side of the corresponding, before the consideration is completely unaffected, but the background interface has been changed, the actual impact on the app side. After comprehensive consideration, the corresponding demand is re-given, this part change is not small, the pressure is bigger later.

Fifth change-12.15 pre-launch

The night before the launch, the test has been completed, delivery of product acceptance. During the acceptance process, the product and UI also put forward a few interface display problems, the development of temporary changes in the evening after the normal online.

3.2 Bumpy development

　　　　Ios

Development team leader in the Test team before submitting a special meal, to ensure that the actual defect in this version of no more than 20, must be to reduce the pressure on the Test team. Before actually submitting the test, the developer is also launched to follow the test case. In the actual testing process, found 113 defects, 80% are found in the test case, 10% of the previous version of the defect, the remaining 10% of the test case design is not covered by the section.

A request was not submitted to the test on time, the developer did not travel to Guangzhou, has been with the author through the telephone to communicate the implementation details of the requirements, after 2 days to submit the test, still found a large number of defects.

iOS in the current iteration of the discovery of 6 flash defects, some very obvious, into the function of the flash back, some need 17 steps to find, there are special conditions of reproduction, need special circumstances to be able.

Android

The Android leader has another special item in the iteration that needs to be tracked separately. At the same time he assigned himself a task of the current project, but has not started to carry out, until 12.13 overtime to complete, 12.14 submitted to test, fortunately, this part did not find serious problems.

However, the new version of Androbao after the user update, the key operation caused the app to Flash, the reason is that the current period of the Android group of the underlying DB layer refactoring, SQLite table in a field has changed, when viewing historical data caused app Flash.

3.3 Testing ahead in communication

Throughout the iteration of the release, the test progresses through continuous communication: and the Product manager confirms the requirements details, and the UI confirms the implementation details, and the development confirmation when to submit the test \ When to solve the problem \ What is the specific requirements of the details of this part of the demand is not how to reproduce the defect The test on Android and iOS confirms the consistency of the implementation. Wait, wait.

Throughout the release process, test cases have undergone multiple updates, depending on the change in requirements.

During the test case review, a large omission of the interaction design was found.

The download installation of the upgrade test and the Cache data Validation section have missed the test, resulting in a flash-back issue on Android's online presence.

4. PostScript

Think originally, Lao Tzu's team just opened, fly more than 10 people seven or eight gun--Beijing opera "Sha Jia Bang" excerpt

The new project team was founded in June, and the team members came from a variety of companies. Just set up the team always have a variety of problems: the professional level of the practitioners of uneven, team personnel to further improve the degree of coordination, due to project tension, the overall communication management, the development of the project management process does not have a unified definition. All kinds of questions you can think of will exist, but this is not the hardest to solve, the hardest part is whether the team has the motivation and determination to solve the problem. This is the only reassuring place where our product, design, development, testing, transportation and our project managers are working hard to achieve the project goals, and each iteration of the project will discuss the existing problems and further analysis, follow-up improvements.

According to the actual situation of the current project, the next iteration will be reconstructed and the interface of the revision, the new version will be in a brand new appearance in front of the user, I hope we can succeed.

　　

Problems with the app version iteration in the eyes of testers