Development Check Test Reference Documentation

foreword

[1] Compared with being an excellent programmer, I prefer to be a valuable and reliable employee. In enterprise work, we not only need to fulfill our daily needs well, but also need to ensure the quality of our code and reduce the occurrence of problems. We must be reliable and responsible employees.

[2] Carrying out detailed and comprehensive self-testing of the written modules is a manifestation of our responsibility for our work.

[3] In my daily business development, I have discovered and accumulated many common problems during development. After continuous summarization and precipitation, I finally summarized the following reference documents. I believe that most developers have more or less encountered similar problems in their daily development work.

[4] The key to growth lies in summarization and reflection. In order to avoid the same problems from happening repeatedly, avoid unnecessary pitfalls, improve work efficiency, and reduce the occurrence of common bugs. Here I have abstracted, organized, and classified the common development attention and self-test check items in daily WEB development, hoping to help developers reduce these error-prone and common development problems.

【5】Everyone gathers firewood and the flames are high. The following is just a summary of my personal experience. It is not comprehensive enough and has many shortcomings. I also hope that more development comrades will work together to improve this document: https://github.com/zwzhangyu/dev-test-doc

 

interface class check

The interface inspection mainly checks whether the layout and style of the system interface (such as windows, menus, and dialog boxes) meet the requirements, whether the text expression is concise and accurate, whether the page is beautiful, and whether the operation is friendly, etc.

Miscellaneous

1. After the development is completed, whether the system module page style, component layout, font size, component text name, etc. are consistent with the requirements document.
2. After the development is completed, whether the prompt information of each operation of the system module is consistent with the requirement document.
3. The text in the interface is concise and easy to understand, without typos.
4. When adjusting the size of the page text box and dynamically dragging to adjust the size, can it be adaptive to other elements on the page.
5. The function module name of each component needs to maintain a consistent style and name throughout the system. (See Appendix T0010 for details).
6. The layout of components in the page in the system maintains a unified order and position arrangement (see Appendix T0001 for details).
7. Pay attention to the alignment and aesthetics of the form controls.
8. The icon selection of the management background menu needs to be close to the business semantics, and cannot be chosen arbitrarily.
9. The text component pays attention to the text overflow and line break (see Appendix T0004 for details).
10. Manually adjust the page resolution, enlarge or reduce the page appropriately, and check the page display after the change, whether there is any cover, loss, or layout disorder, including data display pages, form pages, etc.
11. If there is no requirement, all prompt information will be described in Chinese. If the dependent third-party tools have English descriptions, translation conversion is required.
12. Whether the picture involves copyright, privacy, patent and other issues.

Chart class

1. Check the display status of the chart when the interface data is empty; the display status when part of the data is empty.
2. The proportion chart may show that the sum of the data of each category is less than 100% (see Appendix T0011 for details)
3. The layout of charts should be kept neat and tidy. Check items include: charts of the same type have the same size and alignment.

function check

Functional inspection is to verify each function of the product. According to the functional test cases, test one by one to check whether the product meets the functions required by the user.

comprehensive

1. Link check, to test whether all the links contained in the current module are normal.
2. Return operation, when multiple tab pages are opened, click one of the tabs to return whether it can return normally.
3. Check the header at the top of the page, this part is often overlooked.

file class

file export

1. The quantity of data exported must be consistent with the quantity of the list query; whether the exported quantity includes the header; if there is no specific requirement, the export result field needs to be consistent with the list query result field.
2. Is there a limit to the number of exported Excel? The processing strategy for exporting Excel exceeds 65535.
3. The suffix exported by Excel needs to pay attention to xls and xlsx. Some files with the suffix of xlsx cannot be opened in Office.
4. If the exported fields are non-mandatory or combined fields, the exported string may be displayed as null, pay attention to check.
5. Whether there is sensitive information in the exported file, and whether security policy processing is required.
6. When exporting Excel, determine whether there is a naming requirement for a single sheet name. If there are multiple sheets, it is recommended to set a custom name.
7. When exporting to Excel, it is necessary to check whether scientific notation appears in numeric type fields.

File Upload

