Click a button to subscribe to “Yunjian Da Jia” column, access to the official recommended boutique content, learn technology not lost!

  • The function realized by the product is the embodiment of the product value. Functional implementation is the foundation. Functionality is not implemented, and it doesn’t matter how well you do anything else. So how do you ensure that the functionality you implement covers the requirements?

The function realized by the product is the embodiment of the product value. Functional implementation is the foundation. Functionality is not implemented, and it doesn’t matter how well you do anything else.

The main contents of this paper are as follows:

  1. How to do it: Implemented functionality covers requirements.
  2. What’s wrong with just implementing the functionality.

How to do this: Implement functionality that covers requirements

Achieving functional coverage requirements requires a concerted effort from different roles on the team. As shown below:

Developers test themselves

Developer self-test: after developers develop, they test whether all functions can be implemented. If the product manager has acceptance criteria, run against them. For the front end, the main content of self-test is: function, UI interaction and browser compatibility.

Developing self-testing is important. On the one hand, programmers test themselves and find problems earlier. The sooner you find a problem, the cheaper it will be to fix it. On the other hand, developer self-test is responsible for their own code quality, but also the embodiment of professional quality. Submitting tests without self-testing wastes QA’s time.

It is recommended to incorporate self-testing into workflow tools. If you use CODING, you can configure the task flow rule: When the status is transferred to the test, be sure to fill in the self-test content:

QA testing

QA tests functionality thoroughly: not only normal process functionality, but also abnormal processes, outliers, boundary values, etc. Therefore, QA testing is an important part of checking functionality implementation.

Professional QA will design test cases. Test case complete coverage requirements. Passing QA tests means passing all test cases.

Of course, THERE are limitations to QA testing: if a defect introduced during development is not within the scope of the current test functionality, QA will most likely not find it. To alleviate this limitation, there are two suggestions:

  1. Development informs QA of other features that may be affected when submitting tests.
  2. No matter what function QA tests, after the test is complete, the core test cases for all modules of the product are run again.

Product Manager acceptance

The product manager accepts functionality. Product managers are more sensitive to features and are more likely to find missing or incorrectly implemented features.

Designer acceptance

Designers embrace the UI and interaction. Designers have a “pixel eye” : they can spot UI problems that other people can’t.

What’s wrong with just implementing functionality

For short term projects, just the work is fine. But in reality, many are long-term maintenance projects. Over time, many features will be added and many features will be changed. Projects get bigger and more complex. Just implement it, regardless of the maintainability of the code. Will accelerate the occurrence of the following problems:

  1. It’s getting harder and harder to add new features and fix bugs. And it’s taking longer and longer.
  2. Fixed this bug, other bugs appear.

Therefore, for long-term projects, we should not only implement features, but also focus on the maintainability of the code. I’ll cover this in more detail in the following article.

Talk about code quality – “Learn to learn, copy to go to improve the quality of front-end code” introduction

“Cloud recommendation” is Tencent cloud plus community high-quality content column. Yunjianguan specially invites the top performers in the industry, focusing on the landing of cutting-edge technology and theoretical practice, to continue to interpret hot technologies in the cloud era and explore new opportunities for industry development. Click one button to subscribe and we will send you regular high-quality content.