Test uniqueness in office development

Today I modified some of my previous ones.CodeWhich is particularly bad.

The Code mainly uses VBA for Word and Excel recognition functions. During the modification process, some problems are gradually found and blushing.

To sum up:

1: In the recognition of the first word sinking, the number of corresponding segments after removing all kinds of interference characters must be 1. The interference characters mainly include visible and invisible characters, the most annoying thing is that some words do not support the first line of indent characters, so you have to gradually explore.

2: The biggest problem occurs in some attribute recognition in Excel, mainly due to the impact of null values. In the past, when reading VBA, I did not pay too much attention to null, now it seems to be a big problem. For example, a cell contains multiple Chinese characters, some words are set to bold, and some are not set to bold. At this time, the font of the entire cell is used. the value returned by bold is null. The solution is to identify the values one by one based on the characters in the cell.

Through the discovery and solution of these problems, we can know that in offic development, experience is the most important. One is the proficiency of office software, and the other is the proficiency of office development, however, it is most important to improve office testing in these areas.

In office development, tests are often ignored. Based on my experience, I hope my friends can add:

1: For office version testing, there are some differences in the support of VBA in different versions of office. To quickly correct errors, you must perform system testing in different office versions, the different versions mentioned here refer to testing in different offices, and forming test files in different versions, and then testing again in different versions.

2: The production of test cases, due to the flexibility and diversity of office software, has resulted in the same document, different people have different styles, so in the production of test cases, make sure to combine the functions of the system with Office experts, and consider possible user situations.

3: logic testing. In office documents, related operations often lead to confusion in the system. Therefore, as many operations with logical relationships as possible can be restricted by operation constraints, the test cases are shown.

4: test the dependency on the external environment. For example, some printing-related operations in the office must depend on local or network printers. Therefore, the system should consider changes in the external environment during the test.

5: Test of system errors caused by Office installation. Office components are optional. Therefore, some components that require special installation, such as the "Public Editor" and other components that are specially required by the system, during the test, no installation test is required to check the system stability.

6: test the antivirus software license, which is particularly important. There are no fewer system errors caused by association of office documents with antivirus software or virus interference.

You can only think of this. Let's just add it.