1. Importing files needs to limit the file suffix and file size. Usually, the file suffix is ​​verified first and then the file size is checked.
2. Users can upload various file types processing policies at will.
3. In the single file upload scenario, the file processing strategy for repeated file uploads.
4. In the multi-file upload scenario, there are duplicate file handling strategies.
5. File size tests: too large, too small, fit, borderline, etc.
6. File checking: different file name lengths, file names containing special characters, uploading empty files, etc.
7. When selecting a file, test the multi-selection situation, if it is not supported, please disable the multi-selection function.
8. Upload a file in use.
9. Upload the file with the same name repeatedly to check whether the result meets the requirements.
10. For large files, check whether the upload is canceled during the upload process, whether it is successful, and whether a progress bar needs to be provided during the upload.
11. Check the quality of the uploaded files, especially images.
12. All file types that are allowed to be uploaded need to be tested, and all files that are not allowed to be uploaded also need to be tested. Similar to the image type, it is necessary to test image data with various suffixes.

Download Document

1. Document attachments need to be checked to see if they can be opened and displayed on WPS and Office.
2. Whether the downloaded content of file attachments is beautifully formatted, and whether the font meets the requirements of the required document.
3. Whether the name of the download attachment meets the requirement document requirements.
4. Whether the download attachment URL can be guessed, and other attachments can be easily guessed and downloaded through the URL.
5. Are there specific download directory requirements.
6. Whether the download URL can be requested to download when the user is not logged in or authorized.
7. Whether the downloaded file has Chinese garbled characters.

file data import

1. The file extension needs to be restricted for importing, for example, only "xls" or "xlsx" format files are allowed to be imported.
2. Background analysis Excel/Word and other error handling.
3. Data type check, the import data type does not match the problem, the requirement is a numerical type, but the import is similar to Chinese characters.
4. Excel data import quantity and size limit.
5. Do not close the local file after testing the imported file, and try to import again after modification after the import is complete to check whether there is a problem. When uploading a file, the error net::ERR_UPLOAD_FILE_CHANGED may occur when the modified content is uploaded again.
6. Data processing of non-mandatory items. When filling in values ​​for non-mandatory items, the validity needs to be verified according to the data situation.
7. All imported fields must verify the data length. Pay attention to the length limit of the imported Excel data. All imported fields need to limit the length, otherwise there will be problems when inserting into the database.
8. The processing strategy when there is duplicate data in the imported data; after the imported data is compared with the system, there is a duplicate data processing strategy.
9. Whether it is necessary to remove spaces, note that simply using trim or tools to remove spaces may not necessarily meet the requirements. For example, non-newline spaces, half-width spaces, full-width spaces, and so on. There are many types of spaces in the data imported into Excel, so pay attention to distinguishing and processing.
10. For transactional issues, choose transaction processing according to business conditions. All imported data is maintained in one transaction or an independent transaction. Whether a single data import failure affects the whole.

form class

Miscellaneous

1. Form fields need to be confirmed one by one whether they are mandatory, and confirm whether to display the required logo and verification error message according to the requirements.
2. Type/length check; determine the length calculation standard: Chinese characters, characters, etc.
3. Check for repeated submission issues; whether multiple pieces of data will be submitted by continuous rapid click operation components; whether there is any abnormality in various components in the continuous rapid click click form.
4. Check the long text form information; test whether the long text is submitted to the backend normally; check whether the corresponding field length of the database can store the long text.
5. Reasonably handle common sense form fields, such as ID card format verification, phone number verification, etc. (see attachment T0007 for details).
6. Data duplication check, whether the same data exists, whether there is the same data under a specific unique identifier, and whether submission is allowed.
7. Common sense business data verification processing needs to be as unified as possible (see Appendix T0002 for details).
8. For non-editable fields in the form, it is recommended to use a reasonable background color to distinguish them, and generally gray them out.
9. The data displayed by the form component to the user should not have custom codes, and should be replaced with Chinese descriptions as much as possible.

date time class

1. Check the date information; check the date time zone from the front end to the back end; check the date time zone from the back end to the database.
2. Check that the date format is consistent with the requirements document. Whether it needs to be accurate to the hour, minute and second.
3. When selecting a date within a range, you need to check common sense issues such as the end time cannot be less than the start time.
4. The date selection component, except for specific requirements, cannot select a date greater than today.
5. For date input in form input boxes, Excel date text import, and other ways to process dates, it is necessary to test non-date type text processing strategies.
6. It is recommended to judge the time information based on the back-end server, do not use the front-end time.
7. The date class component needs to be set as a read-only attribute, and the user is not allowed to input manually.

Numerical class

