Inscription
I have been working for more than six years, from the background to the mobile terminal, from development to the project leader, everything is done with a learning mindset. Along the way, I dare not say what I have achieved, but I have done my due diligence and walked step by step. "The deceased is like a man", if it is possible to record this running account of life, it is a blessing. It is also said that "no small stream can become a river", so from today, let's accumulate bit by bit!
background
In early September 2017, after finishing the H project, the leader was arranged to fire the Z project. At that time, the customer was extremely dissatisfied with the progress made in the unit testing that had been carried out for two months. Colleagues in charge of this work are also busy, and suffering:
- There are many project modules , and unit testing has not been adopted since the beginning
- The project adopts plug-in development, and there are technical bottlenecks that need to be tackled
- The main focus of the development brothers is on the technology and the business is ignored
- After failing to achieve the intended goal many times, the customer loses patience
- Mutual distrust continues to accumulate
solution
After deeply understanding the current situation and clarifying our existing capability structure, I formulated the following solutions, and communicated frankly with customers, gaining customers' understanding and recognition of the solution:
- Reduce technical pre-research work priorities clear in the existing structure ability, we can do, not 1 what to do
- Choose typical, high-value business scenarios, sort out business processes, test ideas and implementation logic
- Unit test coverage of these business scenarios and make a case
- Record summaries of lessons learned to form a guidebook
- Share to all development brothers
- In subsequent iterations, the unit test is included as a basic requirement and included in the version implementation plan 2 , which can be a new business or a supplement to the original business
milestone
- On September 12, 2017, the implementation plan was approved
- On September 25, 2017, the plan was approved
- On October 18, 2017, the case and instruction manual passed the review
- On October 23, 2017, all the development brothers were shared
Note
In fact, whether it can or not is not absolute. It is necessary to comprehensively consider the complexity of the implementation, the cost spent, and other factors. The "no" part here can actually be easily achieved through automated testing of the UI. ↩︎
There are at least three tasks to follow up in the follow-up: access to continuous integration, code review, and performance calculation. ↩︎
