Functional testing 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. Common test methods for web systems are as follows:
1. Page link check: Whether each link has a corresponding page, and the switching between pages is correct. Some tools can be used, such as LinkBotPro, File-AIDCS, HTML Link Validator, Xenu and other tools. LinkBotPro does not support Chinese, and Chinese characters are displayed as garbled characters; HTML Link Validator can only test webpage links ending in Html or htm; Xenu does not need to be installed, and supports webpages ending in asp, do, jsp, etc. xenu test links include internal links and external links , you should pay attention when using it, and at the same time, it can generate a test report in html format. If the system uses QTP for automated testing, you can also use QTP's page checkpoint to check links.
2. Relevance check: Functional dependency: Will deleting/adding one item affect other items? A field with a long content may distort the data list during query.
Data dependency: check the default value of the down list, check the value of the down list, if a data item in a list depends on data in other modules, it also needs to be checked, for example, if a certain data is disabled, it may be referencing the data item is not visible in the list of .
3. Check whether the functions of the buttons are correct: such as new, edit, delete, close, return, save, import, previous page, next page, page jump, reset and other functions are correct. A common mistake would be on the reset button, which would appear as a malfunction.
4. String length check: Enter content that exceeds the string length specified in the requirement to see if the system checks the string length. Also check whether the string length specified by the requirements is correct. Sometimes, the string length specified by the requirements is too short to input business data.
5. Character type check: Enter other types of content where the specified type of content should be input (such as input other character types where integers should be input), and see if the system checks the character type.
6. Punctuation check: input includes various punctuation marks, especially spaces, various quotation marks, and the Enter key. See if the system handles it correctly. A common mistake is the system's handling of spaces. When it is possible to add a space, it treats a space as a character, but the space is masked when querying, resulting in the inability to query the added content.
7. Special character check: Input special symbols, such as @, #, $, %, !, etc., to see if the system handles them correctly. A common mistake is the special characters % ' ".
8. Chinese character processing: input Chinese in a system that can input Chinese and English, and check whether there will be garbled characters or errors.
9. Check the integrity of the information: When viewing and updating information, check whether all the information filled in is updated, and whether the updated information is consistent with the added information. It should be noted that each field should be checked when checking. Sometimes, some fields are updated but some fields are not updated.
10. Information duplication: input duplicate names or IDs for some information that needs to be named and the name should be unique, and see if the system handles it and whether an error will be reported. Duplicate names include case-sensitive, and enter spaces before and after the input content. Whether the system handles it correctly.
11. Check the delete function: In some places where multiple messages can be deleted at one time, do not select any message, press "delete" to see how the system handles it, and whether there will be errors; then select one or more messages and delete them to see if they are processed correctly . If there are multiple pages, turn the page and select to see if the system deletes them correctly, and pay attention to whether there is a prompt when deleting, so that the user can correct the error and not delete it by mistake.
12. Check whether the addition and modification are consistent: Check whether the requirements for adding and modifying information are consistent. For example, if an item is required to be added, the modification should also be required; if an item is added as an integer, the modification must also be an integer.
13. Check and modify the duplicate name: When modifying, change the item that cannot be duplicated into the existing content, see if it will be processed, and report an error. At the same time, you should also pay attention to whether you will report the mistake of having the same name as yourself.
14. Repeated submission form: A record that has been successfully submitted, submit it after returning to see if the system has processed it. For the web system, the return key of the browser or the return function provided by the system can be used.
15. Check the situation of using the return key multiple times: where there is a return key, return to the original page, repeat it several times, and see if there is an error.
16. Search check: Input the content that exists or does not exist in the system where there is a search function, and check whether the search result is correct. If you can enter multiple search conditions, you can add reasonable and unreasonable conditions at the same time to see if the system handles it correctly. You should also pay attention to special characters when searching. Some systems will save all the information in the system when entering special characters. are found.
17. Input information position: pay attention to whether the cursor and the input information will jump to other places when inputting information at the place where the cursor stays.
18. Check for uploading and downloading files: whether the function of uploading and downloading files is realized, and whether the uploaded files can be opened. What are the regulations on the format of uploaded files, whether the system has explanation information, and check whether the system can do it. Whether the downloaded file can be opened or saved, whether the downloaded file has format requirements, and if special tools are required to open it, etc. The upload file test should be tested at the same time. If the suffix of the file that cannot be uploaded is changed to the suffix of the file that can be uploaded, see if the upload is successful. And, after uploading the file, modify it again to see if the uploaded file exists.
19. Mandatory items check: whether the system has processed all the items that should be filled in if they are not filled in, and whether there is a prompt message for the required items, such as adding "*" before the required items; after returning to the prompt for the required items, focus Whether to automatically locate required fields.
20. Shortcut key check: Whether it supports common shortcut keys, such as Ctrl+C, Ctrl+V, Backspace, etc., and whether there are restrictions on shortcuts for some fields that do not allow input information, such as selecting people and selecting dates.
21. Enter key check: Press the Enter key directly after the input to see how the system handles and whether an error will be reported. There is a good chance that errors can occur here.
22. Refresh key check: In the web system, use the browser's refresh key to see how the system handles it and whether an error will be reported.
23. Check the back button: In the web system, use the back button of the browser to see how the system handles it and whether an error will be reported. For systems that require user authentication, after logging out, use the back button to see how the system handles it; use the back button multiple times, and use the forward key multiple times to see how the system handles it.
24. Direct URL link check: In the Web system, directly input the URL address of each function page to see how the system handles it, which is more important for systems that require user authentication. If the system security design is not good, directly input the URL address of each function page, it is very likely that the page will be opened normally.
25. Space check: In the input information item, enter one or a series of spaces to see how the system handles it. For example, for items that require the input of integer and dot-type variables, enter a space, which is neither a null value nor a standard input.
26. Half-width and full-width input method check: In the input information item, enter half-width or full-width information to check how the system handles it. For example, for items that require the input of point-type data, enter a full-width decimal point ("." or ".", such as 4.5); enter a full-width space, etc.
27. Password checking: some system’s keying methods use the method of shifting the character’s Ascii code, which is relatively simple to process password keying and has high security. For LAN systems, this method can completely play a key role. However, at the same time, it will cause some problems, that is, the characters corresponding to Ascii greater than 128 cannot be parsed during decryption. Try to use some characters with a larger code value such as "uvwxyz" as the password. At the same time, the password should be as long as possible, such as 17-digit password, etc., resulting in unparseable characters in the final password.
28. User check: Any system has various users, and also has one or more administrator users. Check whether each administrator can manage each other, edit and delete administrator users. At the same time, for general users, try to delete and recreate the user with the same name, and check whether other information of the user is reproduced. Similarly, for a system that provides a logout function, whether this user will be a new user when registering again. And also check the valid date of the user, users who have passed the valid date cannot log in to the system. The error-prone situation is that non-super administrators who may have user management rights can modify the rights of super administrators.
29. System data check: This is the most important function test. If the system data calculation is incorrect, the function test will definitely fail. Data inspection depends on different systems and methods are different. For business management platforms, data remains correct with changes in business processes and status. Junk data cannot appear because of a certain process, and data cannot be lost due to a certain process.
30. System recoverability check: paralyze the system in various ways, and test whether the system can recover normally and quickly.
31. Confirmation prompt check: For update and delete operations in the system, whether to prompt the user to confirm the update or delete, whether the operation can be rolled back (that is, whether you can choose to cancel the operation), and whether the prompt information is accurate. Prompt before or after the event, for the Update or Delete operation, a pre-prompt is required.
32. Data injection inspection: Data injection is mainly for database injection. By inputting some special characters, such as "'", "/", "-", etc. or character combinations, the destruction of SQL statements is completed, causing system queries, The SQL for inserting and deleting operations changes its original intention because of these characters. For example, select * from table where id = ' ' and name = ' ', by entering "12'-" in the id input box, the query statement will comment out the name condition, and only query the record with id=12. Similarly, for update and delete operations, data may be deleted by mistake. Of course, there are other SQL injection methods. For details, please refer to "SQL Application Advanced SQL Injection.doc". Many programs control the input characters based on the page. You can try to skip the interface and directly insert data into the database, such as using Jmeter , to complete the data injection check.
33. Refresh check: The real-time refresh function of the WebForm control in the web system has both advantages and disadvantages in system applications, and has a great impact on system performance. During the test, detect the impact of the refresh function on the system or application (white screen), check whether the control returns to the default initial value, and check whether it has a large impact on the performance of the system (such as connecting to the database query for each refresh, etc.).
34. Transaction check: For transactional operations, disconnect the network or close the program to interrupt the operation, and whether the transaction is rolled back.
35. Time and date check: time and date verification is necessary for every system, such as 2006-2-29, 2006-6-31 and other wrong dates. December of the year (similarly, the first quarter of each year and the fourth quarter of the previous year). In addition, for the verification of date and time formats, such as February 28, 2006, 2006-2-28, 20060228, etc. The date check also checks whether the date range conforms to the actual business, and whether the system will prompt or limit the date that does not meet the time business.
36. Multi-browser verification: With the emergence of more and more various browsers, users no longer rely solely on Microsoft Internet Explorer to access Web programs, but have more choices: Maxthon, Firefox, Tencent Traveler, etc. Consider Use multiple browsers to access the system and verify the effect.
37. Installation test: For systems with C/S architecture, the test of the installation program is an important aspect, the degree of automation of the installation program, installation options and settings (to verify whether various solutions can be installed normally), the interruption test of the installation process, and the installation sequence Testing (distributed systems), repair installation and uninstallation testing.
38. Documentation test: mainly to test user manuals and product manuals to check whether the description is correct and complete, whether it is compared with the current system version, whether it is easy to understand, whether it is ambiguous, etc.
39. Test data check: The facts tell us that the test data is more likely to be wrong than the code. Therefore, when the test results show that there is an error, check the test data before suspecting that the code is wrong.
40. Please let my machine run: In some projects, there is a sick problem: there is no problem with the system, it can pass on my machine. This shows that there are bugs related to the environment. "Is everything managed by the version control tool?", "Is the development environment of the local machine the same as the server environment?", "Is there a real BUG here, but it just happened to appear in other machines ?”. All tests must pass on all machines required by the system, otherwise, there may be problems with the code.
41. Application of Ajax technology: Ajax has many advantages, but it also has many disadvantages. If we use the advantages and avoid the disadvantages, it is a challenge for us to the new Web2.0 application. The most direct problem in the application of Ajax is user experience, and the effect of user experience is directly related to whether to use Ajax technology. "Being able to do it does not mean that it should be done or must be done", this is a very important comment on Ajax technology.
42. Application of Ajax technology: Ajax uses the mechanism of asynchronous call to realize the partial refresh function of the page. Asynchronous call may be interrupted abnormally. Try various methods to interrupt the asynchronous data call abnormally to see if there is a problem. One of the problems encountered here is the operation of the date control, and it has been refreshed when there is a lot of page data.
43. Script errors: With the development of asynchronous calling technologies such as Ajax and IFrame, Javascrīpt technology has been paid more and more attention by developers. However, Javascrīpt has problems such as debugging difficulties and possible incompatibility of various browsers, so in the Web system
Summarize
Finally, I would like to thank everyone who reads my article carefully. Reciprocity is always necessary. Although it is not a very valuable thing, if you can use it, you can take it directly: including, software learning roadmap, more than 50 days of class videos, 16 surprise actual combat projects, more than 80 software testing software, 37 test documents, 70 software testing-related questions, 40 testing experience-level articles, thousands of real test questions to share, and the 2022 software testing interview book, and All kinds of selected resumes for software testing job hunting, I hope it will be helpful to everyone...
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, and I hope it can help you! Partners can click the small card below to receive