1. For the number type components in the form, it is necessary to determine whether to add unit attributes according to the business scenario, and keep the global unit uniform.
2. Numerical components need to check the maximum and minimum values, and at the same time check whether the maximum and minimum values ​​of the input data correspond to the back-end parameter transfer and storage is normal, and also need to check whether the back-end storage to the database is normal. The maximum and minimum values ​​refer to the int/float/long/double data type boundary values.
3. Value type components need to be determined according to specific scenarios: whether to allow manual input, whether to allow decimals, whether to allow negative numbers, the number of retained decimal points, the maximum and minimum values, whether there is a default value, whether to allow the beginning of 0, etc.
4. For floating-point types, the number of reserved digits and carry rules need to be determined according to specific scenarios. Do not default to rounding, and pay attention to specific scenarios.
5. Check whether scientific notation occurs when computing numeric types.

dropdown list component

1. Multi-level linkage, whether the linkage data is correct, and whether the linkage is normal after data switching.
2. When the parent component switches to empty data, whether the child component data is cleared.
3. When there are three or more levels of linkage, after the selection is completed, after arbitrarily switching a certain drop-down list, whether other associated components are processed normally.
4. When the drop-down list loads too much data, reasonable optimization is required (see Appendix T0012 for details).
5. Check whether the information in the drop-down list is correct, and whether there is duplication under multiple linkage operations, including duplication of the data itself and duplication caused by inconsistent asynchronous loading.

delete operation

1. For related operations such as deletion, operations that have a significant impact on data must provide reminder mechanisms: pop-up boxes, identity verification, etc., to prevent users from misoperations.
2. For related operations such as deletion, it is necessary to analyze the data impact surface in detail, and whether the data processing of direct impact or indirect impact is correct (see Appendix T0006 for details).
3. For related operations such as deletion, it is necessary to test and verify multiple times, and at least complete the duplicate deletion, and then add the process once.
4. If there is no special requirement, all deletion operations default tombstone deletion.

update operation

1. Check data writeback is correct field by field.
2. Test whether the data update is normal field by field.
3. If the form storage is uniquely judged, the current data needs to be excluded when editing and updating.

search display

1. Whether the search input box needs to limit the search length, if the input is too long, whether it will cause the Request header is too large exception. If it is not processed, it is necessary to check whether the abnormal information will expose sensitive information of the system.
2. All queries must have sorting conditions. If there is no requirement, the default update time/creation time is recommended.
3. Index checking when querying multiple tables.
4. If there are multiple accounts, you need to check the display of the data logged in by each account, and check whether the data retrieved by each permission account meets its permission requirements.
5. Check whether the queried data is duplicated, and check the key field information.
6. The sorting conditions need to be unique, and check whether there is a duplication of paged data caused by the same sorting data (see Appendix T0001 for details).
7. When searching, just enter a space or nothing, and click Search directly to determine whether to perform a search.
8. Determine the retrieval type of each query component: precise query, fuzzy query, word segmentation query, etc.
9. When there is a large amount of data in the database, whether the query processing time is reasonable, test the response time of small-scale conditional query and large-scale conditional query.
10. Check whether there is a default query condition (see Appendix T0009 for details).
11. Search in the text input box, if there is a space in the input content, whether to filter the space.
12. Query whether the processing of special characters in the input box will cause system exceptions.
13. When retrieving query data according to conditions, the query conditions need to be reflected in the data list (see Appendix T0013 for details).
14. Check in turn whether each search condition writes back the condition value normally after the query is executed, and whether the entered value will be cleared.
15. Verify that the data of each query condition can be kept displayed and will not be lost when the page is turned.
16. When retrieving data, pay attention to check the boundary value of the result data, whether the query condition is included, and whether the date type query contains the data in the selected date.

Bullet box class

1. Note that the length and width of the bullet box should be adapted to various types of screens as much as possible, and do not leave too much white space.
2. Try not to have a back button in the pop-up box, otherwise it will lead to infinite nested pages.

data write back

Data write-back is most common in form scenarios. In addition, it also accounts for a large part of the defect list. Therefore, this part of the scene is extracted and the development and test points related to data write-back are sorted out.

