Summary of test points | How to test the search function?

Here we only summarize and share the common test points of the general search box. In actual work, we need to combine the background business requirements of the search function and other dependent conditions to comprehensively design the test points.

1. Function realization part

(1) If fuzzy query is supported, can any character in the search name be searched

For search boxes that support fuzzy queries, test whether any character in the search name can be searched.

For example, when entering "HUAWEI" in the search box of a product list, the query results should include "HUAWEI", "HUAWEI Watch" and so on. If it is not found, there is a problem with the search function.

(2) Whether the longer name can be queried correctly

Test the search ability of the search box for relatively long names.

For example, when querying basketball shoes "Network Security Engineer Zero-Basic Training Video Tutorial Web Penetration Attack and Defense Employment Class Course Employment Course", set the name of the search box to "Network Security Engineer Zero-Basic Training Video Tutorial Web Penetration Offense and Defense Employment Class Course" Employment class course" to test whether the search box can correctly query this product.

(3) Input matching conditions that do not exist in the system

Test the fault tolerance of the search box, that is, enter conditions that do not exist in the system and query, and test whether there are matching results returned.

For example, input a product name that does not exist in an e-commerce website, and test whether a result will be returned. If a search term returns no results, there is a problem with the search function. If the result does not exist, the system needs to inform that there is no result or other friendly prompts.

(4) When the user performs a query operation, the general situation is not to clear the query conditions, unless there is a special requirement.

When testing the function implementation of the search box, it is necessary to consider that when users perform query operations, they generally do not clear the query conditions. Therefore, for example, when querying a product on an e-commerce website, the user can continuously input multiple search conditions without clearing the previous search conditions. When testing, we need to confirm that this works correctly.

(5) Special character processing

Test the performance of the search box when handling special characters, such as double quotes, slashes, backslashes and other special characters. The testing framework needs to verify that the search box can handle these characters normally to avoid vulnerabilities caused by special characters.

2. Combination test

(1) Choose back and forth between different query conditions, whether there is a page error (radio box and multi-choice box are the most error-prone)

When testing the combination test of the search box, it is necessary to pay attention to the possible page errors between different query conditions. For example, in an e-commerce website, when the user selects the query conditions in the radio box and the multi-select box, it is necessary to test whether there is a page error to verify the normality of the search box.

(2) When testing multiple query conditions, pay attention to the combination test of the query conditions, and the tests of different combinations may report errors.

For the test of multiple query conditions, it is necessary to pay attention to the combination test of different query conditions, because different combinations of tests may cause errors.

For example, on an e-commerce website, when a user queries the product "Water Cup" and adds conditions such as "Brand", "Color", and "Price" at the same time, it is necessary to test whether the search box can handle various combination tests normally.

(3) Pagination of query results, click all the way to the last page to check whether there is duplicate data (dummy data may appear, which is more common in the test process, and many front-ends will miss processing)

When testing the pagination of query results, it is necessary to test whether there is duplicate data. Sometimes, false data may appear in the search box. For example, in a music website, when a user searches for "nursery songs" and performs pagination, it is necessary to verify whether the search box has effectively processed the paging function and query results.

3. Historical search records

(1) It is common when saving the recent historical search records on the page, and the records that are too long to enter (or lead to line breaks) display misplaced

When there are historical search records in the search box, it is necessary to test whether it can save the records correctly. For example, in the input box of the search box, when the user enters a long string of character strings, it is necessary to test whether the records can be stored correctly and whether there is a misplacement.

4. Filter test

When testing the filtering functionality of the search box, it is necessary to test the correctness of different types of filters.

For example, in an e-commerce website, when a user selects filters such as "brand", "color", and "price" in the "water glass" product, it is necessary to test whether the filter can correctly filter out eligible products, so as to Verify the normality of the search box.

5. Smart Tips

When testing smart prompts, you need to test whether the recommended results are displayed when the user enters keywords, and check whether the results are related to the keywords entered by the user.

At the same time, it is necessary to consider whether the intelligent prompts in different input scenarios are accurate and effective, such as pinyin input, error input prompts, etc.

For example, when a news query is performed in a news APP, when the user enters half of the keywords, a smart prompt box should appear, prompting the user with a list of news titles that may be of interest.

6. Test of search results

When testing search results, you need to test whether eligible products or other information are correctly listed in the search results. And whether the sorting, display methods, labels and other related displays in the search result list meet the requirements.

For example, when searching for songs in a music APP, it is necessary to verify the normality of the search box by verifying whether the corresponding music name, singer, album, duration and other information are listed in the search results.

Through the above test points, the normality and effectiveness of the search box function can be better guaranteed. However, there is still a lot of space for the test of the search box and other considerations, such as the need to combine the influence of different operating systems, browsers, screen resolutions, network environments and other factors to improve the comprehensiveness and coverage of the test . Therefore, as testers, we need to constantly explore new testing points and techniques to improve the effectiveness and accuracy of testing.

In the process of testing the search function, what common bugs have you encountered? Welcome to leave a message, comment and share~

Finally:  The complete software testing video learning tutorial below has been sorted out and uploaded, and friends can get it for free if they need it【保证100%免费】

insert image description here

 These materials should be the most comprehensive and complete preparation warehouse for [software testing] friends. This warehouse has also accompanied tens of thousands of test engineers through the most difficult journey. I hope it can help you too!

软件测试技术交流群社:786229024(里面还有工作内推机会,毕竟我们是关系社会。)

Software Testing Interview Documentation

We must study to find a high-paying job. The following interview questions are the latest interview materials from first-tier Internet companies such as Ali, Tencent, and Byte, and some Byte bosses have given authoritative answers. Finish this set The interview materials believe that everyone can find a satisfactory job.

How to obtain interview documents:

Guess you like

Origin blog.csdn.net/wx17343624830/article/details/130160802