1. Check each form field writeback is correct in turn
2. Data integrity check, including the write-back of each field of the form when all fields are not empty, the write-back of each field of the form when some fields are empty, and the write-back of each field of the form when all fields are empty.
3. For dynamic forms, test the write-back of forms under various conditions in turn (see T0014 for details).
4. In the scenario of dynamic switching of components, it is necessary to check whether the change of the precondition will affect the subsequent components, whether the change is correct, and whether the data switching is correct. Multiple clicks are required to test.
5. For non-business variables such as whether, right or wrong, size, etc., it is necessary to check whether the page display is correct, check whether the front and back ends match, and check whether the back end and the database match. Check whether the enumerated values ​​of each link are consistent.

dynamic form

1. When the dynamic form is adding components or deleting components, check whether the operation result is correct.
2. The dynamic form uses different methods such as hiding or direct deletion, which may have different effects on the result data, and it is necessary to repeatedly test various situations.
3. The number of dynamic forms needs to be limited, and the form can be infinitely increased. Check whether it will affect the page layout.
4. The independence and linkage inspection and testing of each component of the dynamic form.

permission class

1. Under the multi-authority system, after switching accounts, whether all kinds of data meet the permission access requirements.
2. Approval process business, check whether the current processor has the data processing authority.

Mobile check

comprehensive

1. Under the same conditions, check whether the mobile terminal query data is consistent with the web terminal query data.
2. When testing, it is necessary to consider that the screen of the mobile device can be rotated. After the rotation, the information displayed on the screen meets the user's needs.
3. The function entrance is obvious, easy to find, and the operation process is simple and easy to use.
4. Separate tests for Android and Apple machines.
5. Check whether the text label component will affect the page display because the length is too long or too short.
6. For testing of different screen sizes, it is necessary to test the screen sizes of mainstream models.

H5

1. Browser Compatibility Check: Consider mobile phone mainstream browsers, such as QQ, UC, Baidu; consider PC-side mainstream browsers, such as IE, Chrome, Firefox; Android and ios built-in browsers.
2. Refresh and return Whether the page refresh is still on the current page; whether the page shakes when refreshing the page or loading new content; whether the user actively clicks the refresh button to still be on the current page; whether the return page is the desired page by clicking the return and Back buttons.

Applets

1. Permission test, according to whether the WeChat login applet has been authorized to check the function status.

app

1. Verify whether the installation and uninstallation are normal under different operating systems, such as Android, IOS, etc.
2. Whether it can be reinstalled after uninstallation, whether the data is synchronized after installation, and whether the function is normal.
3. When the APP switches to the background and returns to the APP again, whether to stay on the interface of the last operation.
4. When using the APP, the interactive test of mobile phone functions, such as incoming calls, receiving text messages, alarm clocks, uploading pictures, etc.

code inspection

Code inspection is an essential part of testing for developers.

comprehensive

1. Check and test every branch of code where possible.
2. For all external variables and query results, it is necessary to assume that they may be empty, and perform appropriate empty judgment processing according to the assumption.
3. When judging null in the business system, you must pay attention to the handling of Null, empty strings, various blank characters, and the length of 0. Only processing !=null may have problems.

Batch processing/timing tasks

1. For batch task processing, it is necessary to consider the processing strategy when the amount of data is large. If the processing time becomes longer when the amount of data is large, whether it will cause the interface call to time out, and whether it needs to be properly adjusted to asynchronous operation.
2. Because there is no session information during the execution of the scheduled task, there may be some exceptions in the interception of some aspects during the execution of insertion/deletion, such as the failure to obtain the current user. Check whether specific processing is required for these scenarios.
3. Timed tasks must be considered idempotent. In actual project operation and maintenance, it is often necessary to execute timed tasks multiple times, so timed tasks must be designed to be idempotent.
4. Scheduled tasks are generally executed during off-peak periods, but we need to consider whether it will affect system operation and occupy a large amount of resources such as server connections and database connections if executed during normal time periods when designing and testing.

Framework class

1. MyBatis: Reasonably select updateByPrimaryKey and updateByPrimaryKeySelective in MyBatis according to specific business needs (see Appendix T0005 for details)
2. Spring: Spring asynchronous annotation, you need to verify whether it is really asynchronous when using it. It may be because other people have modified the thread pool, and related configurations have caused asynchronous to synchronous.
3. PageHelper pagination result validation. What PageHelper intercepts is the latest execution of SQL to check whether the code execution is correct. Reconstructing the collection object for the returned data of PageHelper will affect the total number, pay attention to check.

Tools

1. When the front-end or back-end performs object replication, it is necessary to determine whether deep copy or shallow copy is based on the specific scene. Some defects are caused by shallow copy.

JavaScript-related

1. The result of JavaScript calculation floating point operation is inaccurate

 

SAAS class

1. Whether the access portal provided by the third-party platform service system is stable for a long time, whether it will change, and how often it will change, if the interface URL changes, whether the system can continue to run stably, and whether it needs to provide a certain processing strategy.
2. Whether it is necessary to expose the external network interface for docking with the SAAS platform, and if necessary, check whether the development, testing, and production environment configurations are complete.
3. Whether there is a certain security mechanism for the external interface exposed by the docking SAAS platform, and whether there is a security risk.
4. Whether the configuration related to the docking SAAS platform is completed in the development, testing, and production environments, and the configuration is correct.

compatibility

1. Whether the file path is suitable for the local operating system, the operating system of the test environment, the operating system of the production environment, and the code blocks related to the file path need to be checked.
2. Whether the WEB system needs to be compatible with IE browser, and if necessary, appropriate compatibility testing should be carried out.

performance check

The performance check of this document is different from the general performance check. The focus of this article is to directly affect the daily use of users, and the user experience is obviously uncomfortable.

1. When pulling up and down to refresh on the mobile terminal or the WEB terminal, is it necessary to use a throttle valve to prevent frequent additional requests (see Appendix T0015 for details).
2. When the mobile terminal or WEB terminal monitors the search input box for similar operations in real time, whether it is necessary to avoid frequent meaningless requests through anti-shake and throttling (see Appendix T0015 for details).
3. For a large amount of data retrieval display, check the performance of deep paging, check the performance of jumping according to the page number, and check the performance of large-scale conditional retrieval.

security check

Security testing Security testing is to test how the software handles the attack or malicious destruction of unauthorized internal or external users, and whether the security of the software and data can be guaranteed.

Data Security

1. Whether personal information such as ID cards, phone numbers, and residential addresses in the system need to be desensitized.
2. Whether the sensitive data in the log needs to be desensitized, or avoid outputting sensitive information.
3. Whether property information needs to be confused and desensitized.
4. During front-end development, be careful to clear all alerts and console.logs used for development before testing or launching.
5. Whether relevant filtering and control is required for content related to national security and prohibited by law, including sensitive text information, sensitive image information, etc.

ultra vires inspection

1. Pay attention to check the unauthorized processing of requests with parameters to prevent unauthorized users from accessing unauthorized data through URL guessing (see Appendix T0008 for details)

document check

Documentation testing Documentation testing mainly focuses on requirements analysis, software design, user manuals, and installation manuals, and mainly verifies whether there are differences between document descriptions and actual software.

Code development is only a part of the entire software development process. We write code according to the requirements document. If the requirements document is ambiguous or problematic, it will directly lead to software development failure. In addition, the code has bugs. Similarly, the requirements document is the same, and there may also be flaws and deficiencies. Software developers need to read the requirements documents carefully during the development process, think more about some of the doubts, and be careful when they feel that there are problems. Timely feedback and discussion.

Requirements check

1. Whether all the demand items raised by the customer are covered.
2. Whether all the requirements for this test/launch are covered.
3. Whether the words are clear, whether there is ambiguity in semantics, and whether there are typos.
4. Is it clearly described what the software needs to do and what it does not do.
5. Whether the target environment of the software is described, including the hardware and software environment.
6. Whether the requirement items are properly numbered.
7. Whether the requirements are consistent and do not conflict with each other.
8. Whether each input of the software, the output format, and the corresponding relationship between input and output are clearly described.
9. Whether the priority of requirements is allocated reasonably.
10. Are the various constraints described.
11. Is it clearly stated the data type of each input item, whether it is required, data length, data range and other restrictions.

Testing or pre-launch inspection

1. Whether the assignment of accounts, permissions, menus, etc. is complete.
2. Whether the SQL scripts and configuration files are configured properly.
3. Whether there are problems such as missing basic data and confusion of basic data.
4. Whether the test submission is based on the requirements of the testing department: build a test submission form, fill in relevant required data, upload attachments, etc.
5. Whether relevant personnel are notified before and after going online, and whether routine system inspections are completed after going online.

appendix

【T0001】Example: A query about personnel information is sorted according to updateTime. This logic is no problem, but because of batch processing tasks, a large amount of data with the same updateTime will appear, which will lead to repetitive problems when querying pages. Sometimes some data appears repeatedly. To solve this problem, the sorting condition needs to ensure the uniqueness of the data. The solution to this problem is to add the sorting condition of id after updateTime, so as to ensure that there will not be exactly the same sorting condition to filter data.

【T0002】Example: Be consistent when calculating age. Note that some are calculated by year, some are calculated by birthday, some are calculated by full age, and some are calculated by imaginary age. No matter which calculation, it must be determined that only one calculation method can be used in one system. The above-mentioned calculations are all possible, but they must be consistent.

【T0003】Example: The background list displays the operation bar on the right, which generally includes editing, viewing, and deleting. Then, during development and testing, it is necessary to ensure that the list of each module of the system maintains the same size, the same order, and the same color attributes as much as possible. Displayed differently in different modules.

[T0004] Page text wrapping, hiding, deformation, and layout confusion are the most common bugs, so each field that needs to be displayed needs to be tested for empty, normal length, text that is less than normal length, and text that is far longer than normal length Condition. There are spliced ​​texts on the page, you need to pay attention to the problem that the text is too long to be squeezed, beyond the hidden, show..., mouse hover to display the prompt text. During development and testing, it is necessary to pay careful attention to the relevant text components, which can be checked by modifying the number of characters, modifying browser resolution, and changing components.

[T0005] Notes for updateByPrimaryKeySelective: There are non-required fields in the form. If the field has historical data, but this time it is blank in the form, then the value of the field still exists when the API is executed. But the value should be empty, need attention.

【T0006】Example: In the house registration business, the house information and personnel information have been registered, so the personnel information must be correctly handled when deleting the house information, so as not to cause problems with the personnel information data after the house information is deleted.

【T0007】Example: In the scenario of registered resident information, duplication of ID cards and phone numbers is generally not allowed; in the scenario of reproductive system, the gender and age of registered personnel need to be checked. Such as ID card format verification, phone number verification and so on.

【T0008】Example: such as GET /user/view/0001. Among them, a certain user information can be obtained through parameter 0001, but this information belongs to administrator A, but at this time administrator B logs in and directly requests this path, and administrator B also has permission to access /usr/view/. But there is no /user/view/0001 permission. If there is no restriction in the background, administrator B can access data beyond the permission through enumeration, so this kind of unauthorized data access also needs to be dealt with.

【T0009】Example: Under the multi-level account system, the default query conditions for different users to enter a certain module need to limit the data within the scope of authority.

[T0010] Example: There is a text component phone number in module A, and the same text component exists in module B, but it is named contact information. This example is a common-sense business, and it is not difficult to cause ambiguity, but for some specific businesses, inconsistent descriptions will cause There are significant differences and the naming needs to be kept as consistent as possible. For another example, some commonly used vocabulary also needs to be consistent, such as type and category. The two may be consistent fields in some systems, and may represent different fields.

【T0011】Example: In many old systems, the statistical data is not particularly accurate, and there may be some abnormal data, operation and maintenance data, etc.; The sum is often less than the total number of people, so it needs to be properly dealt with when displaying the chart to avoid unfriendly chart display due to data problems.

【T0012】Example: When the drop-down list items on the mobile or WEB end reach tens or hundreds, the user operation is not friendly. You can add the search and selection function, or perform sorting processing and display, and put commonly used data in front for users to quickly select .

[T0013] When retrieving data according to conditions, the results displayed by the query should reflect the corresponding retrieval conditions, otherwise it is impossible for users to verify the correctness of the retrieval results.

[T0014] The dynamic form scenario of data write-back includes: the form fields displayed are different according to different entry conditions; the form fields change according to different pre-filter conditions; the form fields are different according to different permission accounts.

【T0015】Example: In the process of many front-end and back-end request processing, we need to consider some repeated and frequent request access. For the pull-down pull-up load refresh on the mobile terminal, or the request operation when clicking the button, etc., the same method No further request visits will be made until the request has been processed. For the real-time monitoring input box retrieval scenario, assuming that the user plans to input hello, five requests will be initiated if no processing is done. The first four times are meaningless. For this type of request, a specific interval can be set, such as not repeating the request within 500 milliseconds , so that the above example will only initiate one request to avoid unnecessary requests. Avoid repeated or meaningless requests by setting some anti-shake and throttling measures to circumvent.